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.
My only concern would be where the accessible name adds more clarity where multiple icons appear. For example, where a generic pencil icon with the word Edit appears next to sections of a page, If the author used an accessible name that was unique and descriptive (Edit Address, Edit Username) it seems that may fail, and the author would be forced to use ARIA to add these helpful distinctions.
The text was updated successfully, but these errors were encountered:
Thanks for your comment: Actually, its the other way around from the example provided above. The SC requires that the label be part of the name, not vice versa.
In the example you provide, the word "edit" appears as the label, the "name" which includes the word "edit" would be sufficient to pass the SC. The Dragon user would say "edit" and they would get numbers beside each of the edit fields and they would select the one they want.
This seems beneficial and easily testable.
My only concern would be where the accessible name adds more clarity where multiple icons appear. For example, where a generic pencil icon with the word Edit appears next to sections of a page, If the author used an accessible name that was unique and descriptive (Edit Address, Edit Username) it seems that may fail, and the author would be forced to use ARIA to add these helpful distinctions.
The text was updated successfully, but these errors were encountered: