| Line 30: | Line 30: | ||
|- | |- | ||
| − | | <br> | + | | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-avoid-flicker 7.1] Until user agents allow users to control flickering, avoid causing the screen to flicker. <br> |
| − | | <br> | + | | Yes<br> |
| − | | <br> | + | | There are no blinking or flickering contents in the editor. Moveable UI elements such as dialogs can only be moved in a smooth fashion by the user.<br> |
|- | |- | ||
| − | | <br> | + | | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-simple-and-straightforward 14.1] Use the clearest and simplest language appropriate for a site's content. <br> |
| − | | <br> | + | | Yes<br> |
| − | | <br> | + | | Accessible labels are kept as concise and simple simple as possible.<br> |
|- | |- | ||
| − | | | + | ! colspan="3" | And if you use images and image maps (Priority 1) <br> |
| − | |||
| − | |||
|- | |- | ||
| − | | <br> | + | | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-redundant-server-links 1.2] Provide redundant text links for each active region of a server-side image map. <br> |
| − | | <br> | + | | NA<br> |
| − | | <br> | + | | There are no image maps in the editor. <br> |
|- | |- | ||
| <br> | | <br> | ||
Revision as of 01:48, 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 |
|
| 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. |
Yes |
There are no blinking or flickering contents in the editor. Moveable UI elements such as dialogs can only be moved in a smooth fashion by the user. |
| 14.1 Use the clearest and simplest language appropriate for a site's content. |
Yes |
Accessible labels are kept as concise and simple simple as possible. |
| And if you use images and image maps (Priority 1) | ||
| 1.2 Provide redundant text links for each active region of a server-side image map. |
NA |
There are no image maps in the editor. |
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|