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

revise meter authoring advice #1129

Merged
merged 3 commits into from
Apr 3, 2020
Merged

revise meter authoring advice #1129

merged 3 commits into from
Apr 3, 2020

Conversation

scottaohara
Copy link
Member

@scottaohara scottaohara commented Dec 7, 2019

closes #1123

to have similar authoring expectations to HTML’s meter element, the authoring adivce for the meter role is updated to remove the requirement for aria-valuemin and max, and instead indicate these attributes should have implicit defult values, similar to progressbar.

removes aria-valuemax and min from the required states and properties row of the characteristics table, and moves them to an Implicit Value for Role row.

Adds meter’s required aria-valuenow to the Fallback values for missing required attributes table


Preview | Diff

to have similar authoring expectations to HTML’s meter element, the authoring adivce for the meter role is updated to remove the requirement for aria-valuemin and max, and instead indicate these attributes should have implicit defult values, similar to progressbar.

removes aria-valuemax and min from the required states and properties row of the characteristics table, and moves them to an Implicit Value for Role row.

Adds meter’s required aria-valuenow to the Fallback values for missing required attributes table
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
Copy link
Contributor

@carmacleod carmacleod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 except for the one little nit suggested above.

[Edit: committed the suggested nit]

@carmacleod
Copy link
Contributor

@jnurthen This PR is ready for final review.

@jnurthen jnurthen merged commit 21b5aee into master Apr 3, 2020
jnurthen pushed a commit that referenced this pull request Apr 3, 2020
* to have similar authoring expectations to HTML’s meter element, the authoring advice for the meter role is updated to remove the requirement for aria-valuemin and max, and instead indicate these attributes should have implicit defult values, similar to progressbar.
* removes aria-valuemax and min from the required states and properties row of the characteristics table, and moves them to an Implicit Value for Role row.
* Adds meter’s required aria-valuenow to the Fallback values for missing required attributes table
Co-authored-by: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>
@a11ydoer
Copy link
Contributor

a11ydoer commented Apr 6, 2020

@scottaohara APG is very near to close this issue. Would you like to have a final look?
w3c/aria-practices#1279

carmacleod pushed a commit that referenced this pull request May 7, 2020
* to have similar authoring expectations to HTML’s meter element, the authoring advice for the meter role is updated to remove the requirement for aria-valuemin and max, and instead indicate these attributes should have implicit defult values, similar to progressbar.
* removes aria-valuemax and min from the required states and properties row of the characteristics table, and moves them to an Implicit Value for Role row.
* Adds meter’s required aria-valuenow to the Fallback values for missing required attributes table
Co-authored-by: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>
@jnurthen jnurthen deleted the issue_1123 branch July 23, 2020 22:27
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.

meter role should have optional aria-valuemin/max with defaults
5 participants