Are there really no (normative) constraints on use and exposure of aria-atomic and aria-relevant ? from Joanmarie Diggs on 2017-09-12 (public-aria@w3.org from September 2017)

From: Joanmarie Diggs <jdiggs@igalia.com>
Date: Tue, 12 Sep 2017 16:43:26 -0400
To: ARIA Working Group <public-aria@w3.org>
Message-ID: <bd166568-d632-3207-eaa4-1eb433ea31eb@igalia.com>

Hey all.

According to the ARIA spec, aria-atomic and aria-relevant are each
supported on "all elements of the base markup." The ARIA spec does state
that aria-atomic and aria-relevant are associated with live regions.
However, I don't see any normative statement in the ARIA spec indicating
that authors should/must not use aria-atomic or aria-relevant if the
element is not a live region and not inside of a live region. I
similarly do not see a statement that user agents should/must not expose
these properties if an author does use them outside of a live region. Is
this by design?

The above, combined with the mappings in the Core AAM for aria-relevant
and aria-atomic, seem to suggest that if these properties are present,
they should be exposed to ATs even if the properties are used outside of
a live region. Is that desired?

--joanie (who hopes she's just missing something obvious)

Received on Tuesday, 12 September 2017 20:44:03 UTC