Re: Keyboard controls for landmarks

Exposing landmark names:
Even a lay user not familiar with HTML coding  quickly finds out  the
landmark names main / search / navigation etc. as one navigates by
landmark and the screen reader exposes these names.
Now how does a non-AT user (sighted keyboard user) identify the
landmmark names if the user agent permitted navigation by landmarks?
This user will see the various sections of the page and might want to
navigate to search form or right side complementary section.
How will he know it is called the main or complementary section?

Sailesh


On 4/7/13, Patrick H. Lauke <redux@splintered.co.uk> wrote:
> On 07/04/2013 16:20, Steve Faulkner wrote:
>> they don't expose the aria role as an attribute in the DOM, its not how
>> it works.
>
> As a developer, I'd actually find that sort of thing useful. Any reason
> why not? For instance, it would make writing browser extensions that,
> say, jump to anything with role="main" (either defined as such in HTML,
> or given automatically by the browser, such as a <main> element),
> trivially easy to implement.
>
> P
> --
> Patrick H. Lauke
> ______________________________________________________________
> re·dux (adj.): brought back; returned. used postpositively
> [latin : re-, re- + dux, leader; see duke.]
>
> www.splintered.co.uk | www.photographia.co.uk
> http://redux.deviantart.com | http://flickr.com/photos/redux/
> ______________________________________________________________
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> ______________________________________________________________
>
>

Received on Monday, 8 April 2013 02:25:41 UTC