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.

The full WCAG 1.0 checklist can be viewed in W3C's website.

Priority 1 Checkpoints

In General (Priority 1)
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.
Important images, such as toolbar buttons and frequently used smiley icons, are provided with screenreader accessible alternate text.
2.1 Ensure 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.
4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).

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.
The editor and its dialogs are still usable without cascading style sheets. Toolbar buttons appear as textual links without CSS.
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.
  • 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.
7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.
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.
14.1 Use the clearest and simplest language appropriate for a site's content.
Accessible labels are kept as concise and simple simple as possible.
And if you use images and image maps (Priority 1)
1.2 Provide redundant text links for each active region of a server-side image map.
There are no image maps in the editor.
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.
There are no image maps in the editor.
And if you use tables (Priority 1)

And if you use frames (Priority 1)

And if you use applets and scripts (Priority 1)

And if you use multimedia (Priority 1)

And if all else fails (Priority 1)