ATAG & CKEditor

[Mike Gifford]

ATAG is of course the Authoring Tool Accessibility Guidelines (ATAG) 2.0.

​http://www.w3.org/WAI/AU/CR20/ATAGintro.html

How close any system can come to meeting ATAG will very much depend on the WYSIWYG that they use.

CKEditor has been good with WCAG, but would like to have a review for how it handles some of the elements of the W3C's ATAG.

[Marek Lewandowski]

We're already doing a good job to complete part A of ATAG. As for part B (supporting accessible content creation) we're currently working on features that will enhance CKEditor output markup, making it more accessibility friendly.

I think it would be a good idea to make a deeper check for ATAG support, which would be presented in a nice, readable way. We'll discuss this idea and update the ticket. Meanwhile, I'll change issue type to "New Feature".

[Mike Gifford]

Thanks for changing the Type. Sorry about that.

ATAG is still pretty new. Lots to get our heads around.

One issue with images we ran into was just giving folks the option of a reminder for ALT rather than making it mandatory. ​https://www.drupal.org/node/2297681#comment-8973361

Kevin's published a plugin for CKEditor to help ensure the content is accessible using the Quail module, and having something like this in the Core code would be amazing: ​https://github.com/quailjs/quail-ckeditor

Lots of other ways CKEditor could be enhanced to help push along the accessible content.

Also, useful to highlight things like any scrubbed HTML that you're already doing.

Anyways, just expanding the conversation.

[Marek Lewandowski]

That's true, we might do a better job with encouraging CKEditor users to provide alt for images. We'll consider that in our content accessibility imporvement discussion.

We're already familiar with Quail project, we're keeping eye on it. It's a really cool tool Kevin and contributors had created.

We'll update ticket with more informations in next week.

[Mike Gifford]

As @AndrewEchidna said 'I would propose we require alt text for all images in CKEditor and provide a checkbox interface in cases where the editor makes a conscious decision to omit alt text - which I believe should be a rare occurrence. Checking the "Omit Alt Text" checkbox would be the editors was of specifying a null alt text be used in the markup.

This requires the editor make one extra click in the rare case that alt text is not required. Checking the box would disable the alt text input.

Utilizing this checkbox would output the null format alt="".'

I think that would provide enough of a nudge for most.

[Mike Gifford]

CKEditor has the option of using captions & expresses this properly using figure/figcpation. However on opting out for alt text there's this rule here from ​http://w3c.github.io/alt-techniques/#m6

"An image is contained within a figure element and has an associated caption provided using the figcaption element. Using an empty alt attribute hides an image from some users. If an image has a caption the image needs to be discoverable by users, otherwise a caption is present that refers to nothing for some users."

[Marek Lewandowski]

We had a meeting regarding this, and what I can tell is that we're working on a functionality that will improve the accessibility of content created with CKEditor.

We have no ETA at this moment, but stay tuned via our social pages where you will be notified of CKEditor updates.

I'll keep this ticket open, and we'll come back to it once this functionality is out.

[Mike Gifford]

This is likely going to have to get broken down into sub-issues, but thinking about ​http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/#sc_b122

B.1.2.2 Copy-Paste Inside Authoring Tool (WCAG): If the authoring tool supports copy and paste of structured content, then any accessibility information (WCAG) in the copied content is preserved when the authoring tool is both the source and destination of the copy-paste and the source and destination use the same web content technology. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)