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 two levels of accessibility features we aim to provide with V3:

  • Making the editor usable by people with disabilities.
  • Ensuring that accessibility features can be introduced in the contents produced with the editor, guaranteeing and enforcing the minimum accessibility level in the contents.


The first and most practical way to ensure accessibility in both the above aspects is by following the rules and requirements defined by the common standard available for web applications.

We have chosen two of the most notable standards as those we'll be working to be compliant to:

Apart from the real accessibility needs present in the world, compliance to these two standards is a requirement for many companies and public agencies.


Resources permitting, we'll be working to certify our accessibility compliance, making the results of our efforts tangible and trustable.

Not a certification tool, but for Section 508, a common communication approach for compliance is the Voluntary Product Accessibility Template (VPAT).

The Real World

Standards are good, at the bureaucratic point of view. But our main purpose is really making our editor effectively usable by people with disabilities. The most important thing is giving our end users a wonderful editing experience, not only satisfying the checklists defined by the standards.

We invite accessibility experts and end users to participate, helping us providing the dreamed accessibility solution for browser based editing.


[TODO: List the features we need to provide for accessibility and standards compliance]

This page was last edited on 20 May 2009, at 08:46.