In this post, I'll break down a real job advert and point out the things that concern me, in the hope it will help you to avoid taking on an accessibility role which is an impossible task, and likely detrimental to your health!
I've developed a weird fascination with challenging language models, thinking up edge-case questions or scenarios to really work out if it can do what is being claimed, or whether it's just reasonably convincing on the surface.
Most language models are useful, but usually, they aren't that great once you drift outside of the realms of common knowledge and into nuanced territory.
So, since the launch of axe Assistant, I've spent a few days testing it out! This post documents my findings!
The problem with AI, especially large language models (LLM), is that most people don't really understand how they work. This is not an accident! It's in many companies' interests to keep the mystery alive! They use smoke and mirrors to market their products as smarter, safer, or more "human" than they actually are.
As humans, we love to personify things, because our only reference point is often ourselves. When something talks like us, we assume it thinks like us too.
W3C, the World Wide Web Consortium, released a new draft of the WAI-ARIA 1.3 specification on 23 January 2024.
If you're not familiar with it, WAI stands for the Web Accessibility Initiative, and ARIA stands for Accessible Rich Internet Applications.
It's a set of standards created to improve the accessibility of the products we build for the web, and it includes details about HTML attributes you can use to make content better for assistive technology. Some common ones you might have come across are aria-label, aria-live, and aria-describedby.
With the new draft of 1.3, we can get a bit of an idea as to what is coming, and how we can prepare for implementing and testing these features.
Many organisations seem to view accessibility through a narrow lens. They do not recognise the breadth and depth of expertise that is required to create a well rounded accessibility role.
We had a similar situation 10 to 15 years ago, when start-ups were constantly trying to hire a single person that could do visual design, user experience (UX) design and software development.
This results in bloated job adverts hunting for somebody who likely does not exist in the job market. A mythical creature. A legend. Their reputation transcends the entire industry, yet nobody has managed to find a real one. Hence the term 'unicorn'.
Web Chat relies on real time information and notifications, so you're going to need to use several features of Aria (Accessible Rich Internet Applications).
In this post, I'm going to cover in detail which of the Web Content Accessibility Guidelines (WCAG) you're going to need to consider, and some examples of how you can use advanced attributes to give screen reader users the best possible experience.
In this post, I just want to talk through what alt text is, why it matters, and how to avoid some common mistakes!
I know alt text posts are common, but I feel compelled to write it given that it's 2023, and I still see a lot of the same issues I've been seeing for years.
The hidden function of the 'check your answers' pattern'
Excerpt:
A friend of mine, stated that usually when we add steps to a process, people get concerned that it will add friction and lead to fewer conversions. But, he argued that it is even more costly to the business to deal with mistakes, and therefore we should use the check your answers pattern.
I agree. There is always a user need to make sure the information they have entered is correct, and a check your answers page is the easiest way to do that. That is it's primary function.
But, what I want to cover in a bit more depth, is the secondary function which often gets overlooked: The pause!
For those who build websites, digital services or mobile applications, or if you just care about making the internet more accessible in general, then this is big news!
So, lets have a look at what all the fuss is about!