- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Dec 2013 16:44:57 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23976 Bug ID: 23976 Summary: Informing the Accessibility API (AAPI) Product: HTML WG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: blocker Priority: P3 Component: CR HTML Canvas 2D Context Assignee: jaymunro@microsoft.com Reporter: plh@w3.org QA Contact: public-html-bugzilla@w3.org CC: public-html-admin@w3.org This happens when drawCustomFocusRing returns true (ie the focus ring wasn't drawn by the user agent because the user didn't request a particular focus ring). In this case, the web app would need to draw the focus ring itself. How does the web app inform the user through the AAPI? [[ scrollPathIntoView can't be used to notify accessibility software of the focused object location as-is because it doesn't have an element to fire on, and it doesn't know if the scrolling is because of focus or not. ]] http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Oct/0002.html -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 3 December 2013 16:45:02 UTC