3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2]
3.2 Create documents that validate to published formal grammars. [Priority 2]
3.3 Use style sheets to control layout and presentation. [Priority 2]
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [Priority 2]
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2]
7.2 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2]
7.3 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [Priority 2]
7.4 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. [Priority 2]
7.5 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2]
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2]
10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. [Priority 2]
10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. [Priority 2]
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority 2]
11.2 Avoid deprecated features of W3C technologies. [Priority 2]
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]
12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]
12.4 Associate labels explicitly with their controls. [Priority 2]
13.1 Clearly identify the target of each link. [Priority 2]
13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2]
13.4 Use navigation mechanisms in a consistent manner. [Priority 2]
3.2 Create documents that validate to published formal grammars. [Priority 2]
3.3 Use style sheets to control layout and presentation. [Priority 2]
- 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. [Priority 2]
- 3.5 Use header elements to convey document structure and use them according to specification. [Priority 2]
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [Priority 2]
- 5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). [Priority 2]
- 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2]
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2]
7.2 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2]
7.3 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [Priority 2]
7.4 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. [Priority 2]
7.5 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2]
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2]
10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. [Priority 2]
10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. [Priority 2]
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority 2]
11.2 Avoid deprecated features of W3C technologies. [Priority 2]
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]
12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]
12.4 Associate labels explicitly with their controls. [Priority 2]
13.1 Clearly identify the target of each link. [Priority 2]
13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2]
13.4 Use navigation mechanisms in a consistent manner. [Priority 2]
No comments:
Post a Comment