Section 508 Amendment to the Rehabilitation Act of 1973

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

The Voluntary Product Accessibility Template (VPAT) for Section 508 can be retrived from the Department of State IRM Program for Accessible Computer/Communication Technology (IMPACT).

Section 1194.22 Web-based Internet information and applications – Detail

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. Most UI elements (e.g. toolbar buttons, dialog tabs) in the editor come with screenreader accessible labels.

(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). The editor UI does not utilize any plugins or applets.

(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.
  • When the editor is embedded inside a form, tab order works with the editor like any other regular form input.
  • The editor is designed to let screenreaders read out its name.

(o) A method shall be provided that permits users to skip repetitive navigation links. 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).

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. N/A
There are no time outs in UI elements of the editor.
This page was last edited on 13 December 2011, at 12:38.