Re: CSS in Accessibility Name Computation (Was: a11y-outline available for Firefox)

Thanks Bryan for all the work! I have just one quick remark:

On 09/02/18 01:54, Bryan Garaventa wrote:
> 3. Logic for handling nested label elements has been added, in which
> an implicit label element surrounds a form field that also includes
> an explicit form field reference somewhere else. There appears to be
> no standard in the naming computation to address this, so I set this
> to compute the explicit label and ignore the implicit one in such
> cases. This seems logical to me, but if everybody wants this to be
> handled differently it can be changed.

I think the standard is actually clear about this: All labels should be
included in the name. A labelable element is associated with a label
element if:

- the label element has a `for` attribute that matches the control's `id`
- the label element does not have a `for` attribute and the labelable
element is the first labelable descendant of that label.

This means that there can be more than one label for a labelable
element. These labels should be processed in source order.

Source: https://www.w3.org/TR/html52/sec-forms.html#the-label-element

thanks
tobias

Received on Friday, 9 February 2018 06:52:06 UTC