Top 4 Steps You Can Take to Build WCAG-Compliant Website Navigations
Everyone navigates websites in different ways. Physical challenges, even personal preferences, affect the way in which someone traverses a site. Taking the steps to make sure that your site is accessible for screen readers, alternative pointers, and other assistive devices enables a larger set of people to access and use your site.
One of the first things to do is understand how people navigate your website so you can provide alternate options for screen readers and other assistive devices. Let’s dive into that in more depth.
Understand How People Navigate Your Website
Navigation – hamburgers, fly-outs, mega menus, footer menus, sidebar menus, breadcrumbs, and others – matters for usability. So, the amount of time spent on menus and navigation structures should be reflective of their impact on the overall user experience.
Most of us spend enormous amounts of time online and we tend to have a pretty good handle on how sighted people navigate – there's a general flow to how eyes move (depending on a language’s directionality) and certain things catch our attention due to size or placement. However, assistive technology users navigate in completely different ways.
Screen readers offer several ways to navigate a page.
An afternoon learning to navigate by screen reader can be a real brain twister; it’s nothing at all like visual navigation.
The most familiar non-mouse navigation method to sighted users is the simple focusable-item to focusable-item tab behavior using a keyboard. However, readers can also navigate from heading tag to heading tag, by line, by paragraph, or even by letter. Several assistive tools also navigate by landmark. Landmarks are tags like , ,