WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Relationship between WCAG and the ARIA in HTML specification

for

From: Steve Green
Date: Aug 7, 2023 5:11PM

Have they really defined how every type of invalid markup must be handled? Where can I find this? I searched the HTML5 specification but couldn't find anything relevant. Words like "parsing", "invalid" and "error" occur many hundreds of times, so searching was not effective.

Steve

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Patrick H. Lauke
Sent: Monday, August 7, 2023 8:49 PM
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] Relationship between WCAG and the ARIA in HTML specification

On 07/08/2023 20:42, Birkir R. Gunnarsson wrote:
> I also wonder, if we keep going down this path, whether we still need
> to report labels that are not connected to inputs under 4.1.2 or
> 1.3.1, if one or two screen reader browser combinations guess them
> right.

They may guess them right, but this one can be checked very easily in the underlying API: does the browser expose an accessible name for the input, yes or no? If no (but then the specific AT manages to guess it), it's still a failure of 4.1.2. That one is quite unambiguous, because you can't guarantee that all ATs will have the same heuristics.

In the case of misnested/invalid markup, you can guarantee that browsers all error-correct that markup the same way, since that has been defined explicitly in the HTML (5/living standard) spec, so not up to heuristics in browsers anymore, as used to be the case.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux https://mastodon.social/@patrick_h_lauke | skype: patrick_h_lauke