If people treat EAA as yet another compliance thing I think they are missing the greater picture, and probably also greater business.
Year: 2024
Latest posts:
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.
I like the idea behind aria-errormessage and hope it will soon get enough support to make error messages more accessible and establish itself as best practice. NVDA support is coming soon, but beware potential iOS bug and lack of TalkBack support…
Short reflection on positive and negative situations related to accessibility standards. Unification, or to say standardization of accessibility standards, should be our common goal.
W3C Accessibility Guidelines just got a major update. Still a draft, but I love the brainstorming potentials of the newly added guidelines and outcomes. Was the release date an coincidence?
Second Slovenian Accessibility Awareness Day was quite a success, my contribution this time was a manual accessibility audit of crucial WCAG success criteria of larger e-commerces, supported by a team from a11y.si
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.
Sometimes it can be hard to embrace accessibility when we only consider the business perspective. And some people need harsh motivation, when good for people and good for business arguments are not enough.
Prevention of accessibility issues starts long before we code. It is also true for design systems. Sometimes we need much more time to fix things, even if we use a design system…
Do not rely solely on automatic accessibility testing, especially if you do not know that your tool can lie a lot. Use the tools, but educate the people that use them…
Stumbled upon a e-commerce that required hundreds of key-presses to get below the navigation. Reminded me, again, about the importance of skip links…
Another WebAIM’s Million, this time with different webpages. A tiny improvement, but more complexity at the same time. Can design annotations help preventing some issues that are still rising?
There are some limited resources on ARIA role application, but I missed more information for mobile screen readers and just quickly checked the situation on Android and iPhone. It seems that support is not there, besides some small quirks. Be even more careful with role = application!
Digital transformation without accessibility can’t really be called digitalization as it will produce the need to provide alternative formats manually, not to even mention all the problems with bias when relying solely on artificial intelligence.
I’ve done quite some accessibility audits and in this blog post I will go into some common ARIA problems and how to cope with them…
If Jakob’s intention was attention, then he got it. Please don’t internalize that accessibility is failed when it didn’t had a chance to even start.
Even with improved CAPTCHA user experience in the last couple of years we still stumble upon CAPTCHA challenges that are difficult to impossible. The situation is even worse for screen reader users and hasn’t changed in more than a decade. How can we help?
Personal reflection about my encounter with web and accessibility, how I was ignorant of it as well and how I think we can’t be ignorant any more.
After doing an audit of a webpage ,where navigation require horizontal scrolling, I decided to test what does that pattern mean for people with disabilities. Longer story short – be careful, maybe it’s not worth it for critical components like navigation.
Automatic testing, although limited, is useful for quick and bulk test of webpages. With current progress I would expect it to be more efficient, but such tests could easily be bypassed and we can get bad data.
I wrote a lot about automatic accessibility testing, but from developer and accessibility auditor perspective. In this post I summarize some reflections on accessibility tools for content creators – the authors.
I feel that design is too focused on the visual parts and therefore the burden on non-visual design falls on developers. What can we do to improve this? To fill the gaps?
We live in times where technology progress is amazing and therefore we need to make sure we don’t leave groups of people behind. Robots will obviously soon help us at home and everywhere and it is crucial we make their interfaces accessible. Or we will make our society full of new barriers for people with disabilities.
I try to open my mind and reflect on some possibilities that would maybe, perhaps, make accessibility overlays viable solutions. Then I quickly find the downsides and don’t change my mind about them…