Time flies and after four years of directive we can reflect a bit more on the positive effects beyond public sector.
Posts
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.
Focusing on single channel alone is not enough, how to make sure accessibility is implemented throughout or channels? Leadership needs to lead!
Dear leader, this is a letter to you. If you lead people, you need to lead accessibility.Do not just delegate it. You will thank me later.
AI is a fact. Some say it will improve accessibility, and I hope it will, but please consider the facts and new regulation.
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.
I did some work with conversion rate optimization and I couldn’t help myself thinking about how accessibility impacts conversion.
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!
Sometimes I see complex web components copied to native mobile applications and often they are the cause of accessibility issues.
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.
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…