What happens when ARIA conflicts with HTML?
I was trying to make sense of these issues, reported in 2020 against ARIA in HTML : Incorrect or confusing description of aria-required usage #225 Other aria-* attributes which should not be allowed on HTML elements #241 My understanding of strong native semantics was hand-wavy, so I scrutinized the ARIA spec . It gives us an interlocking set of requirements for web authors, ARIA conformance checkers, user agents, and the host language itself (usually HTML, but could be SVG or MathML). To help myself understand the subtleties, I reorganized and rephrased these requirements in more formal language. Words in [square brackets] are my additions, but otherwise these are direct quotes from ARIA spec 1.2 (Working Draft 18 December 2019), section 8.5, Conflicts with Host Language Semantics . How ARIA handles conflicts with a host language The ARIA spec's requirements for a host language spec (e.g, ARIA in HTML) [8.5.1 Attribute Conflicts:] Host languages MUST explicitly declare where the...