-
Notifications
You must be signed in to change notification settings - Fork 125
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
Should text content be used for aria-valuetext? #1308
Comments
I think in the case of |
More info about aria-valuetext in meter "When the element's values are contained within a range but those values are not numeric (such as "small", "medium" and "large"), or they are numeric but there is value in communicating more information than just a number, aria-valuetext is used to surface the text value to assistive technologies. Only use aria-valuetext when aria-valuenow is not sufficiently meaningful for users because using aria-valuetext will prevent assistive technologies from communicating aria-valuenow. |
I'm not sure there is anything to do here. Anyone disagree? |
Should the text content of an element that aria-valuetext may own but does not own be used as value for aria-valuetext, e.g.
Attention: In the example further required attributes are missing. But the question is whether the 3 should be interpreted as aria-valuetext. If not, this should perhaps be mentioned explicitly in the specification, so that, for example, in the first WHATWG example ("Instead, one would either not include the meter element, ..."), the assumption does not arise that the text content would be perceivable with AT.
See also: FreedomScientific/standards-support#419
The text was updated successfully, but these errors were encountered: