This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The specification makes it optional for the user agent to "inform the user" that the focus is at the location given by the intended path. Why is that not always the case? However, this should happen even if the element is not focused. This way, the focus ring can establish a "region" with ARIA rules.
Reassigning to Canvas 2D Context Level 2 since drawSystemFocusRing and drawCustomFocusRing are at risk for CR.
Ian wanted it put in this way as some user agents do not support accessibility. I did not like that but I could not argue his point. Microsoft supported this text when it was first submitted. An ARIA "region" is a perceivable area of the screen and it does not have to do with focus. Did you mean something else?
Rik would be better at answering this one. Adding him in the loop.
I jumped the gun on moving to L2, there are still ongoing discussions on the focus ring methods. Moving back to CR until discussions are complete.
remove the word optional and amend the note regarding notifying the user to include this text: "This is intended to provide inform the user of the location of the element on canvas to support accessibility services."
Revised text to address this can be found in this post: http://lists.w3.org/Archives/Public/public-canvas-api/2013OctDec/0047.html
Removed 'optionally' from description of informing the user.
The Canvas Subgroup agrees this issue has been fixed in the spec.