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

[Accessibility] Discussion: <main> and <section> tag structure #12869

Closed
aphelionz opened this issue Jul 14, 2017 · 2 comments · Fixed by #14243
Closed

[Accessibility] Discussion: <main> and <section> tag structure #12869

aphelionz opened this issue Jul 14, 2017 · 2 comments · Fixed by #14243
Assignees
Labels
bug Fixes for quality problems that affect the customer experience discuss Project:Accessibility

Comments

@aphelionz
Copy link
Contributor

For ease of screen reader navigation, we should talk about transitioning the page structure to use <main> tags as well as <section> tags.

@timroes
Copy link
Contributor

timroes commented Jul 14, 2017

This discussion might be now linked to #11516 .

I would in general love to have a proper main, section structure. It might also get us rid of any skip links and would still leave us flexible enough, to initially focus within the page somewhere (e.g. the query bar), without having larger problems with the skipping links (since they might be more likely at the beginning of the page).

I think we should look at each app individually and sketch a grid, for that page to determine each sections (like @aphelionz did in #12633) and maybe also other landmark roles, like search, complementary (if we at all want to use it) and the appropriate labels for those sections.

@tbragin tbragin added the bug Fixes for quality problems that affect the customer experience label Jul 28, 2017
@chrisronline
Copy link
Contributor

This feels like a larger request. Let's move to phase 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience discuss Project:Accessibility
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants