Accessible Name Calculation - questions

Apologies for the cross-post. The following email references the
following HTML WG document,
which, in turn, references

In seeking to provide the best guidance to clients, as well as
increase the robustness of, I'd like to ask for clarification
on the accessible name calculation rules described in the above
Each question will be delineated with "----------"

Given the following:
<img src="foo.jpg" alt="" title="WHEE">

According to the accessible name calculation description, the
existence of a blank alt should cause title to be ignored. The alt
exists and its value is empty, indicating that there is no suitable
alternative. That doesn't seem to be the case in testing, which shows
the titles being announced by screen readers. Do the rules require
looking for printable characters when considering a "usable text

(I realize an empty alt with a title is generally a stupid idea but
I'm more interested in what *should* happen in this case when it comes
to accessible name calculation)

Section 8.11 of the HTML WG document says:

8.11 Text level elements not listed elsewhere

em, strong, small, s, cite, q, dfn, abbr, time, code, var, samp, kbd,
sub and sup, i, b, u, mark, ruby, rt, rp, bdi, bdo, br, wbr

If the element has an aria-label or an aria-labelledby attribute the
accessible name is to be calculated using the algorithm defined in
section 5.2.7. Accessible Name Calculation of the WAI-ARIA 1.0

Text level element accessible name calculation

Use aria-labelledby
Otherwise use aria-label
Otherwise use the title attribute
If none of the above yield a usable text string there is no accessible name

Why is the element's text node not considered in these cases?


The following roles are listed in the ARIA spec as getting their names
from "contents" or "author".

I'm not sure why "contents" would be used for these because they're
used for groupings of elements and do not have any contents outside of
that which exists in their child subnodes.

row - contents/ author
rowgroup - contents/ author


Should CSS-generated content be considered when determining a
"suitable text string"?


Given the following, what should the accessible names be for the
following inputs?

<label for="two">Whee
    <input type="text" name="one" id="one" value="one">

<input type="text" name="two" id="two" value="two">

The label element references input with ID of "two" but the label also
wraps the input with an ID of "one".  Does it label both inputs? Does
it label only one? If so, which one?

Thank you all for your hard work.

Karl Groves
Senior Technical Lead Accessibility Software Consultant & Director of Training
The Paciello Group
Phone: +1 443-875-7343

Received on Monday, 18 August 2014 20:03:14 UTC