W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2017

Re: ATAG testing

From: Greg Gay <greggay@rogers.com>
Date: Wed, 20 Sep 2017 14:57:11 -0400
To: w3c-wai-ig@w3.org
Message-ID: <930beb19-ceee-0da9-ca58-7e835423d740@rogers.com>

On 2017-09-20 1:45 PM, Mike Gifford wrote:
> Greg, would love to have your feedback on CKEditor to see if it lives 
> up to what you were working on TinyMCE.
Hi Mike,

CKeditor has come a long way. I might even say they exceed TinyMCE a bit 
in terms of its accessibility support.

I took a quick scan. It works well with a keyboard, in fact much like 
TinyMCE does. That's good for those who happen to use both editors.  
It's fairly easy to navigate around the UI, and between the editing area 
and the toolbar and status bar.

It too, seems to be missing prompts to warn authors where they may be 
introducing a barrier (like forgetting to add alt text)

Like TinyMCE, their accessibility checker is an addon, though its free. 
I would be nice, for both editors, to include the accessibility checker 
by default.

I do like CKeditor's alt-0 for quick access to accessibility features. 
We'd originally embedded the descriptions of shortcuts into the UI of 
TinyMCE, but having them in a popup help doc I think now is a better 
approach, not having to listen to the keys announce everytime you access 
the editor.

Received on Wednesday, 20 September 2017 18:57:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 20 September 2017 18:57:34 UTC