Read time: 1 minute 30 seconds
Describe and present content in a way that all users can interpret and understand.
Why it's important
- Briana has a lower technical literacy level. Briana needs a site’s layout to be clear.
- Sebastián has low vision. Sebastián uses a screen reader to navigate the web.
- Merindah has a newborn and attention is often divided. Merindah needs to be able to understand a site’s contents at a glance.
- Darren is undergoing a crisis. Darren needs to quickly find the right advice.
Steps to take
- Read the Australian Government Content Guide on content structure.
- Write descriptive page titles. Users who use assistive technologies like screen readers may not be able to use visual cues to determine a page’s purpose. Make sure your page titles concisely convey each page’s focus.
- Make sure you have good heading structure. Headings are used for navigation by some users.
- Headings must clearly describe the topic or the following section. Use section headings to organise the content.
- Use clear row and column headings for tables. This makes it easier to understand tabular information and helps screen readers navigate tables.
- Use lists as they help users skim content.
- Indicate changes in language (for example, when including a foreign word in a predominantly English text). This will help people using screen readers, people with cognitive disability and people using braille translation software to fully understand your content.
- Determine whether the HTML document has a language attribute so that screen readers will read it with the correct accent and pronunciation. For example: <htmllang="en">. (If you’re not comfortable taking this step, feel free to ask a developer on your project team to help).
- Provide clear labels and instructions with forms. Labels must clearly describe the purpose of the form element.
- Use a screen reader or simulator to make sure you can land on controls and that they’re announcing things as they should.
Web Content Accessibility Guidelines
- 1.3.1 Info and Relationships
- 2.4.6 Headings and Labels
- 3.3.2 Labels or Instructions
- 3.3.3 Error Suggestion