Web Content Accessibility Guidelines

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.

There are no data tables in the editor UI.Tables are used for layout purpose only.

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.

And if you use frames (Priority 1)

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.

And if you use applets and scripts (Priority 1)

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.

And if you use multimedia (Priority 1)

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.

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.

And if all else fails (Priority 1)

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

In General (Priority 2)

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.

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.