E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 6 (In chronological order)

From: Mickey Williamson
Date: Mon, Jun 08 2015 12:16PM
Subject: Navigating via headings in VoiceOver
No previous message | Next message →

So I have a sample page with a list of links split into categories. Each
category is an h3. Like so:

<h3>Category 1</h3>
<ul>
<li>Link 1</li>
<li>Link 2</li>
</ul>
<h3>Category 2</h3>
<ul>
<li>Link 1</li>
<li>Link 2</li>
</ul>

And so on.

Using VO with Safari, I bring up a list of the headings and jump to
Category 2 by pressing enter on the Category 2 heading. That takes me to
the category 2 heading. But if I want to continue in the category and
press tab to navigate through the list of Category 2 links, I'm taken back
to the top of the page. Does that mean that I should always be adding
tabindex of 0 or 1 to all my headings? Or am I misusing VoiceOver?

Thanks,
Mickey

From: Moore,Michael (HHSC)
Date: Mon, Jun 08 2015 12:22PM
Subject: Re: Navigating via headings in VoiceOver
← Previous message | Next message →

I believe that the correct use of Voice Over would be to use reading commands to read by line or paragraph until you encounter a link or other active element. Then tab will take you to the next. The tab key only moves from active element to active element. Adding a tab-index of 0 to the headings would make it more difficult to navigate the page for sighted keyboard users.

Mike Moore
Accessibility Coordinator
Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
(512) 574-0091 (Cell)

From: Jonathan C. Cohn
Date: Mon, Jun 08 2015 1:40PM
Subject: Re: Navigating via headings in VoiceOver
← Previous message | Next message →

If you are doing this testing on a Macintosh then it will depend on your tracking settings on what happens. The tab is moving focus or keyboard while the quicknav keys will move the voiceover cursor.


Jonathan Cohn

> On Jun 8, 2015, at 2:22 PM, Moore,Michael (HHSC) < = EMAIL ADDRESS REMOVED = > wrote:
>
> I believe that the correct use of Voice Over would be to use reading commands to read by line or paragraph until you encounter a link or other active element. Then tab will take you to the next. The tab key only moves from active element to active element. Adding a tab-index of 0 to the headings would make it more difficult to navigate the page for sighted keyboard users.
>
> Mike Moore
> Accessibility Coordinator
> Health and Human Services Commission
> Civil Rights Office
> (512) 438-3431 (Office)
> (512) 574-0091 (Cell)
>
>

From: Rakesh P
Date: Mon, Jun 08 2015 7:47PM
Subject: Re: Navigating via headings in VoiceOver
← Previous message | Next message →

Check if you have used tabindex=1, when you use tab at any point in
the page you will be taken to the element that has tabindex 1
irrespective where you have started tabbing.

This could be the reason as far as I could remember.


On 6/8/15, Mickey Williamson < = EMAIL ADDRESS REMOVED = > wrote:
> So I have a sample page with a list of links split into categories. Each
> category is an h3. Like so:
>
> <h3>Category 1</h3>
> <ul>
> <li>Link 1</li>
> <li>Link 2</li>
> </ul>
> <h3>Category 2</h3>
> <ul>
> <li>Link 1</li>
> <li>Link 2</li>
> </ul>
>
> And so on.
>
> Using VO with Safari, I bring up a list of the headings and jump to
> Category 2 by pressing enter on the Category 2 heading. That takes me to
> the category 2 heading. But if I want to continue in the category and
> press tab to navigate through the list of Category 2 links, I'm taken back
> to the top of the page. Does that mean that I should always be adding
> tabindex of 0 or 1 to all my headings? Or am I misusing VoiceOver?
>
> Thanks,
> Mickey
> > > > >

From: Sean Curtis
Date: Mon, Jun 08 2015 10:20PM
Subject: Re: Navigating via headings in VoiceOver
← Previous message | Next message →

I think you'd use VO + Left/Right instead of tabbing. VoiceOver does read
the elements which have focus, but moving the VO cursor (what you're doing
when you browse headings using the Rotor menu or Quick Nav) does not change
what is focused as far as the browser is concerned.

From: Mickey Williamson
Date: Tue, Jun 09 2015 7:27AM
Subject: Re: Navigating via headings in VoiceOver
← Previous message | No next message

A PEBKAC <http://en.wiktionary.org/wiki/PEBCAK>; error. Thanks everyone! I
got it now.

Mickey


On Tue, Jun 9, 2015 at 12:20 AM, Sean Curtis < = EMAIL ADDRESS REMOVED = > wrote:

> I think you'd use VO + Left/Right instead of tabbing. VoiceOver does read
> the elements which have focus, but moving the VO cursor (what you're doing
> when you browse headings using the Rotor menu or Quick Nav) does not change
> what is focused as far as the browser is concerned.
> > > > >



--