This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23976 - Informing the Accessibility API (AAPI)
Summary: Informing the Accessibility API (AAPI)
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: CR HTML Canvas 2D Context (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P3 blocker
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11y_canvas
Depends on:
Blocks:
 
Reported: 2013-12-03 16:44 UTC by Philippe Le Hegaret
Modified: 2015-06-16 20:43 UTC (History)
5 users (show)

See Also:

Attachments

Description Philippe Le Hegaret 2013-12-03 16:44:57 UTC 
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
Comment 1 Jay Munro 2013-12-03 21:34:28 UTC 
Reassigning to Canvas 2D Context Level 2 since drawSystemFocusRing and drawCustomFocusRing are at risk for CR.
Comment 2 Philippe Le Hegaret 2015-06-16 20:29:43 UTC 
Moved to L1
Comment 3 Philippe Le Hegaret 2015-06-16 20:43:36 UTC 
drawCustomFocusRing is no longer. closing.