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.
Tag: WCAG
Latest posts:
Sometimes best practices are passed as WCAG requirements and that can make accessibility more difficult for some people to implement. We need to understand what WCAG actually requires and what it does not before we try to impact other people.
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.
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?
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.
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.
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?
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.