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.

Sign up for GitHub

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

Clarify behaviour if an author applies an ARIA global attribute on an element with an *inherited* role of presentation #759

Closed
jnurthen opened this issue May 14, 2018 · 0 comments
Closed

Clarify behaviour if an author applies an ARIA global attribute on an element with an *inherited* role of presentation #759

jnurthen opened this issue May 14, 2018 · 0 comments

Comments

@jnurthen
Copy link
Member

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26044

Clarify if an author applies an ARIA global attribute on an element with an inherited role of presentation, the user agent should expose the element to the accessibility tree, but the UA can use its own heuristics to determine the role (any role, including the generic role of the platform or API).
jnurthen added a commit that referenced this issue Jan 11, 2019
@jnurthen
Editorial?: Fix for #759
82ae6e7
joanmarie pushed a commit that referenced this issue Jan 15, 2019
@jnurthen @joanmarie
Editorial: Fix for #759 (#885)
2a72f09 
Clarify if an author applies an ARIA global attribute on an element with an inherited role of presentation, the user agent should expose the element to the accessibility tree.
joanmarie pushed a commit that referenced this issue Jan 15, 2019
@jnurthen @joanmarie
Editorial: Fix for #759 (#885)
ea61062 
Clarify if an author applies an ARIA global attribute on an element
with an inherited role of presentation, the user agent should expose
the element to the accessibility tree.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jnurthen @joanmarie