(New page: {| width="80%" cellspacing="1" cellpadding="1" border="1" |- | Checkpoint | Yes/No/Planned/NA | Comments |- | 1. Images and animations | | |- | 2. Image maps | | |- | 3. Graphs and cha...) |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {| width=" | + | 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="100%" class="datatable" | ||
|- | |- | ||
| − | + | ! Checkpoint | |
| − | + | ! Yes/No/Planned/NA | |
| − | + | ! Comments | |
|- | |- | ||
| − | | 1. Images and animations | + | | 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 | + | | 2. Image maps |
| − | | | + | | NA |
| − | | | + | | There are no image maps in the editor. |
|- | |- | ||
| − | | 3. Graphs and charts | + | | 3. Graphs and charts |
| − | | | + | | NA |
| − | | | + | | There are no graphs and charts in the editor. |
|- | |- | ||
| − | | 4. Multimedia | + | | 4. Multimedia |
| − | | | + | | NA |
| − | | | + | | There are no video or audio contents in the editor. |
|- | |- | ||
| − | | 5. Scripts | + | | 5. Scripts |
| − | | | + | | Yes |
| − | | | + | | Most or all functions in the editor are accessible from keyboard. |
|- | |- | ||
| − | | 6. Applets, plugins and non-HTML content | + | | 6. Applets, plugins and non-HTML content |
| − | | | + | | NA |
| − | | | + | | There is no content requiring plugins or applets in the editor UI. |
|- | |- | ||
| − | | 7. Forms | + | | 7. Forms |
| − | | | + | | Yes |
| − | | | + | | The editor is designed to let screenreaders read out its name. |
|- | |- | ||
| − | | 8. Skip to main content | + | | 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 | + | | 9. Frames |
| − | | | + | | 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 |
| − | | | + | | There are no data tables in the editor UI.Tables are used for layout purpose only.<br> |
|- | |- | ||
| − | | 11. Cascading style sheets | + | | 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 | + | | 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 | + | | 13. Blinking, moving or flickering content |
| − | | | + | | 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.<br> |
|- | |- | ||
| − | | 14. Timed responses | + | | 14. Timed responses |
| − | | | + | | NA |
| − | | | + | | There are no time outs in UI elements of the editor. |
|- | |- | ||
| − | | 15. Text-only page | + | | 15. Text-only page |
| − | | | + | | Yes |
| − | | | + | | 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. |
|- | |- | ||
| − | | 16. Verify accessibility | + | | 16. Verify accessibility |
| − | | | + | | Yes |
| | | | ||
|} | |} | ||
Latest revision as of 20:40, 29 September 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 | NA | There is no content requiring plugins or applets in the editor UI. |
| 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 data tables in the editor UI.Tables are used for layout purpose only. |
| 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 | 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. Timed responses | NA | There are no time outs in UI elements of the editor. |
| 15. Text-only page | Yes | 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. |
| 16. Verify accessibility | Yes |