| Line 1: | Line 1: | ||
The complete checklist with developer guidelines can be found at [http://www-03.ibm.com/able/guidelines/web/accessweb.html IBM's website].<br> | The complete checklist with developer guidelines can be found at [http://www-03.ibm.com/able/guidelines/web/accessweb.html IBM's website].<br> | ||
| − | |||
| − | |||
{| width="80%" cellspacing="1" cellpadding="1" border="1" | {| width="80%" cellspacing="1" cellpadding="1" border="1" | ||
| Line 35: | Line 33: | ||
| 7. Forms | | 7. Forms | ||
| Yes | | Yes | ||
| − | | | + | | The editor is designed to let screenreaders read out its name. |
|- | |- | ||
| 8. Skip to main content | | 8. Skip to main content | ||
| Yes | | Yes | ||
| − | | | + | | Pressing tab and shift-tab to change focus to the editor from outside will put the focus directly into the editing area, instead of other focusable elements of the editor (e.g. toolbar buttons). |
|- | |- | ||
| 9. Frames | | 9. Frames | ||
| Yes | | Yes | ||
| − | | | + | | IFrames in the editor, such as the WYSIWYG editing area and combo boxes, are given screenreader accessible labels. |
|- | |- | ||
| 10. Table headers | | 10. Table headers | ||
| NA | | NA | ||
| − | | | + | | There are no table headers in the editor UI. |
|- | |- | ||
| 11. Cascading style sheets | | 11. Cascading style sheets | ||
| Yes | | Yes | ||
| − | | | + | | The editor and its dialogs are still usable without cascading style sheets. Toolbar buttons appear as textual links without CSS. |
|- | |- | ||
| 12. Color and contrast | | 12. Color and contrast | ||
| Yes | | 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. |
|- | |- | ||
| 13. Blinking, moving or flickering content | | 13. Blinking, moving or flickering content | ||
| NA | | NA | ||
| − | | | + | | There are no blinking or flickering contents in the editor. |
|- | |- | ||
| 14. Timed responses | | 14. Timed responses | ||
Revision as of 09:41, 19 May 2009
The complete checklist with developer guidelines can be found at IBM's website.
| Checkpoint | Yes/No/Planned/NA | Comments |
| 1. Images and animations | Yes | Important images such as toolbar icons are readable in screenreaders. Less important images such as object placeholders and infrequently used smiley icons are given alt="". |
| 2. Image maps | NA | There are no image maps in the editor. |
| 3. Graphs and charts | NA | There are no graphs and charts in the editor. |
| 4. Multimedia | NA | There are no video or audio contents in the editor. |
| 5. Scripts | Yes | Most or all functions in the editor are accessible from keyboard. |
| 6. Applets, plugins and non-HTML content | Planned | There is no alternative text for plugin placeholders in the editor yet. |
| 7. Forms | Yes | The editor is designed to let screenreaders read out its name. |
| 8. Skip to main content | Yes | Pressing tab and shift-tab to change focus to the editor from outside will put the focus directly into the editing area, instead of other focusable elements of the editor (e.g. toolbar buttons). |
| 9. Frames | Yes | IFrames in the editor, such as the WYSIWYG editing area and combo boxes, are given screenreader accessible labels. |
| 10. Table headers | NA | There are no table headers in the editor UI. |
| 11. Cascading style sheets | Yes | The editor and its dialogs are still usable without cascading style sheets. Toolbar buttons appear as textual links without CSS. |
| 12. Color and contrast | 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. |
| 13. Blinking, moving or flickering content | NA | There are no blinking or flickering contents in the editor. |
| 14. Timed responses | NA | |
| 15. Text-only page | Yes | |
| 16. Verify accessibility | No |