Skip to content

To support developers building accessible software under WCAG 2.1 AA guidelines

Notifications You must be signed in to change notification settings

JiscSD/web-accessibility-101

Repository files navigation

web-accessibility-101 ✨

To support developers using React in building accessible software under WCAG 2.1 AA guidelines.

In this repository you will find some information on web accessibility, split into sections and with code examples.
Try and complete the quick fire checklist below to see whether there are any missing from your product.


Contents:

  1. Colour
  2. Page Structure and Semantic HTML
  3. ARIA attributes
  4. Visual Content
  5. Keyboard Only
  6. Forms
  7. Tables
  8. Common Accessibility issues/Examples with UI libraries
  9. Testing resources

Quick fire checklist:

  • Is the lang attribute set to the correct language?
  • Does your codebase have documentation in a README and comments where necessary?
  • Is the HTML valid? (You can check with this W3 validator)

  • Does the design have accessible colours? If not, have the colours been checked?
  • Can you still navigate your site if it was in black and white?
    If no - read through the colour section.

  • Do all of your pages have unique and descriptive title tags?
  • Is there only one h1 heading present on each page?
  • Are the h tags in a logical order matching the structure?
  • Is semantic HTML used where possible?
    If no, read through the page-structure section.

  • Are ARIA attributes used if semantic HTML is not possible?
    If no, read through the aria section.

  • Do all images have descriptive alt text?
  • Does any visual/audio content have the option to pause?
  • Can you resize your website to 200% and still use it?
    If no, read through the visual-content section.

  • If you have a navigation header, is a 'skip to main content' link present?
  • Are interactive attributes focusable, with obvious visible styling on focus?
  • Can you tab through your website in a logical order without using your mouse?
    If no, read through the keyboard-only section.

  • Do your forms use clear labels and alternative text if needed?
  • Do your forms provide guidance to the user upon error?
  • Are all required fields marked?
  • Do all of your input fields have a purpose specified? e.g. input type="email"
    If no, read through the forms section.

  • Does your table have headers with listed scope of 'col' or 'row'?
  • Does your table include a Caption?
    If no, read through the tables section.

Contributing:

Want to contribute to this repository? Please do!
You can do this by...

  1. Creating an issue - if it is a minor addition or if it is a complicated accessibility issue that everyone can input into.
  2. Opening a Pull Request - if there is a particular area you would like to add a chunk of information or some examples to.

Bibliography/Useful Resources:

About

To support developers building accessible software under WCAG 2.1 AA guidelines

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published