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

RE: ARIA and HTML document question about implicit headings

From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Date: Tue, 15 Aug 2017 23:20:02 +0000
To: Rich Schwerdtfeger <richschwer@gmail.com>
CC: ARIA Working Group <public-aria@w3.org>
Message-ID: <BN6PR03MB278547A07B011FF42E390F04F28D0@BN6PR03MB2785.namprd03.prod.outlook.com>
I'll be happy to submit something for 1.2. Before I do though, this is the logic that makes sense to me.

Since there are implicit ARIA roles applied to certain native markup, making it possible to represent the same role in the accessibility tree regardless if a native element is used or its equivalent role on a differing element type, it makes sense that applying supported ARIA attributes to either of these constructs would result in a subsequent update to the accessibility tree accordingly.

E.G

<img aria-label="Test" > Would result in an image with an accessible name of "Test".

<h2 aria-level="3"> Test </h2> would result in a heading role with a level of 3.

<button aria-pressed="true"> Test </button> would result in a pressed toggle button.

And so on with supporting atributes for these role types.

I'm not talking about substituting ARIA attributes for native host semantics like the use of aria-checked instead of checked on a native checkbox or radio button (input+type=checkbox|radio), but rather the updating of native accessibility tree roles with supporting ARIA attributes when there is no equivalent native host semantic available.

This would be helpful in many cases, and already occurs for many roles in browsers already.

Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com

-----Original Message-----
From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] 
Sent: Monday, August 14, 2017 6:46 PM
To: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Cc: ARIA Working Group <public-aria@w3.org>
Subject: Re: ARIA and HTML document question about implicit headings

This was identified as an issue for ARIA 1.1 in part because we started to move toward role parity with HTML 5. The others issues you now raise were not. 

If you would like to other things addressed you should put them in ARIA 1.2 issues on github.

Rich

Sent from my iPhone

> On 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 (o)
> www.LevelAccess.com
> 
> 
Received on Tuesday, 15 August 2017 23:20:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 15 August 2017 23:20:29 UTC