Drupal 8 - What accessibility issues we haven't solved in Core (yet!)

Drupal 8 is the most accessible CMS framework out of the box. That said, there are many items that we wanted to get into Core, but couldn’t. This talk will highlight what we missed, what the implications are for accessibility and approaches to address these issues.

With Drupal 7 there was a lot that we couldn’t introduce because in 2011 the standards just weren’t mature enough yet. Fortunately in the Drupal 8 we were able to add HTML5, WAI-ARIA and some ATAG 2.0 support. Building on the great work done with Drupal 7 we were able to improve the interface and learn from a diverse community of users.

D8 has also seen many enhancements for keyboard only users, low vision users and people who are colour blind.
With the proliferation of screen reader devices like VoiceOver and NVDA it is even more important to make the aural interface as usable as possible. More people are using screen readers to present content in a meaningful way.

We introduced animations in Drupal 8, which can cause visually induced motion sickness for some users. We have barely scratched the surface of ATAG 2.0 AA and lack the ability to address issues like defining acronyms.

There has been almost no work done to support for voice control for users who use Dragon Naturally Speaking or Windows Speech Recognition.

The presentation will focus on these problems which we are yet to solve, but which should be a part of core libraries for every CMS.