In this section
- Use structural and semantic markup properly and validate code
- Aim for maximum consistency
- Convey information so everyone can understand it
- Use JavaScript wisely
- Prioritise information, maximise readability and scanning
References for this section
WCAG 2.1
- 1.3.1 Info and Relationships (A)
- 1.3.3 Sensory Characteristics (A)
- 1.4.1 Use of Colour (A)
- 2.4.6 Headings and Labels (AA)
- 2.5.6 Concurrent Input Mechanisms (AAA)
- 3.2.3 Consistent Navigation (AA)
- 3.2.4 Consistent Identification (AA)
- 4.1.1 Parsing (A)
- 4.1.2 Name, Role, Value (A)
EN 301 549 v 2.1.2
- 9.1.3.1 Info and Relationships
- 9.1.3.3 Sensory Characteristics
- 9.1.4.1 Use of Colour
- 9.2.4.6 Headings and Labels
- 9.3.2.3 Consistent Navigation
- 9.3.2.4 Consistent Identification
- 9.4.1.1 Parsing
- 9.4.1.2 Name, Role, Value
Videos
- W3C Perspectives - Keyboard
- Low Vision: Challenging Assumptions and Understanding Differences - W3C Digital Accessibility Foundations
- Evaluating Web Accessibility - W3C Resources Overview
- Accessibility for People with Cognitive Disabilities, Low Literacy, Low Proficiency - W3C
- Just use button - A11ycasts #05
Further reading
- W3Docs - List of Deprecated HTML Attributes
- W3Docs - List of Deprecated HTML Tags
- Why Consistency is Important to Accessible Design
- Accessibility according to actual people with disabilities
- Accessibility testing as a screen reader user - TPGi
- Accessibility according to actual people with disabilities - Axess Lab
- W3C - Pointer Events Example
- Is Infinite Scrolling Accessible? - Bureau of Internet Accessibility