A11ying with Sanna - Testing for accessibility A little testing workshop

Help users understand your content

Using semantic HTML to provide structure to the page is important. With semantic HTML, assistive technologies will have much more information about the type of content on the page.

When you use semantic HTML, you reduce the need for ARIA markup. Semantic HTML is also more SEO friendly.

Headings provide structure

Headings should tell the user what content is below them. When the page content has good headings, the user can understand the page structure better.

Headings shouldn't be used for visual purposes.

Pay attention to heading levels

Each page should have one main heading, a H1 heading. After that, the heading levels should only increase by one. So after the H1 we should have only H2 headings. And after the H2s should come H3 headings.

While in many cases the wrong heading level doesn't necessarily cause problems, in the worst case the content will end up below the wrong section. And in these cases the headings violate accessibility requirements.

Links should tell the user where they go

Too generic link texts don't tell users much. In general it is recommended to avoid generic links such as read more or click here.

Links need to be understandable within their context. While it is possible to have read more make sense in a sentence, it isn't very user friendly. And if you have multiple read more links on the same page that say read more, they should then also take the user to the exact same location.

Improve link texts above the accessibility requirements

Aim to have link texts that are unique and understandable outside of their context. This is not a requirement before AAA level but it is better for accessibility.

For example, read more about the topic or read more about the author are much better than just read more.