Sakai 2.8 CKEditor Firefox Accessibility Toolbars Protocol Results
Instructor View
Test Details
Browser/OS Used: |
Firefox 3.6.12, IE 8, Windows 7 |
Sakai Tool: |
CKEditor |
Page(s) Tested: |
Assignments - Add new assignment, |
Date: |
1/5/2010 |
QA Server: |
qa1-nl (sakai_2-8-0 Beta 2 using MySQL 5/InnoDB, Java 1.6.0_17 amd64 ) |
Accessibility Problems and Recommended Solutions
Subject |
Results |
Recommendations |
Priority |
JIRAs |
---|---|---|---|---|
Links |
Clicking on links to the CKEditor site (http://ckeditor.comin the CKEditor About Dialog box results in the CKEditor.com site replacing the tool's iframe content with the site's content. |
If keeping these links, have them open in new windows. |
Major |
|
Images |
|
|
|
|
Page Structure / Markup |
|
|
|
|
Page Structure / Markup |
|
 |
|
|
Page Structure / Markup |
 |
 |
|
|
Page Structure / Markup |
 |
|
|
|
Page Structure / Markup |
 |
 |
|
|
Page Structure / Markup |
 |
|
|
 |
Access Keys / Tab Order |
CKEditor uses hot keys to give keyboard access to the CKEditor toolbars (Alt+F10), and for editing features like bolding text (Ctrl+B), etc. Obviously, there is no standard for a hot key to give access to the toolbar (the Alt+F10 combo). Unfortunately there is no way for the user to discover the Alt+F10 key combination required for accessing the toolbars, or the other available keyboard shortcuts as they are not advertised. |
The pages which rely on rich text editor functionality should contain a link to an accessible page which contains help text, documentation and keyboard shortcuts for people who are using the WYSIWYG editor without a mouse, using a screen reader, etc. |
|
 |
Frame Titles |
|
|
|
 |
Style sheets / Linearization |
|
|
|
 |
Text Zoom |
|
|
|
 |
Tab Order |
|
|
|
 |
Tab Order |
|
 |
|
 |
Functionality |
|
|
|
 |
Color |
 |
|
|
|
Color |
|
|
|
|
FAE Results |
|
|
|
 |
Priority Definitions
- Critical: Issue will keep some/all users from being able to use this tool.
- Major: Issue will cause significant difficulty to some/all users and should be revised.
- Minor: Tool can be used successfully, but functionality will be significantly improved by fixing issue.
- Trivial: Indicates that this issue has a relatively minor impact.