Skip to content

Accessible Intentions: blog series introduction

You want to make your website more accessible but you don’t know where to start. You don’t have a team of knowledgeable developers, you don’t have a big budget. You just have you, and your best intentions.

Sound familiar? You’re in the right place. My new blog series, Accessible Intentions, is for people who need the basics of accessibility to be explained as simply as possible.

Blog structure

Each blog covers a particular area of website accessibility, and explains the basics in a non-technical way, with each one following the same format.

At the top, there’s a ‘cheat sheet’, which gives the lowest-effort way to make sure the particular issue is not a problem on your site. It’s for people who don’t want to be overwhelmed by the background and details.

I then cover:

  • Why it’s important: What problems the particular issue creates, and who for.
  • What does WCAG say? What the Web Content Accessibility Guidelines say about it, with a link through to the actual criteria.
  • Exceptions: Where there’s an exemption from WCAG, and how that affects accessibility.
  • Where it gets complicated: What to do in edge cases and more complex scenarios.
  • Free tools: Simple, free tools or built-in features that help you test or fix the issue.

Accessibility is more complicated than this. There will always be new things to look at and more to discuss. I’ll keep doing other blogs, too. But this series is for people who are overwhelmed by the complexity, and just want to do the next right thing.

Definitions

Here are some common terms used in the blog series, and what they mean. I’ll add to this as the series grows. Select each term to display or hide the definition.

WCAG

This stands for ‘Web Content Accessibility Guidelines’. It’s the international standard of accessible websites. It’s not a legal standard in itself, but it’s used as the basis for many laws and standards that govern accessibility. More importantly, it’s a framework to help you understand where you can make things better.

People use this abbreviation in different ways, but I normally refer to it in the singular: “WCAG says…”. (And I pronounce it ‘wuh-cag’)

WCAG standards are split into 3 levels:

  • A: The basic minimum for accessibility – think of this like a bronze medal
  • AA: The medium standard that most places aim for – like a silver medal
  • AAA: Gold standard accessibility

Not every guideline is split into these three levels.

WCAG is useful, but there are limits to a single, international, set of measurable guidelines that define accessibility. There’s also nuance around exactly how it’s interpreted. Lot of content can theoretically pass WCAG, but still not be accessible. So I work with WCAG, but always look at issues more broadly.

Screen readers

Screen reading technology is when content on a website is read out loud. It’s most commonly used by blind people – but not exclusively.

On computers, most people use one of two screenreader tools: ‘JAWS’, which is a paid tool, or ‘NVDA’, which is free. These need to be installed on a computer.

There are also built in tools that read out content. For example, Android users have ‘TalkBack’ and iPhones and Mac computerr use ‘VoiceOver’. These come as part of the software and just need to be turned on.

You can try using screenreading software to understand more about how they work, but this is not a substitute for proper testing. Full testing should always be done by someone who actually uses a screenreader day-to-day.

Content Design Ireland have a great post explaining this in more depth.

Accessible Technology (AT)

Screen readers are just one example of accessible technology. There are lots of other kinds of technology that people use to help them access websites.

For example:

  • sip-and-puff devices: These allow someone to use a computer using a kind of straw, or ‘wand’. They are used by people who can’t do this using their hands.
  • speech-to-text: This means people can dictate aloud instead of typing something. Like a lot of accessible technology, this is now used by all kinds of people, but it’s still most useful for people who are unable to type.
  • refreshable Braille devices: These send website content to a special device using Braille. They are most commonly used by Deafblind people.
Sight impairment/blindness

In the UK, the official terms for people who cannot see well, or at all, are ‘sight impaired’ or ‘severely sight impaired’. But lots of sight impaired people still use the term ‘blind’. It’s still considered an acceptable term.

Being blind doesn’t always mean people can’t see at all. Some people can’t see anything at all; others can see a little. This means a blind person might use a screen reader, or might still look at a site, perhaps using screen magnification.

Around 2 million people in the UK have some level of sight impairment. That’s a little less than 3 in 100. [Source: RNIB]

WAVE plugin

In the free tool section of each blog, I often mention the WAVE plugin. This is a browser extension created by WEBAim that lets you check for accessibility issues on any web page. You can read more about WAVE in my article about accessibility checker tools.

D/deaf

When I use the word ‘D/deaf’, you might wonder why I use the letter D twice. This is because being Deaf (capital D) and deaf (small d) are culturally different. I’m neither big D or little D deaf, so for a fuller explanation of this, I’ll pass over to people who are.

Read the blogs

I will publish more blogs as time goes on. If there’s a particular area you’d like to see covered here, let me know.

Contact me

If you have any feedback on the blog series, or want help making your website more accessible and inclusive, please do get in touch via email or social media.