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

There's no name computation for the area element #176

Closed
dd8 opened this issue Apr 3, 2019 · 3 comments · Fixed by #187
Closed

There's no name computation for the area element #176

dd8 opened this issue Apr 3, 2019 · 3 comments · Fixed by #187
Assignees

Comments

@dd8
Copy link

dd8 commented Apr 3, 2019

area isn't listed in the Accessible Name and Description Computation
https://www.w3.org/TR/html-aam-1.0/#accessible-name-and-description-computation

although it is listed in HTML Element Role Mappings
https://www.w3.org/TR/html-aam-1.0/#el-area

<img src="usa.png" alt="Map of United States" usemap="#us_map">
<map name="us_map">
 <area alt="Alabama" href="alabama.htm" shape="poly" coords="..." />
 <area alt="Alaska" href="alaska.htm" shape="poly" coords="..." />
 ....
 <area alt="Wyoming" href="wyoming.htm" shape="poly" coords="..." />
</map>

There are two different ALT's involved here - one on the IMG referencing the MAP AREAs and the ALT on each AREA - and there could be null ALTs on either element (or both elements). This poses a few questions:

  1. Should the accessible name of an AREA be a combination of both IMG ALT and AREA ALT? That could get very verbose with the example above when reading each AREA link.
  2. If not a combination then should IMG ALT be exposed in some other way, such as mapping IMG ALT to AREA link accessible description?
  3. What should happen when IMG has null ALT, but IMG USEMAP references MAP AREAs with non-null ALT? Should it set the image to role=presentational, even though the USEMAP attribute says the image isn't presentational? If AREA is voiced as a combination of IMG ALT and AREA ALT then there will be cases where you don't want any IMG ALT to reduce verbosity.
  4. What should happen when IMG has non-null ALT, but AREA has a null ALT?

To get an idea of UA differences currently:

  • NVDA 2018 with FF60 voices IMG ALT and AREA ALT as link title
  • JAWS 2018 with IE11 voices AREA ALT as link title
  • JAWS 2018 with FF60 voices AREA HREF as link title
  • VoiceOver with Safari on macOS 10.13 voices AREA ALT as link title
  • VoiceOver with Safari on iOS 11.4 voices AREA ALT as link title, but only reads IMG ALT (and not AREA ALT) when the speak screen gesture is used (i.e. no link roles read, and no indication AREA links exist - the only way to find the AREA links seems be setting rotor is set to Links, and using the move to next rotor item gesture )

MDN page here:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/area

WCAG technique here:
https://www.w3.org/TR/WCAG20-TECHS/H24.html

Tested support here:
https://www.powermapper.com/tests/screen-readers/labelling/area-alt/
https://www.powermapper.com/tests/screen-readers/labelling/area-alt-img-null-alt/
https://www.powermapper.com/tests/screen-readers/labelling/area-title/
https://www.powermapper.com/tests/screen-readers/labelling/area-aria-label/
https://www.powermapper.com/tests/screen-readers/labelling/area-aria-labelledby/

@asurkov
Copy link
Contributor

asurkov commented Apr 3, 2019

there is mapping for area element, see https://w3c.github.io/html-aam/#el-area

@dd8
Copy link
Author

dd8 commented Apr 3, 2019

Yeah - I clarified the text to say there was a mapping, but no accessible name computation for AREA

@dd8 dd8 changed the title There's no mapping for the area element There's no name computation for the area element Apr 8, 2019
@scottaohara scottaohara self-assigned this May 17, 2019
@scottaohara
Copy link
Member

Sorry for the delay @dd8.

Picking this up and will clarify. But in the meantime I can tell you that what some screen readers are announcing is not necessarily just the accessible name, but rather a mish mashing of different data.

For instance, with Firefox MSAA and IA2 are exposing the area's alt as the accessible name, the URL as the accValue/Value, and MSAA exposes the image's alt as the accParent.

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 a pull request may close this issue.

3 participants