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

Possible error in 3.1 HTML5 Sectioning Elements #239

Closed
ZoeBijl opened this issue Jan 18, 2017 · 3 comments
Closed

Possible error in 3.1 HTML5 Sectioning Elements #239

ZoeBijl opened this issue Jan 18, 2017 · 3 comments
Assignees
Labels
bug Code defects; not for inaccurate prose question Issue asking a question

Comments

@ZoeBijl
Copy link
Contributor

ZoeBijl commented Jan 18, 2017

The table lists the following as default landmark role for section:

region when it has an accessible name using aria-labelledby or aria-label

As @stevefaulkner said in a thread opened by @matatk [1]:

section always maps to region, it is only announced by AT when it has an accessible name.

Should we change this to reflect the ARIA spec and ARIA in HTML document?

[1] w3c/html-aria#64

@mcking65
Copy link
Contributor

I think it is the core AAM that conflicts with the ARIA spec. Assistive tech should not have to do extra checking to see if a region really is a landmark. The intent we had when making region a subclass of landmark and making name required was to make it so only named sections are regions.

I see @joanmarie is a step ahead of me and raised w3c/aria#513, which is the path I support.

@ZoeBijl
Copy link
Contributor Author

ZoeBijl commented Jan 18, 2017

Yes, I discussed this a bit with @joanmarie during/after today’s APA call.

Changed wording in my original post a bit.

@mcking65 mcking65 added bug Code defects; not for inaccurate prose question Issue asking a question labels Jan 19, 2017
@mcking65 mcking65 added this to the 1.1 PR milestone Jan 19, 2017
@mcking65 mcking65 self-assigned this May 21, 2018
@mcking65
Copy link
Contributor

w3c/aria#513 was closed and that means the text in the guidance is correct as written; no conflict.

Landmark Regions Guidance and Examples Development Project automation moved this from Next Steps to Complete Jun 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Code defects; not for inaccurate prose question Issue asking a question
Development

No branches or pull requests

2 participants