22993 2013-08-17 03:40:08 +0000 Expose target and formtarget attributes to ATs 2013-08-21 08:25:38 +0000 1 1 1 Unclassified HTML WG HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) unspecified All All NEW a11y P2 normal --- 1 taken.spc faulkner.steve lwatson mike public-html-admin public-html-bugzilla public-html-wg-issue-tracking surkov.alexander sideshowbarker+html-a11y-api oldest_to_newest 92217 0 taken.spc 2013-08-17 03:40:08 +0000 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 92341 1 surkov.alexander 2013-08-20 15:37:41 +0000 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?