Why are conflicts between native markup semantics and WAI-ARIA so complicated? from Tobias Bengfort on 2018-05-01 (w3c-wai-ig@w3.org from April to June 2018)

From: Tobias Bengfort <tobias.bengfort@posteo.de>
Date: Tue, 1 May 2018 09:41:43 +0200
To: WAI IG <w3c-wai-ig@w3.org>
Message-ID: <2f6f7aba-cc29-043f-7c81-c1e41223e771@posteo.de>

I always assumed that WAI-ARIA will always override native semantics.
But now I found <https://www.w3.org/TR/core-aam-1.1/#mapping_conflicts>.

Some examples:

- `<div role="button"></div>` has role "button" (ARIA wins)
- `<div aria-label="foo">bar</div>` has label "foo" (ARIA wins)
- `<div aria-hidden="false" hidden></div>` is hidden (native wins)

This seems overly complicated to me. What were the reasons this was decided?

tobias

Received on Tuesday, 1 May 2018 07:42:12 UTC