Latest posts:

Posted on:

Some tips for keyboard support on native mobile applications

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?

Posted on:

Accessibility group – often overlooked native mobile app pattern

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.

Posted on:

Why should all organizations establish feedback mechanisms for accessibility?

European public sector websites and mobile apps are required to have feedback mechanism. I believe that such feedback helps any kind of organization, even single person businesses.

Posted on:

Native mobile app accessibility – choice of platform is essential

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.

Posted on:

My contribution to second AccessibleEU conference in Slovenia (DIGIN 2024) – inaccessibility of e-commerce

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.

Posted on:

Web Accessibility Directive with positive accessibility effects beyond public sector

Time flies and after four years of directive we can reflect a bit more on the positive effects beyond public sector.

Posted on:

Briefly on conflicts between aesthetics and accessibility requirements

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.

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:

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