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.
Posts
Sustainability and accessibility are absolutely interconnected. Recent sustainability guidelines, although still in draft version, are quite often referring to accessibility, so I wanted to expose parts where accessibility is beneficial to sustainability.
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?
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?