Quick Wins

Summary

 Ensure that there is sufficient colour contrast on all areas of the application.

• Use HTML features appropriately to indicate content structure such as the hierarchy of headings using H1 through to H6 in a hierarchical manner to inform screen reader users
• Label input fields appropriately and explicitly associate form controls with their labels
• Identify data tables appropriately with table markup, along with table headers andcaptions
• Ensure that webpages can be used using a keyboard, and there is sufficient contrast when a user focuses on an element
• Alert users to changes of context on a page, such as a pop up or dialog, and programmatically set focus to that layer
• Provide captions and Audio description on video that has important speech or sound
• Provide a skip to content link on each page that will jump to the user to the main content of the page
• Ensure that images have an appropriate alt text description. 
• Provide an accessibility statement for each unique application, giving advice and guidance, where necessary, for disabled users to navigate the application

Resources for developers and designers

The following resources are for developers and designers in ensuring that they are creating accessible web applications.

General

• Web Content Accessibility Guidelines 2.1 – the definitive set of guidelines for building accessible content from the W3C’s Web Accessibility Initiative.
• How to Meet WCAG 2.1 - A customizable quick reference to Web Content Accessibility Guidelines 2.1 requirements (success criteria) and techniques.
• Techniques for WCAG 2.1 - Techniques and Failures for Web Content Accessibility Guidelines 2.1
• Understanding WCAG 2.1 - A guide to understanding and implementing Web Content Accessibility Guidelines 2.1
• How WCAG 2.1 applies to mobile - Mobile Accessibility: How WCAG 2.1 and Other W3C/WAI Guidelines Apply to Mobile