Open scottaohara opened 1 year ago
Or there is a reason why the visible label can become the description and why this is only true for a few elements - and this reason is explained
From the wg call today, we see three options to go forward here:
I like 2, unless there are a sufficient number of sites that rely on this mechanism (but I don't know of any) - then I would prefer 3
The accessible description computation section indicates that a table's caption, a summary element's subtree, or the value attribute of an input type=submit|button|reset can all be used as an accessible description if the elements in question have an overriding accName (e.g., aria-label).
While out of scope for resolving https://github.com/w3c/accname/pull/69 and the companion HTML AAM PRs, I have been wondering why these elements are treated as special cases where other similar elements are not?
for instance, why doesn't button element's subtree become also become its accessible description if a stronger naming mechanism is used? Similarly, a table's caption becomes the accDescription if a table has an aria-label... but a fieldset's legend doesn't presently become the description if the fieldset has been given an aria-label.
It seems to me that either we need to expand this behavior to other similar elements, or these special cases shouldn't be there?
If expanding to other elements, then the following would need to be considered for addition to the special cases:
a
elementbutton
elementfieldset
>legend
label
elementoption
element with alabel
attribute or child text