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…
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.
Social media is one of the most used internet services. And people with difficulties are users too. And as they should have the right to work as well – they do use LinkedIn. So it must really be accessible. But, is it?
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.
My reflections on the process. And yes – testing early is a requirement. Developers should also use screen-readers to test their components, templates etc.