Less than a month before EAA start and some organizations still wait with accessibility activities. It is not too late. Stay calm, but make sure you are preparing. It is about process improvement, not perfection.
Author: Bogdan Cerovac
Latest posts:
I love GAAD and sharing and learning about practical and theoretical knowledge about accessibility and disabilities. But I also agree that awareness alone is not enough.
Recently I did an audit of a webpage rich with animations. And needed to warn people about them as sometimes they destroy the experience if we are not careful.
A couple posts back I pointed out latest WebAIM Million shows shopping websites have worst accessibility, and it seems that shopping native mobile applications also share this unfortunate faith.
Vibe Coding is here and it’s amazing. It started a new era where it seems that make your own software is now often a better choice compared to buying it. But – please beware.
You have already read about why is it important and I hope you also understand that it’s not a project but a continuous program, or even better – an upgrade of a culture. But how to prepare?
Accessibility statements are not there for authorities, but for your users. And 90/100 and similar scores mean different things to different people, so I suggest to drop them and rather make the statement understandable.
If you don’t believe me – check the latest draft of Accessibility Roles and Responsibilities Mapping and translate it to your product / service / organization.
Not a very well known fact, but all products and services that are in the scope of EAA and include support services will also need to have them accessible.
A lot of opinions, a lot of academic studies, some lab testing, too little feedback from people with disabilities and too much hype – I need to add.
We have a lot of good accessibility guidelines for web content, documents and multimedia. But what about accessibility of games on mobile phones and tablets? Things can be quite complex there, but that also allows for innovation.
Unfortunately sometimes organizations take shortcuts and just make a generalized copy of accessibility statements from their competition or some random site.
People starting with accessibility can often get a bit biased perception and focus mainly on screen readers. I believe it has to do with the guidelines.
Save yourself time and resources and prepare before you buy an accessibility audit with these tips.
Seems that even AI needs accessibility, at least some parts of WCAG will help AI as well. Another benefit of accessibility.
Demographics tells us that we need help. Automating the physical world requires robots. We need them to be accessible!
Sometimes they can be a huge burden and sometimes just a small annoyance. A quick reflection on what to think before using…
2025 is the year of European Accessibility Act. But we can establish that it will help with global accessibility, not only European.
Authentication is often a burden to many different groups of users, but for people depending on assistive technologies it can be a total barrier. What can we do to improve that?
Tables are sometimes critical for understanding, and even if HTML supports quite complex tables we should keep them as simple as possible.
WCAG 4.1.3 is dedicated to status messages and we encourage their use, but we need to be aware of some potential dangers that are often beyond strict technical conformance.
You connect your physical keyboard to an Android device and start pressing the tab key. And then shift tab. And sometimes – you circle around the UI but can not reach all interactive elements. Is this a WCAG 2.1.1 failure? Maybe it is, maybe you need to try harder…
Is it just me or is it weird to require and encourage the use of standard and at the same time hide them behind paywalls and even make them inaccessible?
This is a summary for my Universal Design 2024 (UD2024) conference contribution, where I was using parts of EN 301 549 and WCAG to check how (in)accessible are iOS and Android mobile applications from 4 largest Norwegian banks.
Web Content Accessibility Guidelines touch keyboard accessibility in a couple of success criteria. It’s essential for your native app to support keyboard interactions for it to be accessible. But how?
Grouping is not an exact science, but all designers and developers touching native mobile applications need to be aware of the simplification possibilities it can bring.
European public sector websites and mobile apps are required to have feedback mechanism. I believe that such feedback helps any kind of organization, even single person businesses.
Naming is one of the most difficult and enduring challenges in software engineering, and it is obvious that it’s also a giant problem in accessibility. How can you help?
Native mobile applications are often more focused and with that – less noisy for users (and I meant that visually and non-visually). But platform choices can lead to inevitable inaccessibility as some abstractions lack support.