Latest posts:

Posted on:

Browser’s accessibility tree and screen-readers speech log aren’t always sincere

Accessibility tree in browser and screen-reader’s speech logs are extremely valuable tools when we want to check how HTML, CSS and ARIA translate to assistive technologies like screen-readers, no doubt about that. But please make sure to go through to the end – do listen to your screen-readers and in different combinations with browsers. As sometimes that’s the only way to find out about real problems.

Posted on:

Operating systems, browsers, screen-readers, automatic analysis tools can all have bugs that make accessibility even more difficult

The journey from content creator to end user is quite long. At least in terms of different software that needs to deliver. And as we all know – software has bugs. And sometimes even so called features that can actually be called bugs as well. So please test and if we find a problem – report it, so that we improve the accessibility one step at a time.

Posted on:

Developers should test with screen-readers

Every (front-end) developer should add screen-reader to their tools. Screen-reader experience can really help us make products more accessible and also be better at our coding. Combinations of screen-readers and browsers can get over complicated, so it is important to think if code we write is supported for majority.

Posted on:

Screen-reader users don’t tab through your site

I organized an accessibility workshop for our front-end and full-stack developers, user interface and user experience designers and others involved in digital production. This post will concentrate on screen-reader (SR) users way of navigation because it may surprise non-screen-reader users quite a lot.

Posted on:

After 7 weeks of waiting – now I am also officially Web Accessibility Specialist

Some reflections on my newly acquired Web Accessibility Specialist certification and a mention of Neuralink that will be demoed today and can have positive implications on accessibility as well. If used correctly.