Inspired by others – I reflected on the origins of accessibility problems in design. It’s not so strange when we think that design is the implementation plan and if plan is not accessible then the final product will most certainly also not be accessible. Code, low-code or no-code alike.
Time flies and this blog has now 100 posts. Counting posts does not count for much but I try to consistently write about accessibility to think out loud. I also tried to summarize some quite special thoughts about complexity and how accessibility must be a team effort to be successful. On the end I also added some stats…
Vocal user interfaces come to my attention when playing around with my phones voice assistant. I treat screen-reader as a vocal user experience as well. They are not very related though and that came as a surprise for me. But voice assistants have giant impacts for everybody, not only from accessibility perspective but in general when thinking about humans interacting with computers.
Accessibility for web and mobile seems to be very code-oriented, but it really starts much earlier – in the design phase.We should really shift accessibility left, on the whole picture – from A to Z. That also goes for design and initial product setup, not just developing!
Accessibility team as a team of members of other teams that are motivated to take a proactive role in their primary team – so that all teams can really implement accessibility efforts coherently.
Why are we not encouraged to use ARIA everywhere? Because it is a last option – if we are not able to find a native semantic element, or if we want to create something special, then we can use ARIA. But it should be used wisely!
Design is art, I agree, but not every new page should be a independent piece of art, consistency is king. Easier to make accessible, easier for the user to use.
I have done some quick practical testing and research about cookie consents accessibility, usability and also some testing with search engines – on some websites in Europe, to see what are consequences of cookie consents for users, owners and search engines.
My reflections on the process. And yes – testing early is a requirement. Developers should also use screen-readers to test their components, templates etc.