Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

Comment on 2.4.12 Accessible Name #477

Closed
AidanA11y opened this issue Oct 9, 2017 · 4 comments
Closed

Comment on 2.4.12 Accessible Name #477

AidanA11y opened this issue Oct 9, 2017 · 4 comments

Comments

@AidanA11y
Copy link

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.

@DavidMacDonald DavidMacDonald self-assigned this Oct 9, 2017
@DavidMacDonald
Copy link
Contributor

Proposed response:

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.

@AidanA11y
Copy link
Author

@DavidMacDonald thanks, that makes sense then

@joshueoconnor
Copy link
Contributor

@awkawk
Copy link
Member

awkawk commented Oct 27, 2017

Proposed response approved in 10/26/17 WG call.

@awkawk awkawk closed this as completed Oct 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants