Another HTML-lint 5
Table of Contents
Another HTML-lint 5
About Accessibility

WAI Content Accessibility Guidelines 1.0 is advised in 1999/05/05. This document also includes another document named Techniques for Web Content Accessibility Guidelines.

The following priority is provided for guidance.

[Priority 1]: MUST checkpoint. You have to satisfy this checkpoint, otherwise your document could be inaccessible.
[Priority 2]: SHOULD checkpoint. You should satisfy this checkpoint, otherwise you document could be difficult to access.
[Priority 3]: MAY rule. If you address this checkpoint, more visitors are able to access your document without difficulty.

Web Accessibility Initiative (WAI) defines three levels of conformance to the document as below.

A: all Priority 1 checkpoints are satisfied
AA: Double-A. all Priority 1 and 2 checkpoints are satisfied
AAA: Triple-A. all Priority 1, 2, and 3 checkpoints are satisfied

This advisory report is a guideline regarding a content of HTML documents, which Another HTML-lint 5 does not cover. Therefore, Another HTML-lint 5 is unable to check most of the checkpoints given here. That is, Another HTML-lint 5 will not show the levels of conformance. You can use this checklist instead.

You can see what kind of checkpoints Another HTML-lint 5 checks among the Checkpoints for Web Content Accessibility. Please visit here for more information.

Top  
Guideline 1. Provide equivalent alternatives to non-text element
1.1 Provide a text equivalent for every non-text element [Priority 1]
This guideline is applicable to: and so on. Regarding ALT, other tags than <IMG> are also checked. This guideline prompt us to provide an additional description using, for example, LONGDESC where the ALT text does not provide a complete text equivalent. However it is hard to tell if the provided text is a complete text equivalent, so Another HTML-lint 5 does not go that far. The combination between <A> and <MAP> for image map is not to be checked either.
1.2 Provide redundant text links for each active region of a server-side image map. [Priority 1]
Not be checked.
1.3 Provide an auditory description for a visual content. [Priority 1]
Not be checked.
1.4 Provide equivalent alternatives for a movie or animation etc. [Priority 1]
Not be checked.
1.5 Provide redundant text for a client-side image map. [Priority 3]
Not be checked.
Top  
Guideline 2. Don't rely on color alone.
2.1 Ensure that all information conveyed with color is also available without color. [Priority 1]
Not be checked.
2.2 Ensure that foreground and background color combinations provide sufficient contrast. [Priority 2 and 3]
This guideline is applicable to: and so on. However, these are basically related to <BODY> and Another HTML-lint 5 can not check the contrast in detail.
Top  
Guideline 3. Use markup and style sheets and do so properly.
3.1Use markup rather than images to convey information. [Priority 2]
Not be checked.
3.2Create documents that validate to published formal grammars. [Priority 2]
This guideline is exactly what Another HTML-lint 5 exists for, but to mention some; and so on.
3.3 Use style sheets to control layout and presentation. [Priority 2]
This guideline is applicable to: and so on.
3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. [Priority 2]
Not be checked.
3.5 Use header elements to convey document structure. [Priority 2]
This guideline is indirectly applicable to, but it is not possible to check this directly.
3.6 Mark up lists and list items properly. [Priority 2]
Not be checked.
3.7 Do not use quotation markup for formatting effects such as indentation. [Priority 2]
Not be checked.
Top  
Guideline 4. Clarify natural language usage
4.1 Clearly identify changes in the natural language of a document's text. [Priority 1]
This guideline may be applicable to: and so on.
4.2 Specify the expansion of each abbreviation or acronym in a document. [Priority 3]
This guideline is applicable to:
4.3 Identify the primary natural language of a document. [Priority 3]
This guideline is applicable to:
Top  
Guideline 5. Create tables that transform gracefully.
5.1 For data tables, identify row and column headers. [Priority 1]
Not be checked.
5.2 Use markup to associate data cells and header cells. [Priority 1]
Not be checked.
5.3 Do not use tables for layout unless the table makes sense when linearized. [Priority 2]
Not be checked.
5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2]
Not be checked. Another HTML-lint 5 does check where <TH> is placed in a table, however we are not sure if that is what the guideline means.
5.5 Provide summaries for tables. [Priority 3]
This guideline is applicable to: but <CAPTION> is not to be checked.
5.6 Provide abbreviations for header labels. [Priority 3]
This guideline is applicable to:
Top  
Guideline 6. Ensure that pages featuring new technologies transform gracefully.
6.1 Organize documents so they may be read without style sheets. [Priority 1]
Not be checked.
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1]
This guideline is applicable to:
6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. [Priority 1]
This guideline is applicable to: and so on.
6.4 For scripts and applets, ensure that event handlers are input device-independent. [Priority 2]
This guideline is applicable to: and so on.
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2]
his guideline is applicable to: and so on.
Top  
Guideline 7. Ensure user control of time-sensitive content changes.
7.1 Avoid causing the screen to flicker. [Priority 1]
This guideline is applicable to: which restricts use of <BLINK> and <MARQUEE>.
7.2 avoid causing content to blink. [Priority 2]
This guideline is applicable to: which restricts use of <BLINK> and <MARQUEE>.
7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2]
Not be checked.
7.4 Do not create periodically auto-refreshing pages. [Priority 2]
This guideline is applicable to:
7.5 Do not use markup to redirect pages automatically. [Priority 2]
This guideline is applicable to:
Top  
Guideline 8. Ensure direct accessibility of embedded user interfaces.
8.1 Make programmatic elements such as scripts and applets directly accessible. [Priority 1～2]
Not be checked.
Top  
Guideline 9. Design for device-independence.
9.1 Provide client-side image maps instead of server-side image maps. [Priority 1]
This guideline is applicable to:
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2]
Not be checked.
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2]
Not be checked.
9.4 Create a logical tab order through links, form controls, and objects. [Priority 3]
This guideline is applicable to:
9.5 Provide keyboard shortcuts to important links, form controls, and groups of form controls. [Priority 3]
This guideline is applicable to:
Top  
Guideline 10. Use interim solutions.
10.1 do not cause pop-ups or other windows to appear and do not change the current window without informing the user. [Priority 2]
Not be checked.
10.2 for all form controls with implicitly associated labels, ensure that the label is properly positioned. [Priority 2]
This guideline may be applicable to: but it is not exactly what the guideline intend.
10.3 provide a linear text alternative for all tables that lay out text in parallel, word-wrapped columns. [Priority 3]
Not be checked.
10.4 include default, place-holding characters in edit boxes and text areas. [Priority 3]
This guideline is applicable to:
10.5 include non-link, printable characters between adjacent links. [Priority 3]
This guideline is applicable to:
Top  
Guideline 11. Use W3C technologies and guidelines.
11.1 Use W3C technologies when they are available and appropriate for a task. [Priority 2]
Not be checked.
11.2 Avoid deprecated features of W3C technologies. [Priority 2]
This guideline is applicable to: and so on.
11.3 Provide information so that users may receive documents according to their preferences. [Priority 3]
Not be checked.
11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information, and is updated as often as the inaccessible page. [[Priority 1]
Not be checked.
Top  
Guideline 12. Provide context and orientation information.
12.1 Title each frame to facilitate frame identification and navigation. [Priority 1]
This guideline is applicable to:
12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [Priority 2]
Not be checked.
12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]
Not be checked.
12.4 Associate labels explicitly with their controls. [Priority 2]
This guideline is applicable to: and so on.
Top  
Guideline 13. Provide clear navigation mechanisms.
13.1 Clearly identify the target of each link. [Priority 2]
This guideline is applicable to: and so on.
13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]
This guideline is applicable to: but <ADDRESS> is not to be checked.
13.3 Provide information about the general layout of a site. [Priority 2]
Not be checked.
13.4 Use navigation mechanisms in a consistent manner. [Priority 2]
This guideline is applicable to: and so on.
13.5 Provide navigation bars to highlight and give access to the navigation mechanism. [Priority 3]
No be checked.
13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. [Priority 3]
Not be checked.
13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.[Priority 3]
No be checked.
13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc. [Priority 3]
No be checked.
13.9 Provide information about document collections. [Priority 3]
No be checked.
13.10 Provide a means to skip over multi-line ASCII art. [Priority 3]
No be checked.
Top  
Guideline 14. Ensure that documents are clear and simple.
14.1 Use the clearest and simplest language appropriate for a site's content.[Priority 1]
No be checked.
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.[Priority 3]
Same as Guideline 1. checkpoint for Another HTML-lint 5.
14.3 Create a style of presentation that is consistent across pages. [Priority 3]
No be checked.
Top  
Copyright (C) 2009 - 2018 Heartcore,Inc. All Rights Reserved.