diff --git a/index.html b/index.html index 0669179..35ed060 100644 --- a/index.html +++ b/index.html @@ -16,7 +16,7 @@

Accessibility Guidelines Summary

This document provided by TAB will help you quickly get up to speed with the Web Content Accessibility Guidelines (WCAG) 2.1, and avoid common accessibility mistakes.

It only covers Level A and Level AA requirements, which are referenced in public sector procurement laws in the UK, US public sector procurement laws, EU public sector procurement laws and public sector procurement laws around the world. - +

These guidelines apply to both native apps and web-based apps, except for three which are labelled Web only.

This summary is a simplification. If you're not sure how a guideline applies, check the official WCAG 2.1.

@@ -121,7 +121,7 @@

1.3. Create content that can be presented in different ways
  • Level A
  • Design
  • -
    If you give tips or instructions, don't assume that users can perceive colour, size, shape, sound or the location of elements on screen.
    +
    If you give tips or instructions, do not assume that users can perceive colour, size, shape, sound or the location of elements on screen.
  • @@ -240,7 +240,7 @@

    2. Easy to operate

    Your website/app must be easy to navigate and use, no matter how someone interacts with it.

    -

    For example people who don't use a mouse may use their voice, or press the 'Tab' key to move their keyboard's focus to interactive controls.

    +

    For example people who do not use a mouse may use their voice, or press the 'Tab' key to move their keyboard's focus to interactive controls.

    2.1. Make all functionality work with a keyboard

    @@ -262,7 +262,7 @@

    2.1. Make all functionality work with a keyboard

  • Design
  • Code
  • -
    Make sure that keyboard-only users don't get trapped within any element.
    +
    Make sure that keyboard-only users do not get trapped within any element.