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
My reading of the accname spec is that the following should happen for the button:
It should hit 2.B.ii and follow the idRef inputId
Start from step 2 with the input as the current node
The input should use step 2E to calculate its text alternative, and return the text of the <label>
The button's accName should be "Something"
This is not the case for Firefox, Chrome, Edge, or Safari in my testing. All of them return the value of the input as its text alternative when within an aria-labelledby traversal instead of the name derived from the <label>. My guess is that browsers are following step 2C here, even though the input is directly referenced, and not within a parent label.
I'd like to confirm whether the correct behavior is for the button to have the accName "Something" here, or whether the current browser behavior is correct.
The text was updated successfully, but these errors were encountered:
I think you are right: according to Accname, in your example the button label should be "Something". However, what the browsers do feels more correct - i.e. maybe the accname should be adjusted here rather than changing the behavior of the browsers.
Problem in the AccName is also that the example 3 is wrong:
a checkbox must not contain a textbox (because of Children Presentational: True).
Using the accName for the button in the following markup as a reduced example:
My reading of the accname spec is that the following should happen for the button:
inputId
<label>
This is not the case for Firefox, Chrome, Edge, or Safari in my testing. All of them return the value of the input as its text alternative when within an
aria-labelledby
traversal instead of the name derived from the<label>
. My guess is that browsers are following step 2C here, even though the input is directly referenced, and not within a parent label.I'd like to confirm whether the correct behavior is for the button to have the accName "Something" here, or whether the current browser behavior is correct.
The text was updated successfully, but these errors were encountered: