In one paragraph
Active area elements must have alternative text means a tested image-map link lacked an accepted accessible name. Name each linked region for the destination or action it provides; a description of the overall image does not name every separate link. Verify keyboard access and responsive coordinates as well as labels. Consider ordinary visible links when the map is unnecessarily complex or unreliable.
Why it matters
An image map divides one image into independently linked regions. The whole picture and the destinations perform different jobs. A map's general alternative can explain what it represents, while each active area needs to identify its own choice.
A region named Link or Area supplies little useful meaning even when a presence test accepts it. Users should be able to distinguish floors, departments, locations, or other actual destinations without guessing coordinates from the visual picture.
The map also needs usable keyboard focus and layout behaviour. Naming an area does not prove its active coordinates still correspond to the visual region after scaling or that a small hotspot is practical to use.
How WebAuditOS evaluates this finding
The supplied area-alt rule examines area elements with href inside maps and recognises naming paths including alt, supported ARIA references or labels, and title fallback. The source states that hidden or abandoned maps can remain within this rule's inspection.
Critical impact maps to high severity. It does not assess the label's meaning, the associated image alternative, server-side image maps, or full input usability. Native alt is the straightforward attribute for an active HTML area even when another accepted fallback avoids a finding.
How to fix it
- Find the active map and the image using it. Check usemap references and unique map names so the intended image actually points to the intended regions.
- Assign a useful destination name to every active region. A small illustrative fragment is:
<img src="/floor-plan.png" usemap="#floor-plan" alt="Building floor plan with department links">
<map name="floor-plan">
<area shape="rect" coords="0,0,100,100" href="/departments/reception" alt="Reception department">
</map>Replace the asset, coordinates, and destination with real matching content. This fragment does not prove responsive geometry or full accessibility.
- Keep the image's own alternative appropriate to the whole context. Do not assume a long image description compensates for unnamed region links or duplicate the entire map unnecessarily in each name.
- Remove unused areas or maps that are no longer part of the interface. If a region is not intended to link, model that explicitly rather than retaining an empty-named active destination.
- Provide an ordinary usable list of destinations when that helps equivalent access. A complex diagram may also need explanatory text beyond link names. Keep that alternative maintained alongside the map.
- Test Tab navigation, focus visibility, activation, and expected destinations. Review touch targets and behaviour at relevant zoom and image sizes. Coordinate-based geometry can need additional implementation work.
- If the diagram needs rich interactive exploration, choose a complete appropriate accessible design rather than adding ARIA roles indiscriminately. A map naming repair does not implement a custom widget.
- Rescan and manually verify the link choices. Check stale templates and hidden maps too, accounting for the supplied rule's applicability and rendered-page coverage.
What the fix can break
Changing the image size or crop can disconnect active coordinates from their visible locations. A correct accessible name does not fix an incorrect hotspot.
Removing an active area can remove a real navigation route. Preserve access through another deliberate link if the destination remains useful.
Do not fill every missing alt with an empty string. An active link needs a meaningful name even when a decorative image elsewhere legitimately has an empty alternative.
Questions
Does the overall image alt name each region?
No. The image and its independent links need their respective purposes communicated.
Can an active area use empty alt as decoration?
Do not leave active navigation unnamed. Remove a nonfunctional region or supply an appropriate link name.
Why might a hidden old map still appear?
The supplied rule does not apply the same hidden-element filtering as every other check. Inspect and remove genuinely abandoned markup.
Which related checks help?
Review image alternatives, server-side image maps, and the automation limits guide.
What severity does this get in the report?
High. An axe finding takes its severity from the impact axe reports for the element that failed, and the report maps critical and serious to high, moderate to medium, minor to low. axe declares area-alt critical, so a failure arrives as high. The panel above shows a conformance level instead of a severity because for axe rules that value comes from the scan, not from the rule.