This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Some WCAG 2.0 Success Criterions require/recommend warning when opening new window. As target and formtarget attributes are machine readable information, these should be exposed to ATs through Accessible APIs. I believe that HTML to Platform Accessibility APIs Implementation Guide spec should define how to expose target and formtarget attributes to ATs. Once they are exposed, ATs can warn users when new window will be opened even web pages don't indicate that in link text. Related WCAG Techs: H83: Using the target attribute to open a new window on user request and indicating this in link text http://www.w3.org/TR/WCAG-TECHS/H83.html G200: Opening new windows and tabs from a link only when necessary http://www.w3.org/TR/WCAG-TECHS/G200.html G201: Giving users advanced warning when opening a new window http://www.w3.org/TR/WCAG-TECHS/G201.html Related HTML Specs: http://www.w3.org/TR/html5/links.html#attr-hyperlink-target http://www.w3.org/TR/html5/forms.html#attr-fs-target
What is the purpose for the user to know where the link will be open? Why AT users would need to have an access to this information while sighted users don't need it? Or if sighted users need it then wouldn't we need browser's UI rather than AT API mapping?