Assistive Technologies and the aamtest test harness need to expect a certain amount of structure surrounding web content -- and that is currently not specified, and there are differences between the browsers.
For example:
- What is the root of the web content, what role does it have?
- How does an assistive technology get to the web content / find the active tab?
See discussion in:
In ATSPI there are differences between Firefox and Chrome, for example the attribute name for the URL of the document, and what role the root node has. Additionally, all the browser use the embed relationship to help assistive technologies find web content, and this isn't specified anywhere.
Not sure if I should put this issue here or in https://github.com/web-platform-tests/interop-accessibility, but because it would require additional spec text, I thought I'd start here.
Assistive Technologies and the
aamtesttest harness need to expect a certain amount of structure surrounding web content -- and that is currently not specified, and there are differences between the browsers.For example:
See discussion in:
In ATSPI there are differences between Firefox and Chrome, for example the attribute name for the URL of the document, and what role the root node has. Additionally, all the browser use the
embedrelationship to help assistive technologies find web content, and this isn't specified anywhere.Not sure if I should put this issue here or in https://github.com/web-platform-tests/interop-accessibility, but because it would require additional spec text, I thought I'd start here.