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

Context-sensitive navigation to webpage regions of given types #195

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 7 comments
Closed

Context-sensitive navigation to webpage regions of given types #195

nvaccessAuto opened this issue Jan 1, 2010 · 7 comments

Comments

@nvaccessAuto
Copy link

@nvaccessAuto nvaccessAuto commented Jan 1, 2010

Reported by benjaminhawkeslewis on 2008-10-11 12:31
Allow rapid navigation to regions of a given type within webpages, web applications and widgets, using lists and/or next/last shortcut keys.

Key types include: navigation areas, main content, articles, and search functionality. These would be contextualized if you were within a particular widget.

Potential markup to support this includes HTML4 markup (MENU, DIR, REL="search" pointing to an internal fragment), proposed ARIA landmark roles ("navigation", "main", "search"), proprietary extensions (INPUT TYPE="search") and proposed HTML5 markup (NAV, SECTION, ARTICLE).

Labels could be derived for regions from headings, TITLE attributes, and proposed ARIA markup like LABELLEDBY.

Heuristics might be able to provide similar functionality even in pages without this markup.

Compare discussion of how ARIA landmark roles should be used and interpreted at:

Blocked by #192

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Jan 1, 2010

Comment 1 by benjaminhawkeslewis on 2008-10-11 12:33
Changes:
Changed title from "Context-sensitive shortcuts for document and application regions of given types" to "Context-sensitive navigation to webpage regions of given types"

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Jan 1, 2010

Comment 2 by jteh on 2008-10-12 00:30
Would it be correct to call all of these regions "landmarks" (as opposed to "ARIA landmarks")? Accessibility APIs should have a concept of "landmarks"; see MozillaBug:459395. This will allow the various forms of markup to be exposed simply as landmarks, thus unifying the interface to ATs.

Note that this functionality can (and probably should) only be available in our virtual buffers. Web applications (i.e. where document browsing concepts are not used at all) should act as desktop applications and provide similar ways to navigate.

What do you mean by contextualising if in a particular widget? Can you provide an example?

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Jan 1, 2010

Comment 3 by tlog333 on 2009-01-13 07:59
Verifying if this should be included in new issue or can be added here.

NVDA should begin reading from role="main" content on a webpage by default. This would allow in the future for authors to remove the skip navigation link that currently exists on their pages by appropriately marking up the content. One example page is http://codetalks.org

A user navigating to the http://codetalks.org should start from the section heading "Main Page" rather than hearing the banner and navigation bars.

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Jan 1, 2010

Comment 4 by jteh (in reply to comment 3) on 2009-01-13 11:38
Replying to tlog333:

Verifying if this should be included in new issue or can be added here.

It could possibly be encompassed by this ticket. However, because this ticket is quite broad and I'm still not entirely sure what this ticket is about, I'd recommend opening a new ticket. File it under virtual buffers.

@derekriemer
Copy link
Collaborator

@derekriemer derekriemer commented Jun 28, 2016

Is this still relevant?

@ehollig
Copy link
Collaborator

@ehollig ehollig commented Jun 23, 2018

Bringing this up again. Is this still relevant, or is this resolved from #192? This could also not be entirely clear on what this ticket is about,.

@Adriani90
Copy link
Collaborator

@Adriani90 Adriani90 commented Jun 6, 2020

Articles are now navigable, you can assign a gesture for it and enable this in document formatting settings. Main navigation areas can be navigated by d for landmarks or m for regions. Search field can easilib be reached by pressing e for edit field. Thus, I am closing this issue since NVDA already provides this feature. I there is something still missing here, please create a new issue for the specific navigation area that you think would be useful to have contained into the quick navigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants