I just received mail from IAAP that my certification is prolonged based on my activities that generated enough Continuing Accessibility Education Credits (CAECs). I like that we need not only to pass the exam but to also remain active to maintain it. There are some downsides of certifications, but still way more positive effects in my opinion.
Posts
4 years went fast. A small self-reflection about the blog and a bit about the future of it.
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.
Some brief thoughts on how to make a small business more accessible, at least digitally. Don’t take it as a project, it is a program, a journey.
Advertising is big money. Making your ads inaccessible is expensive. In this post I summarize some common accessibility issues that are present in online adverts.
WCAG 2.2 seems to be around the corner, document is currently a Proposed recommendation. But what does that actually mean?
Digital transformation – as we move from paper to spreadsheets and then to smart applications for all parts of our business needs, we have the obligation to make our future digital business accessible from the start.
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.
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.
Inert is still useful and although we are slowly getting native dialog we can still benefit from using inert when we don’t strictly use dialogs or modals.
Found an interesting study that should encourage business owners to do something about poor accessibility of their websites and mobile apps. Hopefully somebody will think about how much people their business is potentially missing.
We have well known robots.txt, a bit less known humans.txt and seemingly very important security.txt. Is it also time for accessibility.txt? A uniform info about how accessible the site claims to be and how to contact people that can help us if we experience problems?
Autocomplete and correct keyboard layout when filling out forms are simple and powerful helpers to make less errors when filling out forms. They benefit everybody, but they are even more appreciated by people with different disabilities. Web support is there for years, but what about native mobile applications?
European Accessibility Act is around the corner. 100 weeks is not a lot in terms of conformance and compliance. Especially considering banking, e-commerce and transport services that will be a part of EAA. What to do? Start now!
I don’t like the fact that EN 301 549 is provided in PDF format. It’s way simpler to process HTML. And when I did some parsing I figured out I could also check how exactly does EN 301 549 goes beyond WCAG for web and mobile applications. Quite a lot is the short answer.
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.
Shifting left, that is considering accessibility earliest possible, should be a concept in our school system as well. Basics of accessibility thought earlier in our lives is probably the only sustainable way to make our societies more inclusive and our products and services more accessible.
Just a quick brainstorm when checking a design wireframe for potential accessibility issues, finding low level problems that may be solved way earlier than we may think. Maybe even before designer became a designer and before developer became a developer?
We finally made an official Global Accessibility Awareness Day in Slovenia, and I am proud that I was a part of it and even had two presentations. It was amazing to meet a lot of people from different organizations connected to accessibility and to greet people that I cooperate with in-person for the first time.
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.
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.
This is the fourth part in a series and in this post I expand the automatic analysis report to cover approximately 50 webpages under each of 356 Norwegian municipalities – 17837 URLs to be precise.
The general outcome is quite interesting and I was surprised to see some very positive trends as well.
Accessibility statements can claim all sorts of things but we should test as much as we can to establish the reality. The simplest and quickest way to do that is to use automatic tests. In this post I reflect on the results of automatic tests of homepages for all Norwegian municipalities. You will be surprised as I was.
Accessibility statements required by Web Accessibility Directive are quite efficient indicators of websites accessibility, when sites are audited by professionals with some experiences. We don’t have better data than this at the moment, so let’s process this a bit and then dive into numbers and findings.
What is the state of accessibility of municipal websites in Norway? Now we can get some data based on their official accessibility statements. While doing so we can also draw some conclusions, but this post is only the first part of a series of posts on the subject and talks mainly about motivation, methodology and preparation.
I love WebAIMs Million, but I need to point some things out. Some people may come to wrong conclusions after reading parts of the report and I hope I can improve that. I also think I know the reason and the solution about the still very poor state of accessibility.
I stumbled upon a lot of websites that had untrue accessibility statements. It’s quite easy to know when they are not being honest actually. Some goes even so far to claim they are compliant and conform to WCAG 2.1 on AAA level while their autoplaying hero video with no controls is screaming “lies” to me.
I wanted to check for myself it ChatGPT can help delivering more accessible code. And after multiple trials I gave up. The reason for it’s confident but wrong example code is clear to me and when you read this post it will also be clear to you.
Do we have more accessibility specialist in 2023 compared to 2022? I got the numbers from IAAP and it’s looking better. And some countries are really doing good, check to learn more about which countries got most new certified professionals.