Open Bug 1737946 Opened 4 years ago Updated 1 month ago

GroupPosition broken for radio buttons in shadow DOM

Categories

(Core :: Disability Access APIs, defect, P3)

defect

Tracking

()

People

(Reporter: Jamie, Unassigned)

References

(Blocks 1 open bug)

Details

STR:

  1. Open this test case:
    data:text/html,<input name="foo" type="radio"><div role="presentation" id="shadow"><script>shadow.attachShadow({ mode: "open" }).innerHTML = '<input type="radio" name="foo">';</script>
  2. Use the Firefox Accessibility Inspector to check the attributes for the first radio button.
    • Observe: There are posinset and setsize attributes with a value of "1".
  3. Use the Firefox Accessibility Inspector to check the attributes for the second radio button.
    • Expected: There are posinset and setsize attributes with a value of "1".
    • Actual: There are no posinset and setsize attributes.

I originally wrote this use case to test how we handle two radio inputs with the same name, but where one is in a shadow DOM. I expected we might count them both in the same group. To my surprise, it turns out we just fail altogether for shadow radio inputs!

Severity: -- → S4
Priority: -- → P3

(In reply to James Teh [:Jamie] from comment #0)

To my surprise, it turns out we just fail altogether for shadow radio inputs!

It seems that at some point, this got fixed. But...

I expected we might count them both in the same group.

Now we have this bug.

See Also: → 2066630

So we count them in the same group for RemoteAccessible, but as separate groups for LocalAccessible. As I understand it, LocalAccessible is actually correct, because each shadow DOM has an isolated scope for names. That seems to match how DOM handles focus: you can't arrow key between the two radio buttons, for example.

You need to log in before you can comment on or make changes to this bug.