The Voluntary Product Accessibility Template (VPAT) for Section 508 can be retrived from [http://www.access-star.org/ITI-VPAT-v1.3.html access-star.org]. 

== Section 1194.22 Web-based Internet information and applications – Detail ==

{| width="100%" cellspacing="1" cellpadding="1" border="1"
|-
! Criteria
! Supporting Features
! Remarks and Explanations
|-
| (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
| 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="". 
| 
|-
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
| N/A 
| There are no video or audio contents in the editor. 
|-
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
| 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. 
| 
|-
| (d) Documents shall be organized so they are readable without requiring an associated style sheet.
| The editor and its dialogs are still usable without cascading style sheets. Toolbar buttons appear as textual links without CSS. 
| 
|-
| (e) Redundant text links shall be provided for each active region of a server-side image map.
| N/A 
| There are no image maps in the editor. 
|-
| (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
| N/A 
| There are no image maps in the editor. 
|-
| (g) Row and column headers shall be identified for data tables.
| N/A 
| There are no data tables in the editor UI.Tables are used for layout purpose only. 
|-
| (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
| N/A 
| There are no data tables in the editor UI.Tables are used for layout purpose only. 
|-
| (i) Frames shall be titled with text that facilitates frame identification and navigation
| IFrames in the editor, such as the WYSIWYG editing area and combo boxes, are given screenreader accessible labels. 
| 
|-
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
| N/A 
| 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. 
|-
| (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
| 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. 
| 
|-
| (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.
| 
| 
|-
| (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
| 
| 
|-
| (n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
| 
| 
|-
| (o) A method shall be provided that permits users to skip repetitive navigation links.
| 
| 
|-
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
| 
| 
|}

2009-05-20T01:44:45Z

Martinkou:

The full WCAG 1.0 checklist can be viewed in [http://www.w3.org/TR/WCAG10/full-checklist.html W3C's website]. 

== Priority 1 Checkpoints ==

{| width="80%" cellspacing="1" cellpadding="1" border="1"
|-
! colspan="3" | In General (Priority 1) 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-text-equivalent 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. 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-color-convey 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. 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-identify-changes 4.1] Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). 
| No 
| 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-order-style-sheets 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. 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-dynamic-source 6.2] Ensure that equivalents for dynamic content are updated when the dynamic content changes. 
| Yes 
|
*IFrames in the editor, such as the WYSIWYG editing area and combo boxes, are given screenreader accessible labels. 
*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. 

|-
| [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. 
| 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. 
|-
| [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. 
| Yes 
| Accessible labels are kept as concise and simple simple as possible. 
|-
! colspan="3" | And if you use images and image maps (Priority 1) 
|-
| [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. 
| NA 
| There are no image maps in the editor. 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-client-side-maps 9.1] Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. 
| NA 
| There are no image maps in the editor. 
|-
! colspan="3" | And if you use tables (Priority 1) 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-table-headers 5.1] For data tables, identify row and column headers. 
| NA 
| There are no data tables in the editor UI.Tables are used for layout purpose only. 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-table-structure 5.2] For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. 
| NA 
| There are no data tables in the editor UI.Tables are used for layout purpose only. 
|-
! colspan="3" | And if you use frames (Priority 1) 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-frame-titles 12.1] Title each frame to facilitate frame identification and navigation. 
| Yes 
| IFrames in the editor, such as the WYSIWYG editing area and combo boxes, are given screenreader accessible labels. 
|-
! colspan="3" | And if you use applets and scripts (Priority 1) 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-scripts 6.3] Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible 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. 
|-
! colspan="3" | And if you use multimedia (Priority 1) 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-auditory-descriptions 1.3] Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. 
| NA 
| There are no video or audio contents in the editor. 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-synchronize-equivalents 1.4] For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. 
| NA 
| There are no video or audio contents in the editor. 
|-
! colspan="3" | And if all else fails (Priority 1) 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-alt-pages 11.4] If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) 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. 
|}

== Priority 2 Checkpoints ==

{| width="80%" cellspacing="1" cellpadding="1" border="1"
|-
! colspan="3" | In General (Priority 2)
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-color-contrast 2.2] Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text]. 
| Yes 
|
*Image elements in the editor UI are designed with good contrast to insure visibility in black and white screens. 
*Textual elements in the editor UI have good contrast against the background color. 

|-
| 3.1 When an appropriate markup language exists, use markup rather than images to convey information. 
| 
| 
|-
| 3.2 Create documents that validate to published formal grammars. 
| 
| 
|-
| 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. 
| 
| 
|-
| 3.5 Use header elements to convey document structure and use them according to specification. 
| 
| 
|-
| 3.6 Mark up lists and list items properly. 
| 
| 
|-
| 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. 
| 
| 
|-
| 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. 
| 
| 
|-
| 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). 
| 
| 
|-
| 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. 
| 
| 
|-
| 7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. 
| 
| 
|-
| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-avoid-pop-ups 10.1] Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. 
| Yes 
| All dialogs in the editor UI are floating dialogs displayed within the same page. 
|-
| 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. 
| 
| 
|-
| 11.2 Avoid deprecated features of W3C technologies. 
| 
| 
|-
| 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. 
| 
| 
|-
| 13.1 Clearly identify the target of each link. 
| 
| 
|-
| 13.2 Provide metadata to add semantic information to pages and sites. 
| 
| 
|-
| 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). 
| 
| 
|-
| 13.4 Use navigation mechanisms in a consistent manner. 
| 
| 
|-
! colspan="3" | And if you use tables (Priority 2)
|-
| 5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). 
| 
| 
|-
| 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. 
| 
| 
|-
! colspan="3" | And if you use frames (Priority 2)
|-
| 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. 
| 
| 
|-
! colspan="3" | And if you use forms (Priority 2)
|-
| 10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. 
| 
| 
|-
| 12.4 Associate labels explicitly with their controls. 
| 
| 
|-
! colspan="3" | And if you use applets and scripts (Priority 2)
|-
| 6.4 For scripts and applets, ensure that event handlers are input device-independent. 
| 
| 
|-
| 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. 
| 
| 
|-
| 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.] 
| 
| 
|-
| 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. 
| 
| 
|-
| 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. 
| 
| 
|}

CKEditor 3.x/Accessibility Compliance/Web Content Accessibility Guidelines

2009-05-20T01:25:48Z

Martinkou:

CKEditor 3.x/Accessibility Compliance/Web Content Accessibility Guidelines

2009-05-20T01:17:11Z

Martinkou:

CKEditor 3.x/Accessibility Compliance/Web Content Accessibility Guidelines

2009-05-20T01:11:50Z

Martinkou:

2009-05-20T00:43:41Z

Martinkou:

Martinkou:

CKEditor 3 is designed with people who have disabilities in mind. In addition to be usable with a mouse, a keyboard and a monitor; CKEditor is usable with a keyboard and a screenreader as well. JAWS with IE7 and JAWS with Firefox 3 are currently supported.

== Basic Navigation ==

*Tab and Shift+Tab To move into and out of the editor among other form elements, press tab and shift+tab. On supported browser and screenreader combinations, the editor should behave just like any other form elements in respect to tab and shift+tab key presses. One exception to this rule is when config.tabSpaces is set to a non-zero value. In this case, if the user presses tab from inside the editor, spaces will be added to the editing area, and the focus will not be moved out of the editing area. Shift-tab would still work as expected when config.tabSpaces is set to a non-zero value.
*Alt+F10 Pressing Alt+F10 when the editing area is focused will move the focus to the editor toolbar.
*Shift+F10 or Ctrl+Shift+F10 Pressing Shift+F10 or Ctrl+Shift+F10 (in cases where Shift+F10 does not work), will open the context menu inside the editing area.
*Alt+F11 Pressing Alt+F11 will put focus to the element path bar, usually at the bottom of the editor. While the element path bar is being focused, pressing tab and shift+tab will select HTML elements that are parents of the current element. Pressing Esc will move the focus back to the editing area without changing selection; while pressing Enter will select the element in the editing area.

== Navigating Toolbar ==

*Tab, Shift+Tab, Left Arrow and Right Arrow Once the toolbar is focused by Alt+F10 from the editing area, Tab and Shift+tab will move focus forward and backward among toolbar items. Toolbar item focus is cyclic so going backwards from the first item will put focus to the last item, and vice versa. Left Arrow and Right Arrow works in the same manner as Tab and Shift+Tab.
*Enter and Esc Pressing Esc will put the focus back to the editing area without executing any commands. Pressing Enter will activiate the selected toolbar item.

== Navigating Dialogs ==

*Tab and Shift+Tab Pressing Tab and Shift+Tab when dialog tabs are not focused will move the focus among input element in the dialog; when a dialog tab is focused, Tab and Shift+Tab will cycle through tab pages in the dialog. Focus order in dialogs is cyclic so when the first tab or first input elements is focused and Shift+Tab is pressed, then the last tab or last input element will get the focus. Dialog buttons count as input elements as well.
*Left Arrow and Right Arrow When a dialog tab is focused, Left Arrow and Rigth Arrow can also be used to cycle between tabs like Tab and Shift+Tab.
*Alt+F10 Pressing Alt+F10 in a dialog will put focus to the currently active tab.
*Enter and Esc Pressing Esc in a dialog is equivalent to pressing the Cancel button or the Close button. Pressing Enter in a dialog when a single-line text input is at focus is equivalent to pressing the OK button. Pressing Enter in a dialog when a dialog tab is focused puts focus back to the first input element inside that tab page.

== Navigating Context Menus ==

*Tab, Shift+Tab, Down Arrow and Up Arrow When a context menu is opened, press Tab to cycle through menu items forward, Shift+Tab to cycle backwards. Down Arrow and Up Arrow work in the same manner as Tab and Shift+Tab respectively.
*Enter and Esc Press Enter to activate a menu item or open a sub-menu. Press close a context menu without executing any command.

== Navigating Style Combo Boxes ==

*Tab, Shift+Tab, Down Arrow and Up Arrow Press Tab and Shift+Tab to cycle through items in a combo box forward and backwards, respectively. Down Arrow and Up Arrow work in the same manner as Tab and Shift+Tab.
*Enter and Esc Press Enter to activate the selected item in a combo box and put the focus back to the editing area. Press Esc to close the combo box without executing any command, and put the focus back to the toolbar.

== Navigating Color Selection Boxes ==

*Tab, Shift+Tab, Left Arrow and Right Arrow Press Tab and Shift+Tab to cycle through colors forward and backwards, respectively. Down Arrow and Up Arrow work in the same manner as Tab and Shift+Tab.
*Enter and Esc Press Enter to apply the selected color to the current selection in the editing area. Enter puts the focus back to the editing area as well. Press Esc to close the color selection box and put focus back to the toolbar.

== Editor Hotkeys ==

Here is a list of hotkeys that you can use inside the editing area in addition to the more common text editing keyboard commands (i.e. arrow keys to move the caret, end to move to the end of line, etc.).

*Ctrl+Z Undo command.
*Ctrl+Y and Ctrl+Shift+Z Redo command.
*Ctrl+L Open link dialog.
*Ctrl+B Bold command.
*Ctrl+I Italics command.
*Ctrl+U Underline command.
*Ctrl+C or Ctrl+Insert Copy.
*Ctrl+V or Shift+Insert Paste.
*Ctrl+X or Shift+Delete Cut.
*Ctrl+Left or Ctrl+Right Move to the previous or next word.
*Ctrl+Backspace Remove the previous word.
*Ctrl+Delete Remove the current word.
*Shift+Enter Create a new line in the same paragraph or list item. 

== JAWS ==

*Editing Mode vs. Non-editing Mode JAWS has the distinction between editing mode and non-editing mode for text boxes and rich text areas. When JAWS is entering editing mode, a high pitched 'pop' sound is played to notify the user of the mode switch. Similarly, when JAWS is entering non-editing mode, a lower pitched 'pop' sound is played. It is up to JAWS to decide whether to put a text box or a rich text area to editing mode on the initial focus. When it happens that JAWS has put the initial focus to CKEditor in non-editing mode, the user will find that he/she cannot type into the editor, and no 'pop' sound is played when focus was put into the editing area. To fix that, simply press Enter to switch JAWS to editing mode, and a high pitched 'pop' sound should be played. Pressing Esc inside CKEditor will switch JAWS to non-editing mode, along with a lower pitched 'pop' sound to indicate the mode switch.
*Refreshing the Virtual Cursor JAWS keeps an internal model of the browser's view, and along with it, a virtual cursor, to facilitate reading of the contents in a web browser. The internal model kept by JAWS, however, is not always in sync with the displayed contents in the browser window. This is especially true for dynamically generated web contents written in JavaScript, which CKEditor depends on. When JAWS's virtual cursor is out-of-sync with the browser's displayed contents, the user will be unable to move correctly among the web page's contents. The user will also find that JAWS's voice reading out unpredictable garbage from the web browser - e.g. it may be reading out the raw HTML code in the web page, or it may be reading out the same element over and over despite the user's actions to move the virtual cursor away from that element. To refresh JAWS's internal model and to keep the virtual cursor back in sync with the browser, the user will need to press Insert+Esc. In cases where even Insert+Esc fails to refresh JAWS's virtual cursor correctly, the user can press Insert+Z twice, slowly, to disable and re-enable the virtual cursor. There are a few points in CKEditor usage in which JAWS will get out-of-sync with the browser window contents:

#When an editor is newly created in the middle of a browsing session.
#When a dialog is opened.
#When a dialog is closed.

In all of the above three events, it is recommended that the user press Insert+Esc to keep JAWS's virtual cursor in sync with the browser display.

*Arrow Keys Arrow keys have special meaning in JAWS when virtual cursor is mode is on. Arrow hotkeys (like left arrow and right arrow for cycling through toolbar items) will stop working when JAWS is opened and in virtual cursor mode. Equivalent hotkeys like Tab and Shift+Tab should be used instead.

CKEditor 3.x/Accessibility

2009-04-14T07:46:32Z

Martinkou:

CKEditor 3 is designed with people who have disabilities in mind. In addition to be usable with a mouse, a keyboard and a monitor; CKEditor is usable with a keyboard and a screenreader as well. JAWS with IE7 and JAWS with Firefox 3 are currently supported.

== Basic Navigation ==

*Tab and Shift+Tab To move into and out of the editor among other form elements, press tab and shift+tab. On supported browser and screenreader combinations, the editor should behave just like any other form elements in respect to tab and shift+tab key presses. One exception to this rule is when config.tabSpaces is set to a non-zero value. In this case, if the user presses tab from inside the editor, spaces will be added to the editing area, and the focus will not be moved out of the editing area. Shift-tab would still work as expected when config.tabSpaces is set to a non-zero value.
*Alt+F10 Pressing Alt+F10 when the editing area is focused will move the focus to the editor toolbar.
*Shift+F10 or Ctrl+Shift+F10 Pressing Shift+F10 or Ctrl+Shift+F10 (in cases where Shift+F10 does not work), will open the context menu inside the editing area.
*Alt+F11 Pressing Alt+F11 will put focus to the element path bar, usually at the bottom of the editor. While the element path bar is being focused, pressing tab and shift+tab will select HTML elements that are parents of the current element. Pressing Esc will move the focus back to the editing area without changing selection; while pressing Enter will select the element in the editing area.

== Navigating Toolbar ==

*Tab, Shift+Tab, Left Arrow and Right Arrow Once the toolbar is focused by Alt+F10 from the editing area, Tab and Shift+tab will move focus forward and backward among toolbar items. Toolbar item focus is cyclic so going backwards from the first item will put focus to the last item, and vice versa. Left Arrow and Right Arrow works in the same manner as Tab and Shift+Tab.
*Enter and Esc Pressing Esc will put the focus back to the editing area without executing any commands. Pressing Enter will activiate the selected toolbar item.

== Navigating Dialogs ==

*Tab and Shift+Tab Pressing Tab and Shift+Tab when dialog tabs are not focused will move the focus among input element in the dialog; when a dialog tab is focused, Tab and Shift+Tab will cycle through tab pages in the dialog. Focus order in dialogs is cyclic so when the first tab or first input elements is focused and Shift+Tab is pressed, then the last tab or last input element will get the focus. Dialog buttons count as input elements as well.
*Left Arrow and Right Arrow When a dialog tab is focused, Left Arrow and Rigth Arrow can also be used to cycle between tabs like Tab and Shift+Tab.
*Alt+F10 Pressing Alt+F10 in a dialog will put focus to the currently active tab.
*Enter and Esc Pressing Esc in a dialog is equivalent to pressing the Cancel button or the Close button. Pressing Enter in a dialog when a single-line text input is at focus is equivalent to pressing the OK button. Pressing Enter in a dialog when a dialog tab is focused puts focus back to the first input element inside that tab page.

== Navigating Context Menus ==

*Tab, Shift+Tab, Down Arrow and Up Arrow When a context menu is opened, press Tab to cycle through menu items forward, Shift+Tab to cycle backwards. Down Arrow and Up Arrow work in the same manner as Tab and Shift+Tab respectively.
*Enter and Esc Press Enter to activate a menu item or open a sub-menu. Press close a context menu without executing any command.

== Navigating Style Combo Boxes ==

*Tab, Shift+Tab, Down Arrow and Up Arrow Press Tab and Shift+Tab to cycle through items in a combo box forward and backwards, respectively. Down Arrow and Up Arrow work in the same manner as Tab and Shift+Tab.
*Enter and Esc Press Enter to activate the selected item in a combo box and put the focus back to the editing area. Press Esc to close the combo box without executing any command, and put the focus back to the toolbar.

== Editor Hotkeys ==

Here is a list of hotkeys that you can use inside the editing area in addition to the more common text editing keyboard commands (i.e. arrow keys to move the caret, end to move to the end of line, etc.).

*Ctrl+Z Undo command.
*Ctrl+Y and Ctrl+Shift+Z Redo command.
*Ctrl+L Open link dialog.
*Ctrl+B Bold command.
*Ctrl+I Italics command.
*Ctrl+U Underline command.
*Ctrl+C or Ctrl+Insert Copy.
*Ctrl+V or Shift+Insert Paste.
*Ctrl+X or Shift+Delete Cut.
*Ctrl+Left or Ctrl+Right Move to the previous or next word.
*Ctrl+Backspace Remove the previous word.
*Ctrl+Delete Remove the current word.
*Shift+Enter Create a new line in the same paragraph or list item. 

== JAWS ==

*Editing Mode vs. Non-editing Mode JAWS has the distinction between editing mode and non-editing mode for text boxes and rich text areas. When JAWS is entering editing mode, a high pitched 'pop' sound is played to notify the user of the mode switch. Similarly, when JAWS is entering non-editing mode, a lower pitched 'pop' sound is played. It is up to JAWS to decide whether to put a text box or a rich text area to editing mode on the initial focus. When it happens that JAWS has put the initial focus to CKEditor in non-editing mode, the user will find that he/she cannot type into the editor, and no 'pop' sound is played when focus was put into the editing area. To fix that, simply press Enter to switch JAWS to editing mode, and a high pitched 'pop' sound should be played. Pressing Esc inside CKEditor will switch JAWS to non-editing mode, along with a lower pitched 'pop' sound to indicate the mode switch.
*Refreshing the Virtual Cursor JAWS keeps an internal model of the browser's view, and along with it, a virtual cursor, to facilitate reading of the contents in a web browser. The internal model kept by JAWS, however, is not always in sync with the displayed contents in the browser window. This is especially true for dynamically generated web contents written in JavaScript, which CKEditor depends on. When JAWS's virtual cursor is out-of-sync with the browser's displayed contents, the user will be unable to move correctly among the web page's contents. The user will also find that JAWS's voice reading out unpredictable garbage from the web browser - e.g. it may be reading out the raw HTML code in the web page, or it may be reading out the same element over and over despite the user's actions to move the virtual cursor away from that element. To refresh JAWS's internal model and to keep the virtual cursor back in sync with the browser, the user will need to press Insert+Esc. In cases where even Insert+Esc fails to refresh JAWS's virtual cursor correctly, the user can press Insert+Z twice, slowly, to disable and re-enable the virtual cursor. There are a few points in CKEditor usage in which JAWS will get out-of-sync with the browser window contents:

#When an editor is newly created in the middle of a browsing session.
#When a dialog is opened.
#When a dialog is closed.

In all of the above three events, it is recommended that the user press Insert+Esc to keep JAWS's virtual cursor in sync with the browser display.

*Arrow Keys Arrow keys have special meaning in JAWS when virtual cursor is mode is on. Arrow hotkeys (like left arrow and right arrow for cycling through toolbar items) will stop working when JAWS is opened and in virtual cursor mode. Equivalent hotkeys like Tab and Shift+Tab should be used instead.