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 8, 2023 4:39AM

I will assume that's a comprehensive list of error conditions - it's certainly a long list. However, it doesn't say anything about the accessibility tree. Is there a specification for how it is constructed? If there is, I can't find it.

Is it possible that different browsers could generate different accessibility trees from the same DOM if the HTML is well formed, but contains invalid nesting? Or does the accessibility tree not take account of an element's nesting?

Steve


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



On 08/08/2023 09:15, Patrick H. Lauke wrote:
> https://html.spec.whatwg.org/#parse-errors

Oops, fat finger...meant to point to the overall section https://html.spec.whatwg.org/#parsing

(this is the part that was never defined in the original HTML spec, which caused browser engines to just implement their own secret sauce heuristics when they encountered misnested markup like <b><i>foo</b></i>
- the latter being what 4.1.1 means when it talks about "nested according to the specification")

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