WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Where Does The Idea Screen Reader Users Use Tab for Main Navigation Come From?

for

From: Michael Bullis
Date: Oct 11, 2018 8:44AM

I'd like to think of myself as a pretty experienced screen reader user and I seldom, if ever, think of using tab navigation. I first look at headings with the h and if that doesn't work I use the n key for "next blank line, because it's most likely to get me to new sections. If the site clearly indicates tab navigation I'll use it.


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: Thursday, October 11, 2018 10:05 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Where Does The Idea Screen Reader Users Use Tab for Main Navigation Come From?

Hi Reuben, I was wondering the same thing and hope Brandon can clarify that part of his question, but my guess was that if you only focus on tab navigation, then the developer will make sure that all form elements have an accessible name and all links have appropriate context but they might not focus on other semantic elements such as headings, lists, tables, images, etc, which are only navigated to using screen reader shortcut keys or via the arrow keys. If that happens, then the screen reader user would miss out on a lot of information and organization that is not properly tagged.

I use the tab key as one of my first testing scenarios to make sure I can get to and interact with all interactive elements, that they all have a focus indicator, and that they all have an accessible name.

On Thu, Oct 11, 2018 at 7:54 AM Reuben Turk < <EMAIL REMOVED> > wrote:

>
> I guess the part I'm not understanding relates to this part of the
> original
> post:
>
> "It's harmful when developers make an experience that is only
> accessible using tab and I miss it because I'm using the arrow keys."
>
>
>