RE: Issues with the naming computation and parsing nested element structures including CSS pseudo elements

This does in part, but only partially.

Where it states:

"• For :before pseudo elements,  User agents MUST prepend CSS textual content, without a space, to the textual content of the current node. 
• For :after pseudo elements,  User agents MUST append CSS textual content, without a space, to the textual content of the current node."

That's clear enough, which all of the browsers are not doing.

And this comment:

"Editor's note (Joseph) the last step above needs work since there are cases where you "append with a space" and others where you "append without a space".  Example of the latter: <label> <input type="checkbox"> Make this the <em>top</em>most element</label>.  The result is "Make this the topmost element", not "Make this the top most element" – do not append a space after "top"."

This is only partially correct, because it does not address the differences between inline versus block level elements.

E.G

<label> <input type="checkbox"> Make this the <div>top</div>most element</label>

Which would need to result in "Make this the top most element"

Otherwise all nested structures within controls that are separated by block level elements like list items, tables, divs, and so on will all be concatenated without any spaces even though visually they are separated.


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

-----Original Message-----
From: Tobias Bengfort [mailto:tobias.bengfort@posteo.de] 
Sent: Wednesday, January 31, 2018 10:49 PM
To: Bryan Garaventa <bryan.garaventa@levelaccess.com>; Aaron Leventhal <aleventhal@google.com>
Cc: Alexander Surkov <asurkov@mozilla.com>; Marco Zehe <marco.zehe@gmail.com>; david bolter <david.bolter@gmail.com>; James Craig <jcraig@apple.com>; Dominic Mazzoni <dmazzoni@google.com>; Matthew King <mck@fb.com>; ARIA Working Group <public-aria@w3.org>
Subject: Re: Issues with the naming computation and parsing nested element structures including CSS pseudo elements

On 01/02/18 02:17, Bryan Garaventa wrote:
> This also appears to contradict the spec where it states at the end of 
> the naming computation algorithm the following:
> 
> "Append the result of each step above, with a space, to the total 
> accumulated text." http://www.w3.org/TR/accname-aam-1.1/

> 
> Which steps is this referring to if not the parsing algorithm?

I think this issue is already mentioned in the editor's note on https://w3c.github.io/accname/#step2F.iii


tobias

Received on Thursday, 1 February 2018 18:02:53 UTC