This will be an updated version of the session I gave at Drupal Dev Days this year in Leuven.

By now we all know how to implement the basic needs for accessibility: use semantic HTML, have alt-texts for images, add styles for focus states, test with keyboard, etc. That might be enough for a small website.

Bigger sites have more complicated components like: sliders; info cards that turn 180 degrees; navigation elements with more content; and lightboxes. We will have a look at some of those elements for the website of the Jewish Museum Berlin.

At the end of last year, we had an external accessibility expert check the site. He had a lot to say about those components and made a few suggestions to improve the accessibility. In this session, we will have a detailed look at the problems he found and the steps we took to improve the components.

I will add some smaller problems in surprising places, and some problems that Drupal or screenreaders add to the mix. Like that one incredibly annoying “feature” in CKEditor.