(New page: The full WCAG 1.0 checklist can be viewed in [http://www.w3.org/TR/WCAG10/full-checklist.html W3C's website].<br> Priority 1 Checkpoints<br> {| width="80%" cellspacing="1" cellpadding="1...) |
|||
| Line 1: | Line 1: | ||
| − | The full WCAG 1.0 checklist can be viewed in [http://www.w3.org/TR/WCAG10/full-checklist.html W3C's website].<br> | + | The full WCAG 1.0 checklist can be viewed in [http://www.w3.org/TR/WCAG10/full-checklist.html W3C's website].<br> |
| − | Priority 1 Checkpoints<br> | + | Priority 1 Checkpoints<br> |
{| width="80%" cellspacing="1" cellpadding="1" border="1" | {| width="80%" cellspacing="1" cellpadding="1" border="1" | ||
|- | |- | ||
| − | + | ! colspan="3" | In General (Priority 1)<br> | |
|- | |- | ||
| − | | 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.<br> | + | | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-text-equivalent 1.1] Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.<br> |
| − | | Yes<br> | + | | Yes<br> |
| Important images, such as toolbar buttons and frequently used smiley icons, are provided with screenreader accessible alternate text.<br> | | Important images, such as toolbar buttons and frequently used smiley icons, are provided with screenreader accessible alternate text.<br> | ||
|- | |- | ||
| − | | <br> | + | | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-color-convey 2.1] Ensure that all information conveyed with color is also available without color, for example from context or markup. <br> |
| − | | <br> | + | | Yes<br> |
| − | | <br> | + | | Toolbar buttons will appear as textual buttons in Windows high contrast mode. Selection of text and background colors is still possible with textual labels in the color selection panels. <br> |
|- | |- | ||
| − | | <br> | + | | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-identify-changes 4.1] Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). <br> |
| − | | <br> | + | | No<br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-order-style-sheets 6.1] Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.<br> |
| − | | <br> | + | | Yes<br> |
| − | | <br> | + | | The editor and its dialogs are still usable without cascading style sheets. Toolbar buttons appear as textual links without CSS. <br> |
|- | |- | ||
| − | | <br> | + | | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-dynamic-source 6.2] Ensure that equivalents for dynamic content are updated when the dynamic content changes. <br> |
| − | | <br> | + | | Yes<br> |
| − | | <br> | + | | |
| + | *IFrames in the editor, such as the WYSIWYG editing area and combo boxes, are given screenreader accessible labels. <br> | ||
| + | *An equivalent text-only page with a <textarea> element can be created by not activating CKEditor's replace API, if JavaScript is not an option.<br> | ||
| + | |||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| <br> | | <br> | ||
|} | |} | ||
<br> | <br> | ||
Revision as of 01:43, 20 May 2009
The full WCAG 1.0 checklist can be viewed in W3C's website.
Priority 1 Checkpoints
| In General (Priority 1) | ||
|---|---|---|
| 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. |
Yes |
Important images, such as toolbar buttons and frequently used smiley icons, are provided with screenreader accessible alternate text. |
| 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. |
Yes |
Toolbar buttons will appear as textual buttons in Windows high contrast mode. Selection of text and background colors is still possible with textual labels in the color selection panels. |
| 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). |
No |
|
| 6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. |
Yes |
The editor and its dialogs are still usable without cascading style sheets. Toolbar buttons appear as textual links without CSS. |
| 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. |
Yes |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|