ATAG & Drupal 8
Making it easier to produce a11y content!
Drupal 8 Core Accessibility Maintainer
Spearheading accessibility improvements since
OpenConcept Consulting Inc.
Authoring Tool A11y Guidelines
ATAG is well defined, but still getting baked.
W3C Working Draft 7 November 2013
Drupal 8’s also still a work in progress.
Expected to release in 2015.
Why ATAG Matters
As much as designers, themers & developers
might want …. less technical people are
usually going to be producing most of the
content of a website.
If a site is going to be accessible...
The UN Convention on the Rights of
What is Content Anyways?
Articles, Stories, Blogs, Articles, FAQ’s…
Anything that convey’s meaning between the
website & the user.
Images, videos, charts, tables...
How Can a CMS Help?
❖ Data analysis
❖ Simple Checks
Most user edited content will be coming
through CKEditor, so putting pressure on
their bugs is important!
IBM is leading the accessibility improvements
for CKEditor for both WCAG & ATAG.
When is alt=”” appropriate
HTML5 support for longdesc
Knowing how to use it properly for AT
It’s really hard for a machine to correctly read
(a screen reader) a mis-spelled word, or
click on a misspelled link using voice
commands (Dragon Naturally Speaking)
Also usually bad for SEO.
Readability & Broken HTML
There are open source programs to assess
Several filters address broken HTML, sadly,
none seem to be keeping up with HTML5.
ATAG Parts A & B
A) Make the editing interface accessible
B) Essentially WCAG P.O.U.R. - Support the
Production of Accessible Content
A3 Editing-views are operable
❖ Provide keyboard access to authoring features
❖ Provide authors with enough time
❖ Help authors avoid flashing content that could cause seizures
➢ Slow animations and motion sickness -
❖ Enhance navigation and editing via content structure
❖ Provide text search of the content
❖ Allow users to manage preference settings
❖ Ensure that previews are at least as accessible as user agents - (Coming
A4 Editing-views are understandable
Help authors avoid and correct mistakes
➢ Fixing broken HTML
➢ Highly structured semantic content
➢ Required images
Document the user interface, including all
accessibility features - (Not yet)
B1 Auto-Processes & A11y Content
❖ Ensure that automatically-specified content
is accessible (CKEditor)
➢ Drupal 8 is doing pretty well.
❖ Ensure that accessibility information is
➢ Cut/Paste from Word
B2 Support Content Authors
❖ Ensure that accessible content production is possible
❖ Guide authors to produce accessible content
❖ Assist authors with managing alternative content for
❖ Assist with accessible templates
❖ Assist with accessible pre-authored content
B3 Support A11y of Existing Content
❖ Assist authors in checking for accessibility
❖ Assist authors in repairing accessibility
B4 Promote Accessibility Features
❖ Ensure the availability of features that
support the production of accessible content
❖ Ensure that documentation promotes the
production of accessible content
Accessibility is complicated… Making it easier
to create accessible content is more
complicated… But by working together we
can make it easier for everyone to work
This presentation will be at http://openconcept.ca/blog
OpenConcept Consulting Inc http://openconcept.ca