WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 4.1.1 Parsing > nested elements

for

From: glen walker
Date: Mar 30, 2018 6:41PM

Going off topic a bit, for an html reference, I prefer the other w3c
document that has Steve's name on it:

https://www.w3.org/TR/html53/

because it's easy to search the left navigation panel. Whatever html
element I'm looking for, I can type the element tag name (without the
brackets), followed by the letter "e" for "elements". So for the <ul>
element, I'd search the page for "ul e". For the <main> element, I'd
search for "main e". (Or you can actually type "element" instead of "e"
but I'm a lazy typer.) This works great when the element name is a common
word, like "table" or "main" or "form", or if the element name is a single
letter or common letter combination found it lots of other words, such as
<a> or <p> or <q> (search for "a e" or "p e" or "q e").

So for the <ul> element, it found the page,
https://www.w3.org/TR/html53/grouping-content.html#the-li-element, which
shows the allowed roles for the <ul> element. Steve had referenced
https://www.w3.org/TR/html-aria/#ul. I just wanted to give another option.


On Fri, Mar 30, 2018 at 3:05 PM, Steve Faulkner < <EMAIL REMOVED> >
wrote:

> Hi Jon,
> Use of role=navigation on <ul> is a conformance error
> https://www.w3.org/TR/html-aria/#ul
>
> So if you do check your code it will throw an error, for example
> https://validator.w3.org/nu/?doc=https%3A%2F%2Fs.codepen.
> io%2Fstevef%2Fdebug%2FjzYgdJ
>
>
>
> --
>
> Regards
>
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
>