WordPress and Accessibility. It has always been a difficult discussion. The developers wrote code, without knowing what’s important for someone that doesn’t see a website like they do. And the WordPress Accessibility team could not find the time or voice to help them fix the problems. So we asked members of the WordPress community for help, and they answered!
This week 4.1 “Dinah” was released. A lot of attention was given by the developers to improve the accessibility of the front-end, the Admin and the default theme Twenty Fifteen.
How to get a WordPress developer all emotional and fanatic: discuss about heading structure.
Here’s my point of view on how headings should be set up in a WordPress theme.
And an overview of the pros and cons brought up in discussions.
A web page can be perfectly WCAG 2 proof, but if it doens’t tell a story, it’s still a puzzle for people that depend on a braille line or a screen reader.
Set yourself in the place of someone who get’s your web page read out loud linearly and the only clue she has on what the structure is, are headings and links.
WordCamp San Fransisco 2014 (WCSF14), the place to be if you’re serious into WordPress. Visiting San Francisco with the accessibility contributors team was a week I won’t forget. It was intense, fun, I spoke a zillion people and learned a lot.