If you use AI agents – you still need to be able to take over manually. WebMCP is a standard proposal for a new in-browser AI control and it still requires accessibility, it can make us more efficient, but all users need to have the possibility to take control at any time.
Category: Accessibility innovation
Latest posts:
Thanks to Michael Fairchild and Microsoft, we now have some accessibility benchmarks for a selected range of AI models – where they were tested with automatic accessibility tools after generating sample code. Project is called A11y LLM Eval, and it provides quite some insights, both directly and indirectly.
Vibe Coding is here and it’s amazing. It started a new era where it seems that make your own software is now often a better choice compared to buying it. But – please beware.
Not a very well known fact, but all products and services that are in the scope of EAA and include support services will also need to have them accessible.
A lot of opinions, a lot of academic studies, some lab testing, too little feedback from people with disabilities and too much hype – I need to add.
We have a lot of good accessibility guidelines for web content, documents and multimedia. But what about accessibility of games on mobile phones and tablets? Things can be quite complex there, but that also allows for innovation.
People starting with accessibility can often get a bit biased perception and focus mainly on screen readers. I believe it has to do with the guidelines.
Seems that even AI needs accessibility, at least some parts of WCAG will help AI as well. Another benefit of accessibility.
Demographics tells us that we need help. Automating the physical world requires robots. We need them to be accessible!
Question of dealing with conflicts between aesthetics and accessibility comes up a lot and sometimes it’s easy to just let one side win and be done with it. I think that we need a cultural shift to have both of them.
AI is a fact. Some say it will improve accessibility, and I hope it will, but please consider the facts and new regulation.
W3C Accessibility Guidelines just got a major update. Still a draft, but I love the brainstorming potentials of the newly added guidelines and outcomes. Was the release date an coincidence?
Automatic testing, although limited, is useful for quick and bulk test of webpages. With current progress I would expect it to be more efficient, but such tests could easily be bypassed and we can get bad data.
We live in times where technology progress is amazing and therefore we need to make sure we don’t leave groups of people behind. Robots will obviously soon help us at home and everywhere and it is crucial we make their interfaces accessible. Or we will make our society full of new barriers for people with disabilities.
I try to open my mind and reflect on some possibilities that would maybe, perhaps, make accessibility overlays viable solutions. Then I quickly find the downsides and don’t change my mind about them…
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.
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.
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?