Latest posts:

Posted on:

Look for accessibility statements before using third party tools

Website owners are responsible for use of third party widgets, plugins and more. Before using them they should check if they conform to WCAG, otherwise their site will not conform either. Checking for accessibility statement of the third party may reveal huge problems with their product’s future.

Posted on:

Screen-readers work differently with different browsers and combinations can have bugs

Sometimes it’s simple to make a feature with JavaScript but not so simple to make it consistent for all those screen-reader and browser combinations. In this post I describe how I tried to update some live regions and the order in the DOM was not respected. Solution was simple, but it’s easy to forget about it when it works visually.

Posted on:

Second Slovenian Accessibility Awareness Day – my private contribution to Global Accessibility Awareness Day 2022

Building on first Slovenian Accessibility Awareness Day and on the first official Web Accessibility Directive reports from Slovenian public sector I made the Second Slovenian Accessibility Awareness Day. Still and always a work in progress, but please read the post and then if you wish also the reports to get some clues about the state of accessibility in Slovenia.

Posted on:

2022 WebAIM’s Million report on accessibility – my comment

Some improvements can be detected and I also added some thoughts of mine about the parts that are not very obvious. Interestingly – e-commerce is almost worst – and that really is a surprise when we think about how much do they invest into ads and SEO, just to get some new users.

Posted on:

Some common web accessibility issues caused by developers

Some accessibility issues originate in code. And when design is being recreated with code it may seem to work but when thinking about accessibility we may notice that it only works for some users and not for others. I’ve decided to describe some common accessibility fails that are on developers.

Posted on:

Should you invest in accessibility certificate for your webpage or mobile app?

I was asked if I can issue “WCAG certificate” for a website, so I decided to investigate what would that actually mean as we all know that sites and mobile apps are constantly evolving and changing and even if they conform to WCAG they may not the following day. What would then mean to issue a WCAG certified certificate and still be ethical and the right thing to do?

Posted on:

What would I like to get from Accessibility-as-a-Service?

What would I want from my Accessibility-as-a-Service provider? What would be the ideal here when we know that automatic testing is absolutely not enough? We must also get people as a part of the service – accessibility specialists and people with disabilities. And when done from start to end it is way more efficient compared to only using it at the end.

Posted on:

External accessibility audits and how to act on them

External agency made an accessibility audit. It provided a lot of possible solutions. In this post I try to make it easier to act on this audit. Breaking results into responsibilities, then prioritizing the issues and finally estimating and fixing them can be one way of doing so.

Posted on:

First official reports on Web Accessibility Directive monitoring in EU

European authorities published accessibility reports from multiple EU lands and I decided to read all of them and make short summary with my personal comment about them. A lot can be learned from their first auditing and there is a lot that can and need to be improved throughout Europe.

Posted on:

How to know that a website or app is really accessible?

To claim that our product is accessible needs more than just WCAG audit that did not discover any fails. Real users, people with disabilities are the only one that can really reflect on the accessibility of our products. That’s why we should include them in all reasonable parts of our production processes. Otherwise we may think we deliver accessibility but the truth can be opposite.

Posted on:

Problems with automatic accessibility testing

Automatic testing of software is brilliant. Saves a lot of time and effort, prevents problems soon and makes our products better. But when trying to automatically test accessibility we need to know about the challenges and problems before. Some tools may even produce wrong results and some tools may report everything is perfect when they can only test up to a third of criteria.

Posted on:

PDF is less accessible than HTML

HTML semantics and assistive technologies support is way better than PDF’s. If you are a MAC user that needs to use a screen-reader you may be forced to experience the missing semantics of even most accessible PDF’s. And maybe it is time to move more PDF documents to HTML?

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:

State of web accessibility in Slovenia – my contribution to accessibility awareness

20th of May 2021 is Global Accessibility Awareness Day and I wanted to contribute by analyzing state of web accessibility on Slovenian web pages. We can therefore say the first ever contribution to Slovenian Accessibility Awareness Day.

Posted on:

End of axe-hackathon 2021 but not the end of aXeSiA

Not really surprisingly – aXeSiA did not won axe-hackathon. And I never dreamed that it will. It was just an experiment for me personally. But this will not mean that aXeSiA is retiring – I will make it a tool I can use often. And a tool I can really tweak as I need and like. Congratulation to other projects and especially Inclusiville. If I had the time I would be happy to work on all other projects as well as they are really good.

Posted on:

My first axe-hackathon with my aXeSiA – my first contribution to accessibility open source

aXeSiA – my open source contribution to accessibility testing and axe-hackathon. We all like to use browser extensions to test the pages but aXeSiA makes our work easier if we want to automate it.

Posted on:

Should we add alternative text to a decorative image because of search engine optimization or not

We remember the rule for alternative text on decorative images, right. But is it really so clear what an decorative image is. Sometimes SEO wants us to have alternative text for images that do not directly add to the information. Should we do it for the bots or should we save time for screen-reader users? It depends. As always…

Posted on:

Some findings from my WAI-tools monitoring pilot analysis

Extremely valuable documentation that reveals some interesting points about future of Web Accessibility Directive monitoring methods, tools and also some less clarified reporting matters. The accessibility statement automatic analysis will most certainly also have a central role and it is worth following on the Accessibility Conformance Testing rules that are the engine of all automatic tools out there.