 |
 |
Home | Policy | About | Status Reports | Meetings | Membership | Listserv | Resources | Tools | Tutorials | Forms | News | Search | Site Map
The Accessibility Working Group is proposing that the new technical standards consist of all WCAG Priority 1 Guidelines, and the following Design Requirements:
Design Requirement: 6. Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
WCAG Guideline: 2 WCAG Checkpoint: 2.2 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: 1194.22 (c)
Suggested Language: 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
Link to Techniques: http://www.w3.org/TR/WCAG10-HTML-TECHS/#color-images
Design Requirement: 1. Include a document type declaration (DOCTYPE) in your web pages. This declares what version of HTML you are using in your documents, and assists the browser in rendering your pages correctly.
WCAG Guideline: 3 WCAG Checkpoint: 3.2 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 3.2 Create documents that validate to published formal grammars. For example, include a document type declaration at the beginning of a document that refers to a published DTD (e.g., the strict HTML 4.0 DTD).
Link to Techniques: http://www.w3.org/TR/WCAG10-HTML-TECHS/#doctype
New
Design Requirement: 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
WCAG Guideline: 5 WCAG Checkpoint: 5.4 WCAG Priority: 2 WCAG Category: Tables
Section 508 Standard: N/A
Suggested Language: 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-table-layout
Design Requirement: 1. Provide alternative content in case active features are inaccessible or unsupported.
WCAG Guideline: 6 WCAG Checkpoint: 6.4 WCAG Priority: 2 WCAG Category: Applets and scripts
Section 508 Standard: 1194.22 (m)
Suggested Language: 6.4 For scripts and applets, ensure that event handlers are input device-independent.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-keyboard-operable-scripts
Design Requirement: 10. Ensure that dynamic content is accessible or provide an alternative presentation or page.
WCAG Guideline: 6 WCAG Checkpoint: 6.5 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: 1194.22 (l)
Suggested Language: 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-fallback-page
New
Design Requirement: 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).
WCAG Guideline: 7 WCAG Checkpoint: 7.2 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-avoid-blinking
New
Design Requirement: 7.3 Until user agents allow users to freeze moving content, avoid movement in pages.
WCAG Guideline: 7 WCAG Checkpoint: 7.3 WCAG Priority: 2 WCAG Category: Applets and scripts
Section 508 Standard: N/A
Suggested Language: 7.3 Until user agents allow users to freeze moving content, avoid movement in pages.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-avoid-movement
Design Requirement: 1. Provide alternative content in case active features are inaccessible or unsupported.
WCAG Guideline: 8 WCAG Checkpoint: 8.1 WCAG Priority: 2 WCAG Category: Applets and scripts
Section 508 Standard: 1194.22 (m)
Suggested Language: 8.1 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.]
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-directly-accessible
New
Design Requirement: 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.
WCAG Guideline: 9 WCAG Checkpoint: 9.2 WCAG Priority: 2 WCAG Category: Applets and scripts
Section 508 Standard: N/A
Suggested Language: 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.
Link to Techniques: http://www.w3.org/TR/WCAG10-HTML-TECHS/#accessible-applets
New
Design Requirement: 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.
WCAG Guideline: 9 WCAG Checkpoint: 9.3 WCAG Priority: 2 WCAG Category: Applets and scripts
Section 508 Standard: N/A
Suggested Language: 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.
Link to Techniques: http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts
New
Design Requirement: 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.
WCAG Guideline: 10 WCAG Checkpoint: 10.1 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 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.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-avoid-pop-ups
Design Requirement: 3. (Text-based design) Provide alternate versions of forms; Alternatives might include a simple list or paragraph of what is needed to submit a form entry and then provide a link to a mailto: feature or simply an appropriate e-mail address to send the text.
WCAG Guideline: 10 WCAG Checkpoint: 10.2 WCAG Priority: 2 WCAG Category: Forms
Section 508 Standard: 1194.22 (n)
Suggested Language: 1194.22 (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-unassociated-labels
Design Requirement: 3. (Text-based design) Provide alternate versions of forms; Alternatives might include a simple list or paragraph of what is needed to submit a form entry and then provide a link to a mailto: feature or simply an appropriate e-mail address to send the text.
WCAG Guideline: 12 WCAG Checkpoint: 12.4 WCAG Priority: 2 WCAG Category: Forms
Section 508 Standard: 1194.22 (n)
Suggested Language: 1194.22 (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-associate-labels
New
Design Requirement: 12.4 Associate labels explicitly with their controls.
WCAG Guideline: 12 WCAG Checkpoint: 12.4 WCAG Priority: 2 WCAG Category: Forms
Section 508 Standard: 1194.22 (n)
Suggested Language: 1194.22 (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-associate-labels
Design Requirement: 15. Hyperlinks to downloadable files should include a text description that includes the file size and file type.
WCAG Guideline: 13 WCAG Checkpoint: 13.1 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 13.1 Clearly identify the target of each link.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-meaningful-links
Design Requirement: 7. (a) Provide meaningful and descriptive text for hyperlinks, don't use short hand, e.g. "click here"; instead "Follow this link to our News Page", where the words "News Page" are hyperlinked. (Screen readers can search specifically for linked text, "click here" provides no indication of where the link will take them.)
WCAG Guideline: 13 WCAG Checkpoint: 13.1 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 13.1 Clearly identify the target of each link.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-meaningful-links
Design Requirement: 5. If you link to an audio file, inform the user of the audio file format and file size in kilobytes.
WCAG Guideline: 13 WCAG Checkpoint: 13.1 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 13.1 Clearly identify the target of each link.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-meaningful-links
Design Requirement: 7. Provide a text-only index or site map of your site.
WCAG Guideline: 13 WCAG Checkpoint: 13.3 WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-site-description
Design Requirement: 2. (a) Maintain a standard navigation method throughout the web site.
WCAG Guideline: 13 WCAG Checkpoint: 13.4 (consistent navigation mechanisms) WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 13.4 Use navigation mechanisms in a consistent manner.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-clear-nav-mechanism
Design Requirement: 3. (Universal Design) (a) Use headings, lists, and consistent structure.
WCAG Guideline: 3 WCAG Checkpoint: 3.5 (headers) WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 3.5 Use header elements to convey document structure and use them according to specification.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-logical-headings
Design Requirement: 3. (Universal Design) (b) Use headings, lists, and consistent structure.
WCAG Guideline: 3 WCAG Checkpoint: 3.6 (lists) WCAG Priority: 2 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 3.6 Mark up lists and list items properly.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-list-structure
Design Requirement: 3. (Text-based design) Provide alternate versions of forms; Alternatives might include a simple list or paragraph of what is needed to submit a form entry and then provide a link to a mailto: feature or simply an appropriate e-mail address to send the text.
WCAG Guideline: 10 WCAG Checkpoint: 10.4 WCAG Priority: 3 WCAG Category: Forms
Section 508 Standard: 1194.22 (n)
Suggested Language: 1194.22 (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-place-holders
Design Requirement: 2. (b) Maintain a standard page layout throughout the web site.
WCAG Guideline: 14 WCAG Checkpoint: 14.3 (consistent presentation) WCAG Priority: 3 WCAG Category: In General
Section 508 Standard: N/A
Suggested Language: 14.3 Create a style of presentation that is consistent across pages.
Link to Techniques: http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-consistent-style
New
Design Requirement: 1194.22 (o) A method shall be provided that permits users to skip repetitive navigation links.
WCAG Guideline: N/A WCAG Checkpoint: N/A WCAG Priority: N/A WCAG Category: N/A
Section 508 Standard: 1194.22 (o)
Suggested Language: 1194.22 (o) A method shall be provided that permits users to skip repetitive navigation links.
Link to Techniques: http://www.access-board.gov/sec508/guide/1194.22.htm#(o)
New
Design Requirement: 1194.22 (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
WCAG Guideline: N/A WCAG Checkpoint: N/A WCAG Priority: N/A WCAG Category: N/A
Section 508 Standard: 1194.22 (p)
Suggested Language: 1194.22 (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
Link to Techniques: http://www.access-board.gov/sec508/guide/1194.22.htm#(p)
New
From the Draft version of the Web Content Accessibility Guidelines (WCAG) 2.0
Guideline 2.4 Provide mechanisms to help users find content, orient themselves within it, and navigate through it. http://www.w3.org/TR/WCAG20/#navigation-mechanisms.
|