23978 2013-12-03 16:46:55 +0000 Informing the user shouldn't be optional 2014-01-20 23:24:39 +0000 1 1 1 Unclassified HTML WG CR HTML Canvas 2D Context unspecified PC Windows NT CLOSED FIXED a11y, a11y_canvas P3 blocker --- 1 plh jaymunro cabanier jmann lwatson mark.sadecki+w3c mike public-html-admin public-html-wg-issue-tracking schwer public-html-bugzilla oldest_to_newest 97058 0 plh 2013-12-03 16:46:55 +0000 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. 97085 1 jaymunro 2013-12-03 21:33:58 +0000 Reassigning to Canvas 2D Context Level 2 since drawSystemFocusRing and drawCustomFocusRing are at risk for CR. 97115 2 schwer 2013-12-04 14:32:13 +0000 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? 97137 3 plh 2013-12-04 17:46:52 +0000 Rik would be better at answering this one. Adding him in the loop. 97158 4 jaymunro 2013-12-04 19:52:04 +0000 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. 97717 5 schwer 2013-12-16 23:21:21 +0000 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." 97860 6 schwer 2013-12-23 18:30:02 +0000 Revised text to address this can be found in this post: http://lists.w3.org/Archives/Public/public-canvas-api/2013OctDec/0047.html 98464 7 jaymunro 2014-01-14 22:58:44 +0000 Removed 'optionally' from description of informing the user. 98792 8 jmann 2014-01-20 23:24:39 +0000 The Canvas Subgroup agrees this issue has been fixed in the spec.