There appears to be a contradiction in the handling of generic when dealing with a parent/child relationship:
https://w3c.github.io/aria/#scope
To determine whether an element has a parent with the required role, user agents MUST ignore any elements with the role generic or none.
https://w3c.github.io/aria/#generic
However, unlike elements with role presentation, generic elements are exposed in accessibility APIs
How would a user agent ignore the generic elements while also being required to expose them? Is the intent that an AT would ignore those generic elements, but a browser would not ignore them when generating the AOM?
There appears to be a contradiction in the handling of
genericwhen dealing with a parent/child relationship:https://w3c.github.io/aria/#scope
https://w3c.github.io/aria/#generic
How would a user agent ignore the
genericelements while also being required to expose them? Is the intent that an AT would ignore those generic elements, but a browser would not ignore them when generating the AOM?