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

Title should not contribute to accName for generic elements #506

Open
scottaohara opened this issue Oct 5, 2023 · 8 comments
Open

Title should not contribute to accName for generic elements #506

scottaohara opened this issue Oct 5, 2023 · 8 comments

Comments

@scottaohara
Copy link
Member

see the title of this issue. authors 'shouldn't' be naming generics, but a title could provide a name if no other method is provided - but it's probably the author's intent to provide a description in these cases (what good that will do, i don't know).

@scottaohara
Copy link
Member Author

related to w3c/aria#1981

closing #495 since apparently i had filed similar before

@spectranaut
Copy link
Contributor

spectranaut commented Oct 12, 2023

What is the change you are suggestion, specifically, in HTML? I'm just confused about why this issue is here...

@spectranaut
Copy link
Contributor

Discussed in today's meeting: https://www.w3.org/2023/11/02-aria-minutes.html#t10

It was decided to schedule a deep dive for this topic.

@cookiecrook
Copy link
Collaborator

cookiecrook commented Nov 2, 2023

I interpret @scottaohara's request to be the #comp_tooltip step in AccName should be changed from:

…if the current node has a Tooltip attribute, return its value.

To:

…if the current node does not have a computed role of generic, and has a Tooltip attribute, return its value.

If I'm correct, then @spectranaut is right that this issue should be moved from HTML-AAM to AccName.

@cookiecrook
Copy link
Collaborator

cookiecrook commented Nov 2, 2023

But then if title is not exposed as label on a generic, where should it be exposed? This is author-provided, human-readable text, and sometimes in the case of poorly coded sites, this is the only information an SR user has to go on. I'd object to a WG decision to suppress title (even on generics) from AT users unless there was another means to access that info.

@JAWS-test
Copy link

this issue should be moved from HTML-AAM to AccName

it is already in AccName: "If the root node's role prohibits naming, return the empty string"

But then if title is not exposed as label on a generic, where should it be exposed?

title is usually used for description. This means that a div with a title could theoretically have a description but no name. But then Accname would also have to be changed (see above quote from Accname). Whether this makes sense is another question, as the AT normally does not output a description for generic elements.

@cookiecrook
Copy link
Collaborator

Whether this makes sense is another question, as the AT normally does not output a description for generic elements.

And the engines don't usually expose a generic element with no label, so there may be nothing to hang the description on.

@MelSumner
Copy link

@accdc and I have dug into this some more. I'd like to have a deepdive on this topic and I would like to present on the topic. We need a good date for this though, considering that holidays are soon.

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

No branches or pull requests

6 participants