This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov Element level Focus APIs In this section, people are instructed to use CSS to hide the focus ring if they "find it unsightly". There should be additional information letting them know that doing so can jeopardize accessibility for some people including those who can see the screen, but who also rely upon keyboard accessibility. [split out from bug 13590]
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: no spec change Rationale: This seems to have been fixed already.
Moved to HTML A11y TF component.
As Hixie mentioned, already fixed in HTML5: [[[ Do not use this method to hide the focus ring if you find the focus ring unsightly. Instead, use a CSS rule to override the outline property, and provide a different way to show what element is focused. Be aware that if an alternative focusing style isn’t made available, the page will be significantly less usable for people who primarily navigate pages using a keyboard, or those with reduced vision who use focus outlines to help them navigate the page. ]]]