Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NVDA does not recognize the region landmark role (even when it is a valid ARIA role) #3741

Closed
nvaccessAuto opened this issue Dec 31, 2013 · 7 comments
Closed

NVDA does not recognize the region landmark role (even when it is a valid ARIA role) #3741

nvaccessAuto opened this issue Dec 31, 2013 · 7 comments
Assignees
@jcsteh
Labels
enhancement
Milestone
2014.2

Comments

@nvaccessAuto
Copy link

Reported by Birkirrg on 2013-12-31 14:56
Occasionally none of the standard landmark roles applies to a section of a webpage. It may still be appropriate to give it a landmark and for that purpose the region role is appropriate (see W3C ARIA specs where role is a valid ARIA tag), Div with role="region" and an aria-label can be very useful. NVDA, however, does not recognize "region" as a landmark role and does not announce it or its aria-label property. The information is available in the browser doms, at least for IE and Firefox, and is announced by some other assistive technologies.
Blocked by #1195
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-01-07 01:08
According to the ARIA spec, region isn't actually considered a landmark (its superclass role is not landmark), so mapping it to landmarks is controversial and perhaps a spec violation. Do other ATs jump to role="region" elements when you navigate by landmark?

See also #1195.

@nvaccessAuto
Copy link
Author

Comment 3 by bgaraventa on 2014-02-09 01:53
Hi,
The feedback typically conveyed in JAWS for example is to announce the name of the region and the word region at the beginning of the content, then to announce the region name followed by the wording region end at the end of the content.

The value of this, is that it clearly defines the boundaries of a region, which is very helpful for menus, dialogs, popups, and other types of content where it may be unclear where one section starts versus another.

E.G

Dialog content here

Which then sounds like the following in JAWS:

Dialog region
Dialog content here
Dialog region end

Which can be quickly moved to by pressing 'r' to jump between defined regions.

Hopefully this helps.

Best wishes,
Bryan

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2014-02-19 07:21
Changes:
Milestone changed from None to next

@nvaccessAuto
Copy link
Author

Comment 5 by jteh on 2014-02-19 07:21
This work will be based on the code for #1195.

@nvaccessAuto
Copy link
Author

Comment 6 by James Teh <jamie@... on 2014-02-20 06:52
In [41e2ffc]:

Merge branch 't3741' into next

Incubates #3741.

Changes:
Added labels: incubating

@nvaccessAuto
Copy link
Author

Comment 7 by James Teh <jamie@... on 2014-03-18 18:39
In [28a1b81]:

In browse mode, labelled regions are now treated as landmarks.

Fixes #3741.

Changes:
Removed labels: incubating
State: closed

@nvaccessAuto
Copy link
Author

Comment 8 by jteh on 2014-03-18 18:40
Changes:
Milestone changed from next to 2014.2

@nvaccessAuto nvaccessAuto added this to the 2014.2 milestone Nov 10, 2015
@nvaccessAuto nvaccessAuto mentioned this issue Nov 10, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jcsteh jcsteh

Labels
enhancement
Projects
None yet
Milestone
2014.2
Development

No branches or pull requests
2 participants
@jcsteh @nvaccessAuto