Latest posts:

Posted on:

What does aria-hidden=true actually do to interactive elements?

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.

Posted on:

Support for aria-errormessage is getting better, but still not there yet

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…

Posted on:

ARIA role=”application” and mobile screen readers

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!

Posted on:

Consider accessibility when using horizontally scrollable regions in webpages and apps

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.

Posted on:

Accessibility overlays often fail to improve accessibility

I would like that accessibility is the default, just there, without effort. Just fixed for all of us. But it’s not yet possible. Probably never will be. And when I try to be open minded and try to use a feature of accessibility overlay and it just fails, not one but two features, under two minutes, on an important page for people with disabilities, then I had to write about it. And even make a video of it.

Posted on:

Welcome WCAG 2.2 and goodbye success criterion 4.1.1 Parsing

9 new success criteria and one less in WCAG 2.2. Removing 4.1.1 from WCAG 2.2 impacting WCAG 2.0 and WCAG 2.1 as well (can’t fail 4.1.1 anymore). Even if three new WCAG 2.2 success criteria are on level AAA I don’t see reasons to not implementing them as they bring much value!

Posted on:

WCAG may seem perfectionistic, but accessibility isn’t

Concentrating on WCAG alone can feel like accessibility is always binary. When thinking about all the success criteria of the WCAG we can quickly conclude that there is not a single medium sized website in the world that conforms totally. A reflection on perfectionism, conformance and reality.

Posted on:

WCAG 2.2 brings more bad news for sticky elements and more good news for users

Keyboard only users (or users of keyboard based assistive technologies) depend on seeing focus indications at all times and if they can’t see them, they are left to guessing where they are. With soon-to-come WCAG 2.2 focus must be at least partially visible at all times, simply put.

Posted on:

Online business and accessibility best practices

I try to reflect on practical best practices to make an online business more accessible. Most of advice is very tactical and some is a bit strategical. Hope at least some of it can improve the accessibility of your business.

Posted on:

Accessibility of municipal websites in Norway after Web Accessibility Directive – usage of accessibility overlays

Are accessibility overlays common on Norwegian municipality websites? Short answer is no, luckily. But when they are they really messed up the site. Not only accessibility-wise but also on mobile devices / smaller screens / when zooming in.