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.
Tag: WCAG
Latest posts:
If you don’t believe me – check the latest draft of Accessibility Roles and Responsibilities Mapping and translate it to your product / service / organization.
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.
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.
Demographics tells us that we need help. Automating the physical world requires robots. We need them to be accessible!
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?
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.
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.
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.
I lead a project to manually test 20 Slovenian e-commerce websites and wrote an article about it, called (In)Accessibility of Slovenian E-commerce the Year Before the European Accessibility Act.
We need to be aware of the limitation of the tools to be able to use them properly and to prevent any bias.
Time flies and after four years of directive we can reflect a bit more on the positive effects beyond public sector.
Question of dealing with conflicts between aesthetics and accessibility comes up a lot and sometimes it’s easy to just let one side win and be done with it. I think that we need a cultural shift to have both of them.
Don’t get too concerned about the differences between WCAG on levels A and AA and instead use the energy to go beyond and implement AAA.
EAA goes beyond technical accessibility. It’s reference to Design for All is a well planned strategical motivator for culture change!
I am a bit biased towards technical parts of accessibility, but when I studied EAA even more, I finally understand why it does not try to be technical.
Benchmarking of accessibility of different e-government digital services and how well do different countries do is a start, but beware!
Whenever you test web accessibility you need to consider all the website variants based on all media queries. This can be vital for your time usage estimates!
Any help to make native mobile application accessibility clearer is welcome. We really need to know more to make apps more accessible.
If people treat EAA as yet another compliance thing I think they are missing the greater picture, and probably also greater business.
Bogdan – can you give us an example of a website that conforms to WCAG / is accessible? A popular question with a less popular answer.
Everybody knows that we must not use aria-hidden on interactive elements. But why is that a problem? I decided to check for myself, so that I can explain it better the next time I will be asked.
Short reflection on positive and negative situations related to accessibility standards. Unification, or to say standardization of accessibility standards, should be our common goal.
Accessibility audits come in different forms and sometimes it is better to take smaller audits than to wait for the larger ones to be finished – and risk missing out on changes that had to happen in the meanwhile.
Quarter of a century later and we still don’t have enough awareness, support, knowledge, buy-in for accessibility. It is improving, but slowly, we need even more advocates.