You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.
I agree with the idea here, but this SC is hard to parse.
"For user interface components with labels that include text or images of text, the name contains the text presented visually."
The last clause can be read as "contains the text that is visually presented" or "contains the text and presents it visually." I think you mean the first, but I had to read it about 5 times to decide.
The word "name" is overloaded. This use of "name" would be more clear as "accessible name" or "accessibility api name"
The text was updated successfully, but these errors were encountered:
[Official WG response]
Thank you for the comment. We will change the SC text editorially to read:
"For user interface components with labels that include text or images of text, the name contains the text that is presented visually."
Regarding the use of "name" the Working Group is using the term consistently as it was used in WCAG 2.0 and made a decision to not change the glossary definition. This can be reconsidered for Silver.
The WG decided on the above response, so we changed the text in the comment containing the proposed response to read "[Official WG Response]". Please confirm is you are satisfied with the response within 3 days. If we haven't heard a response by then we will regard the resolution as satisfactory.
I agree with the idea here, but this SC is hard to parse.
"For user interface components with labels that include text or images of text, the name contains the text presented visually."
The last clause can be read as "contains the text that is visually presented" or "contains the text and presents it visually." I think you mean the first, but I had to read it about 5 times to decide.
The word "name" is overloaded. This use of "name" would be more clear as "accessible name" or "accessibility api name"
The text was updated successfully, but these errors were encountered: