Download our Accessibility Whitepaper >

Dyslexic Reading

Clear and adjustable layout with sufficient colour contrast, for blind users the website must work with screen readers.

You need to make sure users can recognise and use your service with the senses that are available to them.

  • Use the proper markup for every feature (for example, forms and data tables), so the relationships between content are defined properly
  • Do not use colour as the only way to explain or distinguish something
  • Make sure your service works well with assistive technologies - for example, important messages are marked up in a way that the screen readers knows they're important
  • Provide text alternatives ("alt text") for non-text content
  • Make sure content is structured logically and can be navigated and read by a screen reader - this also helps if stylesheets are disabled
  • Make sure every feature can be used when text size is increased by 200% and that content reflows to a single column when it's increased by 400%
  • Do not use images of text
  • Use text colours that show up clearly against the background colour

Identifying Colour Barriers:

  • Our vision allows us to make meaning out of the shapes, colours and text we see. But we all have a unique experience of vision. Due to differences in eyesight and the devices we use, no two people ever see things in quite the same way.
  • Within our vision, perception of colour varies the most from person to person and device to device. This makes barriers relating to colour likely to impact most of us at some point in our online life.

Contrast:

  • Contrast is the measure of how easily a user can tell two colours apart. For example, being able to read text against a background or perceive the edges of a dropdown menu or button.

Examples:

8.01:1*

Click Here

1.73:1*

Click Here
  • At some point, all users will be unable to tell the difference between two colours. This point may occur sooner for older users, users with a vision impairment, or users with low-end devices. Lighting also plays a role. When using a phone in direct sunlight, more contrast is needed for the content to remain visible.

*Colour contrast: What is it?

Colour contrast refers to the difference in brightness and/or colour between text and its background. It's crucial for ensuring that text is readable and perceivable by individuals with visual impairments or those who may have difficulty distinguishing certain colours.
Click here for WebAIM Contrast Checker to test your foreground and background colour for accessibility.

Do's

  • Describe images & provide transcripts for video
  • Follow a linear, logical layout
  • Structure content using HTML5
  • Build for keyboard use only
  • Use text colours that show up clearly against the background colour
  • Write descriptive links and heading

Don'ts

  • Only show information in an image or video
  • Spread content all over a page
  • Rely on text size and placement for structure
  • Force mouse or screen use
  • Write uninformative links and heading

Continue your learning here:

Supplemental guidelines

Mobile First!

Learn more

Supplemental guidelines

Commercial

Learn more

Tools & Checklist:

Supplemental guidelines

WCAG Ratings

Learn more

Supplemental guidelines

Testing Checklist

Learn more

Supplemental guidelines

Resources

Learn more

Colour as a way to convey meaning

  • Even with great contrast, colour is still an unreliable way of conveying meaning.
  • It's best to use colour as an enhancement rather than relying on it being visible to users. If we design our graphs, charts and other graphics to make sense without colour they will be readable to a wider range of users in a broader range of situations. We can achieve this by using different styles of line, different symbols (squares, triangle etc) or shading things in different patterns and colours.
  • The same barrier also occurs with elements such as buttons and links. We can sidestep this barrier by adding an underline to our links and buttons which disappears when the user interacts with them. This technique is common. Extensive use was made of this on BBC websites and apps.

Don't rely on colour exclusively

Avoid these:

Click Here
Click Here

Red/Green with Colour-Blindness:

Click Here
Click Here

Try these:

Click Here
Click Here

Use the WAVE tool to detect errors

WAVE (wave.webaim.org) is a free online tool that can help you evaluate your page for accessibility. WAVE places colour-coded icons over the page you are testing. While it takes some skill to interpret some icons, you can be sure that any red icon is an accessibility error to be addressed.
If you are not sure what an icon means, click on it and then select "More information".
If you cannot see the icons correctly, select the No Styles button to view the page without styles. Although the page will look different, all icons should be visible.

  • Types of Manual Testing Chevron Down
    • Black box testing:
    • It is a type of software testing technique that focuses on testing the functionality of a software system without any knowledge of its internal workings. This technique is used to test the system from a user's perspective, focusing on testing whether the system works as expected and meets the user's needs. The tester only knows the inputs and expected outputs of the system and does not know how the system works internally.

    • White box testing:
    • This technique is used to test the system from a developer's perspective, focusing on testing the system's internal logic, performance, and efficiency. The tester has complete knowledge of the system's internal details, including the code and its implementation.

    • Gray box testing:
    • Combines the approaches of both black box and white box testing. This technique follows from a developer's perspective, the focus is on testing some of the system's internal workings but not all. The tester has partial knowledge of the system's internal details.

  • Testing Without Tools Chevron Down
    • In a form, is it clear which data is expected and which fields are obligatory?
    • Ensure clear instructions are provided in places users have to input data. Add a label to the input fields, for example 'First name'. Mark whether fields are required or optional. Indicate if data must be entered in a specified order.

    • Text resizing
    • On a mobile phone you can turn on text resizing in the system settings. This works differently on different devices, but if you search for "text" in the system settings, you will see the text size option. If you set this to maximum, you can then see whether your app uses large fonts and whether this does not lead to errors.

    • Does text appear larger when you have set a larger font?
    • It is important for visually impaired users that text can be enlarged. Users specify their preferred font size in the system settings. Text in your app should resize according to this preferred font size. Ensure that the text in your app supports resizing.

    • Can all text be read with the largest font?
    • Ensure that all content on the screen remains readable even with the largest font. Content should be readable without having to scroll in two directions. Because the text is displayed larger, it can push other elements off the screen. Ensure content can still be reached, for example, by scrolling vertically.

    • Contrast
    • You can easily test your app's contrast. Answer these questions to form an idea whether your app has sufficient contrast. We use this contrast checker ourselves. But there are various tools available that can do this for you.

    • Is the contrast of normal text at least 4.5:1?
    • It is important for visually impaired and colour-blind users that text is legible. The contrast ratio between the text colour and background colour must be at least 4.5:1. For bold text and larger text, a ratio of 3:1 is sufficient.

    • Is the contrast of the content at least 3:1?
    • The content of a screen must be legible for everyone. You achieve this by using enough colour difference in graphical elements such as icons, buttons and input fields. The contrast must be at least 3:1.

    • Screen reader
    • A screen reader reads what is on the screen. You can navigate through apps and perform actions using gestures. In this way it is possible to use apps without sight. More information about the screen reader can be found on the page about assistive technologies page. If the screen reader works properly, keyboard controls, voice controls, and toggles will usually work as well. You can practice the screen reader gestures in the screenreader.app.

    • Are textual alternatives available for all non-text content?
    • People who are blind use a screen reader to read the information on the screen. Make sure that a description is available for all non-text content. Images, for example. By describing them the screen reader can read what you see.

    • Is the structure of a page clear to users of assistive technologies?
    • Information on the screen must be conveyed to assistive technologies. For example, make sure that headings are not only bold, but also marked as headings in the code. Relationships on the screen must be usable with assistive technologies. Elements in a list must be navigable one by one. Elements in a table must be navigable by rows and columns.

    • Is the order of elements clear to assistive technologies?
    • Make sure that the order which assistive technologies follow reflect the meaning of the content. Otherwise, users of assistive technology may misunderstand the content. Most content is presented from left to right, from top to bottom. The information should also be presented to users of assistive technologies in this way.

    • Can you operate the app with assistive technologies?
    • Make sure that all functionality in the app can be used with assistive technologies. People who are blind use the screen reader. People with a motor disability use switch control, voice control and/or the keyboard. These assistive technologies are built into the operating system.

    • Are there places in the app where you get stuck using the keyboard?
    • Prevent people using an external keyboard from getting stuck in your app. For example, it often happens that pop-ups cannot be closed with a keyboard. You can test this to a large extent with a screen reader.

    • Do the headings and labels describe the content clear enough?
    • The use of headings is important to understand how the content is structured. Blind users can use a screen reader to request an overview of all headings on the screen. The use of labels is important with forms to understand what input is requested. Make sure the labels are linked to the input fields.

    • Is the correct name, role and value given?
    • It should be clear to users of assistive technologies what actions they can take. Make sure that the name, role and value can be determined for all elements. For example, when you use an image as a button, you must set the role as a button.

How to test labels

Labels are something we can test manually. An automated scanner is unable to tell if a label is meaningful.
Most labelling barriers happen with links, buttons, forms and images. But they also arise when media content lacks captions, audio descriptions (for video) and text transcriptions for audio. These 'labels' are known as 'text equivalents. It's not only users who benefit. Search engines use labels to analyse and rank the content of your website. Good labels make your content easier to find.

Other non-descriptive link phrases to avoid comprise:

  • Here
  • Read More
  • More
  • Info
  • Link to [link destination]

When focused on creating exceptional user experiences, it is better to make your descriptive text unique and relevant.

Continue your learning here:

Supplemental guidelines

Mobile First!

Learn more

Supplemental guidelines

Commercial

Learn more

Tools & Checklist:

Supplemental guidelines

WCAG Ratings

Learn more

Supplemental guidelines

Testing Checklist

Learn more

Supplemental guidelines

Resources

Learn more

Use High Contrast Colours

  • Ensure there is a high contrast between text and background colors. This helps users with low vision or color blindness to read content more easily.

Font, Text Size and Resizing

  • Use sans-serif fonts like Arial or Helvetica for better legibility, as they are generally easier to read on screens.
  • Steer clear of script or overly decorative fonts, as they can be difficult for some users to read.
  • Use no less than 16px (12pt) text for body copy.
  • Use no less than 24px (18pt) text for larger text.
  • Use relative units like em or rem instead of fixed units like px to allow users to resize text without breaking the layout.

Keyboard Navigation

  • Ensure all interactive elements (like links and buttons) are accessible via keyboard. This is crucial for users who cannot use a mouse.
  • Use no less than 16px (12pt) text for body copy.
  • Use no less than 24px (18pt) text for larger text.
  • Use relative units like em or rem instead of fixed units like px to allow users to resize text without breaking the layout.

Alt Text for Images

  • Provide descriptive alt text for all images. This helps screen readers convey the content of images to visually impaired users.
Man with visual access needs using a computer

Clear and Consistent Navigation

  • Use clear headings and consistent navigation menus to help users understand the structure of your site.
  • Consider your CTA colours. For example, using red for a 'CANCEL' button next to a green 'OK' button will not be distinguishable for someone with red/green colour blindness.

Avoid Using Colour Alone to Convey Information

  • Use additional indicators like text labels, icons or patterns to differentiate elements.

Forms

  • Ensure form fields are clearly labelled and provide instructions or error messages that are easy to understand.

Responsive Design

  • Make sure your website is responsive and works well on different devices and screen sizes.

Colour Contrast

  • Having identified your colour combinations that don't pass accessibility, utilise one of the colour accessibility tools to find alternatives.
  • Play around with the levels to find where the change from fail to pass comes in so you keep as close to your desired colours as possible.

When checking colour contrast

Remember, it's the contrast between text and background that you're looking at here. Although subtle colour differences can look nice, there's no point if your audience can't read it.

Continue your learning here:

Supplemental guidelines

Mobile First!

Learn more

Supplemental guidelines

Commercial

Learn more

Tools & Checklist:

Supplemental guidelines

WCAG Ratings

Learn more

Supplemental guidelines

Testing Checklist

Learn more

Supplemental guidelines

Resources

Learn more

Consistent Navigation

  • Make sure you standardise your navigation. Keeping the position, style, colour and terminology consistent throughout your site makes it clear where to click and easier to follow. If reinforcing with icons, ensure they make sense, are consistent and look like part of the same family in terms of style.

Responsive Design (Reflow):

  • Periodically check your website on actual mobile devices and tablets as well as using the 'inspect' function in your web browser to emulate a cross section of devices and screen orientations. Look at it through different web browser applications too as they can show variation.

    It should be designed from a mobile first perspective as for most websites, more users will be viewing on their mobile device.

Avoid Flickering Content:

  • Be mindful that some people are sensitive to flashing or flickering content. Review your website to make sure it doesn't contain elements that could trigger seizures or cause discomfort, whether within video footage or graphic effects.

It's important to look beyond ticking the boxes for WCAG AA compliance. The overall objective of accessibility is to remove barriers and make things easier for everyone.
There are other things that will make your site more accessible that aren't necessary for AA compliance.

Continue your learning here:

Supplemental guidelines

Mobile First!

Learn more

Supplemental guidelines

Commercial

Learn more

Tools & Checklist:

Supplemental guidelines

WCAG Ratings

Learn more

Supplemental guidelines

Testing Checklist

Learn more

Supplemental guidelines

Resources

Learn more