Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-41490 Accessibility: Parent jira for CKEditor keyboard and screen reader accessibility issues
  3. SAK-41491

Accessibility: CKEditor: Provide contextual keyboard help for all instances of CKEditor

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: OPEN
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Test Plan:
      Hide

      Test plan to be determined once desired behavior is discussed/decided. Will need to include testing multiple tools, especially Tests & Quizzes, where many editors appear on the same page.

      Show
      Test plan to be determined once desired behavior is discussed/decided. Will need to include testing multiple tools, especially Tests & Quizzes, where many editors appear on the same page.

      Description

      One of the major issues raised in analyzing Sakai Accessibility was difficulty using CKEditor with a keyboard and/or screen reader.

      The problem is that keyboard shortcuts/commands are needed to be able to access the CKEditor menu.  This is not apparent to the user, so appropriate contextual help is needed.

      Karen McPhaul has suggested adding a keyboard icon (similar to the one in Gradebook) above every CKEditor in the Sakai UI.

      Of note, this is similar to how Canvas approaches the issue of keyboard access for their editor: https://community.canvaslms.com/thread/18102-shortcut-keys

      The suggested icon should be in the tab order before the user enters the editor's text area, and when selected, open an appropriately keyboard- and screen reader-accessible modal dialog showing the necessary keyboard commands for the editor.

      Below is a mock-up image showing a proposed location for the icon.

      I suggest the following text alternative: Open dialog to show Rich-Text Editor hotkeys. I will raise this suggestion and discuss potential wording for the dialog at the next Accessibility Working Group meeting.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  maintenanceteam Core Team
                  Reporter:
                  rainribbon Tiffany Stull
                  Votes:
                  6 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                    Dates

                    Created:
                    Updated:

                      Git Integration