Accessibility lucked out

Drupal 8 is both the best and worst that could happen to accessibility in our CMS. We worked hard to make an accessible Drupal 7. Now with Drupal 8, a huge amount of work has been done to make all the new and fancy features accessible, as well as provide APIs for developers to help make their features accessible. 

This session will reframe how accessibility should be approached, show what is the bare minimum to do in order to make a website accessible, how to check that a website is actually accessibility — hint: smartphones are a blessing — and tell you what can be used in Drupal core to make your features accessible. It's not as hard as it looks, and in the usual case vastly easier than you'd expect. In general accessibility is prioritized (if at all) after testing, and we all know what usually happens to testing in a real life project, you can change that.

Meanwhile, with a cruel twist of fate, the rising popularity of decoupled Drupal is once again exposing projects to an abysimal accessibility state. This session is also meant as a ressource for people implementing decoupled Drupal, to make sure all the work done in Drupal can be reused in that type of projects.