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:

GAAD 2024 Slovenia – state of e-commerce accessibility – a year before the new legislation

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

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:

Testing and monitoring accessibility with automatic tools will get less precise

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.

Posted on:

Accessibility errors based on accessibility statements of Norwegian public sector websites

Making large scale analysis of accessibility based on centralized accessibility statements is simple. But we do need to consider that not everybody filling out accessibility statements have the needed experience and knowledge. And sometimes the intention to be transparent is also absent.

Posted on:

Comparison of accessibility of e-government websites in Europe

eGovernment Benchmark of 35 countries in Europe (EU and beyond) finally gathered some insights about accessibility of eGovernment websites. After years of accessibility legislation accessibility is still a pilot indicator which unfortunately indicates how late we are in the awareness process.

Posted on:

WCAG 2.2 will be a part of EN 301 549 and with that a part of WAD and EAA

WCAG 2.2 is here, when do we get it into legislation, like Web Accessibility Directive and European Accessibility Act? Well EN 301 549 seems to be updating in 2025, according to work item schedule it may come in early 2026. Unless ETSI adds WCAG 2.2 sooner it seems that we will have to wait quite a long time.

Posted on:

Norwegian municipality almost got fined for using inaccessible e-learning mobile app

Municipality avoided paying fines after vendor of e-learning app fixed issues with 4 success criteria out of 6 tested (all A level). I found some interesting facts that seem to reveal procurement and especially awareness problems and I also offer some potential solutions.

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:

Status messages on page load – how to notify screen-reader users about important messages when the page loads

Sometimes we expect code to work in a specific way. Here is another example how we need to test it to be certain. Status messages are so important that they even got their own WCAG success criteria, but make sure your code really works.

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:

Some thoughts on how I think Web Accessibility Directive can be improved

I am honored to be a part of a group of experts that will provide some feedback to European Union on accessibility and Web Accessibility Directive. This post is a summary of my ideas that will be in the article with some additional thoughts and context.

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.

Posted on:

Accessibility of municipal websites in Norway after Web Accessibility Directive – parallel analysis by another actor – summary

I am not the only one concerned about accessibility and it seems that I also had similar timing, methodology and results. I didn’t go all in with the crawling of absolutely everything and I didn’t test the documents as they did. So that’s why I made a short summary to enrich my own analysis.