E-mail List Archives
Re: 4.1.1 Parsing > nested elements
From: Glen Walker
Date: Apr 6, 2018 10:36AM
- Next message: Glen Walker: "Re: Trapping focus in an alert"
- Previous message: Glen Walker: "Re: Working around flaky browser accessibility tree"
- Next message in Thread: None
- Previous message in Thread: Fernand van Olphen: "Re: 4.1.1 Parsing > nested elements"
- View all messages in this Thread
Excellent question. I've never looked for a list. Because of the number of combinations you could potentially create in writing bad html, it might not be possible to enumerate every possible combination that might affect accessibility. For example, having a <ul> that has an immediate child that is *not* a <li> (such as a <span>). It may or may not affect the screen reader, depending on whether the author intended the <span> to be read as an item.
Sent from my iPad
> On Apr 6, 2018, at 3:21 AM, Fernand van Olphen < <EMAIL REMOVED> > wrote:
>
> Steve, Glen : thanks for your advice!
>
> You both say that not every nesting error is a blocker (like div inside span), but only a subset is (like button in a)
>
> I am curious to know: is there a list of this subset of nesting errors which DO effect accessibility, or if that list is smaller: which DO NOT effect accessibility?
> And if not: maybe a good topic for a tweet/article/ etc...to compile such a list?
>
> Regards,
> Fernand
> De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op: http://www.denhaag.nl/disclaimer
> > > >
- Next message: Glen Walker: "Re: Trapping focus in an alert"
- Previous message: Glen Walker: "Re: Working around flaky browser accessibility tree"
- Next message in Thread: None
- Previous message in Thread: Fernand van Olphen: "Re: 4.1.1 Parsing > nested elements"
- View all messages in this Thread