Bryan Garaventa

I believe it was to your last message. "I don't understand this comment. Where in the Accname spec is this written down? Div maps to role=generic in the accessibility tree...

It seems likely to me that any printable character will need to be added, regardless of the outliers where such content may sound a bit weird. This is already happening...

At present in 1.1, the fields with only placeholder would have no accessible name because placeholder isn't listed as a valid labeling mechanism, but those with a title attribute would...

We will also need to map the same thing to aria-placeholder.

Actually both inline and block level properties need to be taken into account, because it's also possible to take two block level elements and style them with inline properties to...

Sounds great, thanks! Is this different from the issue of inline versus block level elements adding or not adding whitespace between them when processed recursively?

Hi, The important thing to keep in mind is that the algorithm is recursive. So, after an element is referenced using aria-describedby, the referenced element goes through the same algorithm...

To clarify section 2.B, the full text is as follows. "B. Otherwise: ■ if computing a name, and the current node has an aria-labelledby attribute that contains at least one...

I agree this isn't as clear as it should be. I hope to address this when I work on the AccName simplification project. At present though, this is indicated at...

Hi, I'm not sure what the relevance of role=presentation/none is within this case or how this is supposed to change the naming computation. For example, here is the modified code...