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

RE: ARIA and HTML document question about implicit headings

From: Schnabel, Stefan <stefan.schnabel@sap.com>
Date: Tue, 15 Aug 2017 07:42:58 +0000
To: Aaron Leventhal <aleventhal@google.com>, Bryan Garaventa <bryan.garaventa@levelaccess.com>, ARIA Working Group <public-aria@w3.org>
Message-ID: <83adeb1a58b441c58a67b47d35a83260@sap.com>
So we have to live with the situation that validators will potentially flame
<h1 aria-level="3"> Test </h1>
but in reality it works since AT/UA is resolving it in the sense “ARIA wins”.

<button role=”textbox” ..>

goes in the same ambiguous direction.

Although this is hypothetical and code above can be seen always as “authoring error” by authoring tools - how will this be resolved in the future?
Is it safe to rely on the AT override behaviour in the long run? I don’t think so.


-          Stefan

From: Aaron Leventhal [mailto:aleventhal@google.com]
Sent: Montag, 14. August 2017 21:16
To: Bryan Garaventa <bryan.garaventa@levelaccess.com>; ARIA Working Group <public-aria@w3.org>
Subject: Re: ARIA and HTML document question about implicit headings

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<mailto: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<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709<tel:(415)%20624-2709> (o)
www.LevelAccess.com<http://www.LevelAccess.com>

From: Aaron Leventhal [mailto:aleventhal@google.com<mailto:aleventhal@google.com>]
Sent: Monday, August 14, 2017 11:05 AM
To: Bryan Garaventa <bryan.garaventa@levelaccess.com<mailto:bryan.garaventa@levelaccess.com>>; ARIA Working Group <public-aria@w3.org<mailto: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<mailto: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<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709<tel:(415)%20624-2709> (o)
www.LevelAccess.com<http://www.LevelAccess.com>
Received on Tuesday, 15 August 2017 07:43:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 15 August 2017 07:43:23 UTC