W3C home > Mailing lists > Public > public-aria@w3.org > August 2017

Re: ARIA and HTML document question about implicit headings

From: Aaron Leventhal <aleventhal@google.com>
Date: Mon, 14 Aug 2017 19:15:32 +0000
Message-ID: <CA+1LECQr9K1MOrVGRAqcqfu0gkrEV6CEeUFzoeV4Qy=LgxtRuA@mail.gmail.com>
To: Bryan Garaventa <bryan.garaventa@levelaccess.com>, ARIA Working Group <public-aria@w3.org>
Implementations don't try to do that much verification of markup validity
-- that's mostly left to authoring tools.

Aaron

On Mon, Aug 14, 2017 at 2:25 PM Bryan Garaventa <
bryan.garaventa@levelaccess.com> wrote:

> I thought this only affected the mappings. For example a heading can have
> only one level in the accessibility tree, so only one would be announced
> regardless.
>
>
>
> I just verified this using the following markup.
>
>
>
> <h1 aria-level="3"> Test </h1>
>
>
>
> All of the screen readers JAWS, NVDA, and iOS VoiceOver announce this as
> an H3 heading in Firefox, Chrome, and Safari.
>
>
>
> Bryan Garaventa
>
> Accessibility Fellow
>
> Level Access, Inc.
>
> Bryan.Garaventa@LevelAccess.com
>
> 415.624.2709 <(415)%20624-2709> (o)
>
> www.LevelAccess.com
>
>
>
> *From:* Aaron Leventhal [mailto:aleventhal@google.com]
> *Sent:* Monday, August 14, 2017 11:05 AM
> *To:* Bryan Garaventa <bryan.garaventa@levelaccess.com>; ARIA Working
> Group <public-aria@w3.org>
> *Subject:* Re: ARIA and HTML document question about implicit headings
>
>
>
> Hi Bryan, I think can answer this one.
>
>
>
> The <h1> etc. elements already have a level, so aria-level would be a
> direct conflict. Why say the level twice?
>
>
>
> However, a button (native or ARIA) has no way to say whether it's pressed,
> or pressable, or has a popup, without the aria-pressed/aria-haspopup
> attributes.
>
>
>
> Aaron
>
>
>
> On Mon, Aug 14, 2017 at 12:49 PM Bryan Garaventa <
> bryan.garaventa@levelaccess.com> wrote:
>
> Hi,
> I noticed recently that according to the ARIA and HTML mapping tables, the
> use of aria-level is said to not be allowed on H1 through H6 elements, even
> though these implicitly map to role="heading".
>
> Since supporting attributes like aria-pressed and aria-haspopup are
> accepted on other implicit elements like role="button", amongst other
> implicit role and attribute combinations, why is this one different?
>
> Bryan Garaventa
> Accessibility Fellow
> Level Access, Inc.
> Bryan.Garaventa@LevelAccess.com
> 415.624.2709 <(415)%20624-2709> (o)
> www.LevelAccess.com
>
>
Received on Monday, 14 August 2017 19:16:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 14 August 2017 19:16:09 UTC