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

Problematic User Agents MUST NOT statement needs to be qualified #1476

Closed
joanmarie opened this issue Apr 29, 2021 · 1 comment · Fixed by #1778
Closed

Problematic User Agents MUST NOT statement needs to be qualified #1476

joanmarie opened this issue Apr 29, 2021 · 1 comment · Fixed by #1778
Assignees
@jnurthen @scottaohara
Labels
Agenda clarification clarifying or correcting language that is either confusing, misleading or under-specified F2FCandidate Candidate topics for F2F (or Virtual F2F) meeting high user impact
Milestone
2023

Comments

@joanmarie
Copy link
Contributor

This pull request introduced the following statement into ARIA 1.3:

User Agents MUST NOT expose an ARIA attribute to the platform accessibilty API when the element's computed role prohibits use of the attribute.

Given something like <div tabindex="0" aria-label="foo">bar</div>, in which aria-label is prohibited (generic role), that means we need implementors to NOT expose "foo". We will not get vendor buy-in for this. Trust me. Yes, it's lousy authoring which is not ARIA compliant. But given the explicit author-provided label, user agents aren't going to ignore it in favor of "bar" or worse, nothing.

I think we need to modify the above statement to allow for User Agents to expose "foo" as part of handling author errors.
@jnurthen jnurthen added this to the ARIA 1.3 milestone Apr 29, 2021
@jnurthen jnurthen mentioned this issue May 25, 2021
Closed
@joanmarie joanmarie mentioned this issue Jun 8, 2021
Open
@spectranaut spectranaut added this to James Nurthen in ARIA 1.3 Jun 7, 2022
@scottaohara scottaohara added clarification clarifying or correcting language that is either confusing, misleading or under-specified high user impact labels Jul 1, 2022
@jnurthen jnurthen added the Agenda label Aug 2, 2022
@spectranaut spectranaut added the F2FCandidate Candidate topics for F2F (or Virtual F2F) meeting label Aug 12, 2022
@spectranaut
Copy link
Contributor

Discussed in: https://www.w3.org/2022/08/11-aria-minutes#t06

scottaohara added a commit that referenced this issue Aug 18, 2022
@scottaohara
Resolving user agent must not statement and whitespace defs
8d066f6 
Related to w3c/core-aam#128 
Fixes #1476

- link to definition of whitespace in the aria-braillelabel and aria-brailleroledescription, aria-roledescription sections
- remove reference to whitespace from user agents must not aria-roledescription requirement
- remove author error correction User Agents MUST NOT expose prohibited ARIA attributes statement from correcting for author errors section.
	- adds authors MUST NOT specify aria-roledescription on elements with roles where the attribute is prohibited.
	- removed non-normative "should" from aria-brailleroledescription
	- adds authors MUST NOT use aria-brailleroledescription where prohibited 
	- adds authors MUST NOT use aria-label and aria-labelledby where prohibited
@scottaohara scottaohara mentioned this issue Aug 18, 2022
Merged
@spectranaut spectranaut removed this from James Nurthen in ARIA 1.3 Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jnurthen jnurthen

@scottaohara scottaohara

Labels
Agenda clarification clarifying or correcting language that is either confusing, misleading or under-specified F2FCandidate Candidate topics for F2F (or Virtual F2F) meeting high user impact
Projects
None yet
Milestone
2023
Development

Successfully merging a pull request may close this issue.

Resolving user agent must not statement and whitespace defs w3c/aria
4 participants
@spectranaut @jnurthen @joanmarie @scottaohara