Unable to reproduce this issue on Windows 10 with chrome #56.0.2924.87 & #57.0.2987.110, able to switch between url links by pressing tab button

Attaching the screen-cast for reference.

carolynmacleod4@ Could you please look into it and let us know your observations.

Deleted: Issue 704698.mp4 4.3 MB

	Issue 704698.mp4 4.3 MB View Download

Sure, but wouldn't it be nice to be able to jump directly to the "Related Specs" without having to tab all the way through the left sidebar nav? Wouldn't it be nice to jump directly to the main without having to have a skip link?
I chose this page because it contains an excellent description of what a landmark is.
Note that it would also be nice to be able to navigate through headings using only the keyboard.
Imagine being able to quickly navigate through all of the chapters of a book even though the author did not provide a table of contents.
Imagine a web application with a huge list of links - a feed, maybe - on the left, but you can easily jump over that to the main or complimentary landmarks, or to another nav that you see on the right.
Imagine that you are somewhere in the middle of a large web page, and you want to jump to the header, or you need to see if there's a "Contact Us" link in the footer. With landmark navigation, you could easily do this.
More and more, page authors are organizing their page content into landmark regions. Screen reader users have had the capability to jump directly to specific landmarks and headings for years now, and it is a powerful feature.
I would like to have this feature available natively in the browser so that people who can only use a keyboard can quickly navigate to where they want to go.

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Wikipedia is a better example page: https://en.wikipedia.org/wiki/Main_Page
Say that you need to (or prefer to) use a keyboard.
If your favorite Wikipedia section is "On this day...", there's no way you're going to tab to it - you are going to type ctrl+F and type "on this day", then Esc and start reading from there. But if you are new to the page, you won't know the exact string to search for. You want to know what headings are on the page, and what landmarks are available. Screen readers are good at this, and there are extensions that can do this, too. But I want this capability baked in to the browser. That way, page authors would make sure to create pages with decent page structure - headings and landmarks - because they can see the benefit to users. And users would get used to having (and begin demanding <g>) well-structured pages.

A premium version of this feature would also provide a list of landmarks or headings so that the user can see them all and jump to the one they want. (Mouse users could take advantage of such a list also).
This has the potential to be a _really cool_ feature. Differentiating, even.
Please think about it, and talk about it, and have fun designing it.  :)

PS: You might want to change the Type: from Bug to Feature.

Also: Not specific to Windows. Applies to all platforms.

Seems this is a feature request, marking it as 'Untriaged' to get more inputs from dev.Please feel free to edit if this is not the case.

Thank you..!!

Here's a few decent test pages:
http://www.html5accessibility.com/tests/roles-land.html
http://www.html5accessibility.com/tests/structural-elements.html
http://pauljadam.com/demos/landmarks.html

More info:
Landmark regions can be defined by the page author by either using ARIA landmark roles (http://w3c.github.io/aria/aria/aria.html#landmark_roles), or HTML5 elements that default to having landmark roles (see summary, below, for a list of these elements). 

Note that the generic landmark role="region" - and its corresponding html "section" element - must have a label before it is considered a true landmark, whereas nav, aside, etc do not technically require a label to be a landmark (but they really ought to have one, particularly if there are more than one on a page). 

Note the sentence in the ARIA spec for region that says "Mainstream user agents [ed: eg. Chrome/Chromium] may enable users to quickly navigate to elements with role region.".  :)

Headings (h1, h2...) should also be navigable because they can implicitly define a section, however it would be easiest to treat implicitly-defined sections separately from explicitly-defined sections because unfortunately, without the guidance of a working outline algorithm, they can conflict.

Summary: 
- landmark roles: banner, complementary, contentinfo, form, main, navigation, region, search 
- html elements whose default role is a landmark: header, aside, footer, form, main, nav, section 
- heading content that may define an implied section: h1, h2, h3, h4, h5, h6

Here's the same feature request on other platforms (plus background discussion):
Safari: https://bugs.webkit.org/show_bug.cgi?id=172817
Edge: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/19436788-landmark-navigation
Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=670928

Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

How do I reopen this? It would be such a cool and useful feature.

Slack has implemented landmark navigation using F6 (SHIFT+F6) in their desktop (Electron) app; or CTRL+F6 (CTRL+SHIFT+F6) in browsers. It's quite nice. Please give it a try to get an idea of what landmark navigation could feel like if implemented natively in browsers.
https://get.slack.help/hc/en-us/articles/115003340723-Keyboard-accessibility-in-Slack-

Looping Julien@.
Please take a look into this issue as per C#15 & update accordingly.
Thanks..!

If I read this right it sounds more like a web platform accessibility request than native Chrome UI request, right? 

I will reopen the issue with a new component assigned to it and hopefully the right people will be able to see it and know how to handle this request.

Yes, this is a keyboard accessibility issue.
It is a request to give sighted keyboard-only users and keyboard power users the very powerful landmark and heading navigation capabilities that screen reader users have.

Currently, non-screen-reader keyboard users are stuck with only tab - and sometimes arrow keys - for navigating through web pages. If they know the exact text to jump to, they can use "find in page", but that's a pain for going back and forth between 2 commonly-used sections.

Here's an extension that gives a flavor of what this request is asking for (although, as an extension, it cannot use the F6 key): http://matatk.agrip.org.uk/landmarks/

I like this idea!

> I like this idea!

Awesome!!  :)

If you are interested in the 7 year history of this idea ;) then you could check out the 67-comment-long Firefox feature request: https://bugzilla.mozilla.org/show_bug.cgi?id=670928
(No worries if you'd rather not read all that... might be better to start with a clean slate... ;)

I can't seem to get any traction there (despite attempting several times to come up with a design), so if you want to scoop them, please do.  ;)