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

Update the algorithm to handle roles where naming is not supported #53

Merged
merged 2 commits into from Jun 27, 2019

Conversation

joanmarie
Copy link
Contributor

@joanmarie joanmarie commented Jun 18, 2019

Add a statement to the end of Step 1 ("initialize") stating that if the
root node's role doesn't support naming, return the empty string. At the
present time, this impacts nothing because all roles currently support
naming. If that changes within the ARIA spec, this modification is meant
to accomplish the following:

<span aria-label="bar">foo</span>: The span has no name.

<button><span aria-label="bar">foo</span></button>: The button's
accessible name is "bar" (but the span itself has no name).

In other words, it prohibits generic elements themselves from getting
names, but preserves the name calculation results authors might be
expecting in currently-deployed content.

Add a statement to the end of Step 1 ("initialize") stating that if the
root node's role doesn't support naming, return the empty string. At the
present time, this impacts nothing because all roles currently support
naming. If that changes within the ARIA spec, this modification is meant
to accomplish the following:

<span aria-label="bar">foo</span>: The span has no name.

<button><span aria-label="bar">foo</span>: The button's accessible name
is "bar" (but the span itself has no name).

In other words, it prohibits generic elements themselves from getting
names, but preserves the name calculation results authors might be
expecting in currently-deployed content.
@joanmarie joanmarie requested review from accdc and jnurthen June 18, 2019 18:49
@joanmarie
Copy link
Contributor Author

@accdc and @jnurthen: Here is how I think we can keep the AccName spec in harmony with the ARIA spec even with names being prohibited (or unsupported) on generic roles. Please review. Thanks in advance!

@carmacleod
Copy link
Contributor

Pretty simple. :)

Also remove "initialize" because step 1 is no longer purely
initialization.

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

Successfully merging this pull request may close these issues.

None yet

2 participants