You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Otherwise use alt attribute. 3. Otherwise use title attribute.
Is the "otherwise" in point 3 similar to 5.1.1 where we have
If the accessible name is still empty, then: use the control's title attribute.
?
Right now I can see no consistent language regarding these steps. It seems to me that every step only applies if the previous steps did not produce a name. But sometimes we have this explicitly mentioned and sometimes not.
the accessible name is a localized string of the word "Submit Query".
This is followed by "If none of the above yield a usable text string there is no accessible name.". So this localization could produce an empty string? Wouldn't it be better to produce an accessible name in a foreign language rather than no name at all?
Is the "otherwise" in point 3 similar to 5.1.1 where we have
?
Right now I can see no consistent language regarding these steps. It seems to me that every step only applies if the previous steps did not produce a name. But sometimes we have this explicitly mentioned and sometimes not.
This is followed by "If none of the above yield a usable text string there is no accessible name.". So this localization could produce an empty string? Wouldn't it be better to produce an accessible name in a foreign language rather than no name at all?
By spec this element cannot be labelled via
<label>
.However, a web-platform-test currently test this (https://github.com/web-platform-tests/wpt/blob/677c57c0e8816b0892cc3ae1c2772189b1bdcf65/accname/name_test_case_616-manual.html#L64-L65). Chrome 84 also allows labelling
<input type="image" />
. Should this test be removed or the spec updated to match implementations?The text was updated successfully, but these errors were encountered: