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

No problem, I'll add one later today. I wasn't sure if this was a spec issue or an interpretation issue.

Tobias,
I don't understand what this means though: " This means that there can be more than one label for a labelable element. These labels should be processed in source order."

Are you referring to the DOM source order?

Do you mean that both of these would be treated differently and have different names?

<label>
This is
<input id="lbl" />
</label>
<label for="lbl">a test</label>

As opposed to:

<label for="lbl">a test</label>
<label>
This is
<input id="lbl" />
</label>

Because determining source order will be very expensive from a processing perspective and unreliable in practice because this could relate to anything such as use within data tables.

Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com

-----Original Message-----
From: Matt King [mailto:a11ythinker@gmail.com] 
Sent: Monday, February 12, 2018 8:13 AM
To: 'Tobias Bengfort' <tobias.bengfort@posteo.de>; 'John Foliot' <john.foliot@deque.com>; 'Schnabel, Stefan' <stefan.schnabel@sap.com>
Cc: Bryan Garaventa <bryan.garaventa@levelaccess.com>; jcraig@apple.com; 'Matthew King' <mck@fb.com>; 'ARIA Working Group' <public-aria@w3.org>; 'Aaron Leventhal' <aleventhal@google.com>; 'Alexander Surkov' <asurkov@mozilla.com>; 'Marco Zehe' <marco.zehe@gmail.com>; 'David Bolter' <david.bolter@gmail.com>; 'Dominic Mazzoni' <dmazzoni@google.com>; 'Joseph Scheuhammer' <clown@alum.mit.edu>; 'Michael Cooper' <cooper@w3.org>; 'Tess O'Connor' <hober@apple.com>; 'Joanmarie Diggs' <jdiggs@igalia.com>
Subject: RE: CSS in Accessibility Name Computation (Was: a11y-outline available for Firefox)

Tobias,

I agree with that interpretation. One part that is not clear to me is whether the HTML spec of the AccName spec determines how the multiple labels should be concatenated for the accessible label. Should there be spaces inserted by the browser?

I wonder if the AccName spec should have a Note about this that refers to the HTML spec.

Bryan, it would be better if this question were an issue in the AccName repo.

Matt

-----Original Message-----
From: Tobias Bengfort [mailto:tobias.bengfort@posteo.de] 
Sent: Monday, February 12, 2018 7:47 AM
To: John Foliot <john.foliot@deque.com>; Schnabel, Stefan <stefan.schnabel@sap.com>
Cc: Bryan Garaventa <bryan.garaventa@levelaccess.com>; jcraig@apple.com; Matthew King <mck@fb.com>; ARIA Working Group <public-aria@w3.org>; Aaron Leventhal <aleventhal@google.com>; Alexander Surkov <asurkov@mozilla.com>; Marco Zehe <marco.zehe@gmail.com>; David Bolter <david.bolter@gmail.com>; Dominic Mazzoni <dmazzoni@google.com>; Joseph Scheuhammer <clown@alum.mit.edu>; Michael Cooper <cooper@w3.org>; Tess O'Connor <hober@apple.com>; Joanmarie Diggs (jdiggs@igalia.com) <jdiggs@igalia.com>
Subject: Re: CSS in Accessibility Name Computation (Was: a11y-outline available for Firefox)

I am a bit confused because I did not get any response on my previous message. Myabe it was not properly delivered. So here it is again:

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


tobias

Received on Monday, 12 February 2018 17:57:51 UTC