This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 16826 as part of operation convergence. Originally filed: 2012-04-23 12:42:00 +0000 Original reporter: Matthew Turvey <mcturvey@gmail.com> ================================================================================ #0 Matthew Turvey 2012-04-23 12:42:58 +0000 -------------------------------------------------------------------------------- http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html#element-level-focus-apis The current text advises: "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. (Be aware, however, that this makes the page significantly less usable for some people, especially those with reduced vision who use focus outlines to help them navigate the page.)" The advice could be improved by emphasising that removing the focus outline affects all keyboard-navigation users, and the negative effects can be mitigated by using another CSS technique to display where the focus is, something like: "(Be aware, however, that, removing the focus outline makes the page significantly less usable to people who use a keyboard to navigate the page. If you do remove the focus outline, provide an alternative method of indicating focus with CSS :focus, such as adding an underline on text links or a border on linked images.)" ================================================================================
Not sure about that exact wording, but yeah, I could make that more elaborate.
Checked in as WHATWG revision r7575. Check-in comment: Improve accessibility chops of this non-normative suggestion. http://html5.org/tools/web-apps-tracker?from=7574&to=7575