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

Implicit values for required properties section needs revising #966

Closed
jnurthen opened this issue Apr 29, 2019 · 5 comments · Fixed by #1414
Closed

Implicit values for required properties section needs revising #966

jnurthen opened this issue Apr 29, 2019 · 5 comments · Fixed by #1414
Assignees
Labels
editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo
Milestone

Comments

@jnurthen
Copy link
Member

Section 8.6 states
http://w3c.github.io/aria/#state_property_processing

However, required states and properties that are absent are an author error. Missing required states and properties are treated as if they were present and have an implicit neutral value that is not necessarily their default value. For example, the default value of aria-expanded is undefined, meaning neither expandable nor collapsible. But that does not apply to the case of a combobox. In this case, aria-expanded is needed to convey the expandable/collapsible nature of the combobox. Thus, the implicit value of aria-expanded for the combobox role is false, meaning expandable (and currently collapsed). The characteristics table associated with each WAI-ARIA role has an "Implicit Value for Role" entry that specifies the value of a state or property to use in the context of that role when the state or property is missing.

This needs revising due to the fact required states and properties no longer have implicit values

@carmacleod
Copy link
Contributor

5.2.9 Implicit Value for Role needs revising as well:

Many states and properties have default values. Occasionally, the default value when used on a given role should be different from the usual default. Roles that require a state or property to have a non-standard default value indicate this in the "Implicit Value for Role". This is expressed in the form "Default for state or property name is new default value". Roles that define this have the new default value for the state or property if the author does not provide an explicit value.

@jnurthen
Copy link
Member Author

@carmacleod I'm not sure what needs changing there. Can you clarify?

@carmacleod
Copy link
Contributor

@jnurthen

I'm not sure what needs changing there. Can you clarify?

You are absolutely correct - no changes needed. Sorry about that. I initially saw "Roles that require a state or property to have a non-standard default value" and equated it to the statement that "required states and properties no longer have implicit values", however after reading the paragraph again, I see that it is not related.

@jnurthen jnurthen added this to the ARIA 1.2 milestone Sep 28, 2019
@jnurthen jnurthen self-assigned this Sep 28, 2019
@scottaohara
Copy link
Member

scottaohara commented Oct 2, 2019

looking at this i noticed that option still has
"Implicit Value for Role: Default for aria-selected is false."

I'll start a branch/PR to at least remove that to get this work started.

edit: i will NOT start a branch/pr per followup comment

@jnurthen
Copy link
Member Author

jnurthen commented Oct 2, 2019

looking at this i noticed that option still has
"Implicit Value for Role: Default for aria-selected is false."

I'll start a branch/PR to at least remove that to get this work started.

take a look at #799 for this

@jnurthen jnurthen modified the milestones: ARIA 1.2, ARIA 1.3 Nov 19, 2019
@jnurthen jnurthen added the editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo label Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants