WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: heading as child of another heading - valid?


From: Birkir R. Gunnarsson
Date: Mar 31, 2018 11:20AM

One more observation on this topic,.
Accessibility tester plug-ins for browsers tend not to identify most
nesting issues, because the browser tries to correct them while
building the DOM>
I did extensive testing with aXe about a year ago and it missed most
nesting issues. Granted I should repeat those checks but it is
understandable that a product that tests the DOM (which is usually the
right place to test accessibility) misses markup issues that the
browser will try to correct while parsing.
These can still be issues because there are no hard and fast rules for
how browsers should handle invalid code.
I wouldn't spend too much energy on this compared to other
accessibility issues, but make sure not to overlook this entirely and
try to run suspicious looking HTML through a checker.

On 3/30/18, Steve Faulkner < <EMAIL REMOVED> > wrote:
> Hi Diane, this may be helpful in understanding the w3c markup checker
> HTML5 – Check it Before you Wreck it with Mike[tm] Smith
> <http://html5doctor.com/html5-check-it-before-you-wreck-it-with-miketm-smith/>;
> --
> Regards
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
> On 30 March 2018 at 20:46, Tomlins Diane < <EMAIL REMOVED> >
> wrote:
>> Thanks Steve, that helps to understand what the validator is doing there.
>> I should have thought of just putting in a simple example to check...
>> D'oh!
>> >> It is a conformance error as per the HTML spec, headings cannot be
>> nested.
>> If you test a simple case the error is shown. In the case of your example
>> code there is an error in the patent elements that suppresses validation
>> of
>> child elements, which is probably why it does not get flagged.
>> >> SteveF
>> Diane R Tomlins
>> HCA IT&S | Digital Media
>> Accessibility SME
>> >> >> >> >>
> > > > >

Work hard. Have fun. Make history.