Skip to content

5 ways your inaccessible content can pass WCAG anyway

There are lots of ways a site can pass WCAG, but still be inaccessible, particularly if you’ve used an automated checker. Here are 5 I see too often.

WCAG: Useful to a point

I review the accessibility of websites for a living. Honestly, that review process is pretty much running in my head all the time, even if no-one’s paying me to do it.

When I’m reviewing sites, I of course refer to WCAG, the Web Content Accessibility Guidelines. It’s the international standard of digital accessibility, and the basis of many national laws and standards.

But WCAG is the start of the story, not the end. It’s a framework that can help set minimum standards. For true accessibility, we need to go beyond the minimum, and look at the overall experience of interacting with web content.

I’ve been looking back at all the sites I’ve reviewed this year, and here are 5 WCAG ‘passes’ I see too often.

  1. Images wrongly marked as decorative
  2. Unhelpful alt text
  3. Sulky colour contrasts
  4. Over-ridden dark mode
  5. Impossible choices

1. Images wrongly marked as decorative

Let’s start at the beginning: WCAG 1.1.1, Level A requirement: alt text. Adding alt text to your images is practically the definition of bare minimum for accessibility.

“All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.”

WCAG 1.1.1

But WCAG uses the dreaded phrase “except for…” a total of ten times over the course of the guidelines. For 1.1.1, there are 6 exceptions.

The one I see misused the most is:

“If non-text content is pure decoration… then it is implemented in a way that it can be ignored by assistive technology.”

WCAG 1.1.1

In practical terms, this means setting null alt text – or sometimes fancier approaches like setting something as a background image. And I see people do this way more than they should.

What does ‘decorative’ really mean?

I have a whole other blog coming about the nuance of decorative alt text. The answer to the question “Is this decorative?” often involves a judgement call.

But my basic answer to is “probably not”. It should be rare for images to be marked as decorative, and you definitely shouldn’t have main, featured images hidden from people using screen readers.

I once saw a site that had every single image marked as decorative. That’s not decorative imagery, that’s someone who can’t be bothered to write alt text.

2. Unhelpful alt text

Perhaps just as bad as marking an image as decorative is to use alt text that doesn’t actually describe an image.

Writing good alt text is an art, and most of the time having something is better than nothing. Time and again, though, I see alt text that would definitely pass an automated checker, but isn’t actually useful.

Make sure your alt text usefully describes the image in context. Better yet, use an image description, too.

My Accessible Intention series has more information about alt text.

Alt text: the basics | Accessible Intentions

3. Sulky colour contrasts

I categorise some colour contrasts I come across as ‘sulky’ because that’s how I imagine the person making the colour decision. They know they need a compliant colour contrast, so they’ve picked the very very edge of what they can get away with.

When I test content, I don’t manually check every colour combination on a website. I run it through an automated checker, and then manually check the ones that still look dodgy to me, as not everything comes up on an automated test. When manually checking these contrasts, I often find that they sit right on the minimum possible contrast.

Minimum contrasts in WCAG

WCAG AA asks for at least 4.5:1 for small text – the higher the first number, the better the contrast. When I see a contrast ratio of exactly 4.5:1, it feels like the colours were picked for technical compliance, not genuine care.

I always advise to aim for the AAA 7:1 contrast, to make sure people can actually distinguish your content.

My Accessible Intention series has more information about colour contrasts.

Colour contrasts explained | Accessible Intentions

4. Over-ridden dark mode

Dark mode is used by about 80% of people, according to data from a range of sources. It’s a very common accessibility adjustment people use to reduce eye strain, or overall sensory input, particularly on mobile.

Your site needs to work in dark mode to pass WCAG. But WCAG doesn’t actually use the words ‘dark mode’. What it asks for is particular colour contrasts that make your content perceivable for people with a variety of vision issues, like low vision and colour blindness.

These colour contrasts have to still work in dark mode. If they don’t, that’s a very straightforward WCAG fail. (And a very common one.)

Another cunning get-out clause

But what if your colour contrasts are ok in light mode, and you tell your website to ignore dark mode instructions? What if it just displays in light mode regardless?

Congratulations, you’ve passed WCAG – but created access barriers for the people using your site.

5. Impossible choices

This last one’s a little different. It’s where I argue that something technically is a WCAG fail, although some might feel it’s a stretch. 

I often review forms, and see multiple choice questions, where the choices that don’t cover every scenario.

If you publish a form and someone cannot answer a mandatory question, then as far I see things, it’s not operable – one of the core tenets of WCAG.

This table shows some examples, based on things I’ve actually seen:

QuestionAnswer optionsUnavailable options
How long did it take you to get here?Less than an hour
1-2 hours
2-3 hours
More than 3 hours
How often is this an issue?Every day
Most days
Never
Some days
Occasionally
What is your gender?Male
Female
Non-binary
Something else
Example questions with missing options

If the correct answer for you is not an available choice, you cannot access the form.

Where operability means neurodiversity

This also has an interesting crossover with neurodivergence, because many neurodivergent people get anxious about answering questions truthfully.

For example, I often see gender options of “male, female, or rather not say”. As a non-binary person, there’s no correct answer for me. Some would argue I can just pick “rather not say”. And sometimes that’s true: I would rather not say.

But what if I rather would say? There’s no option that is a truthful answer to that question, so I physically cannot answer it.

It’s the kind of thing some people might dismiss as being pedantic, but can cause a lot of anxiety.

So: questions that can’t be answered, made worse for neurodivergent people? That sounds like an accessibility fail to me.

Care trumps compliance

What all this boils down to is that guidelines are great for providing metrics and a roadmap. But if you approach accessibility as tick-box exercise, you’ll never have a truly accessible site. You’re designing something real humans want to interact with, so it needs humanity and care, too.