- From: Loretta Guarino Reid <lorettaguarino@google.com>
- Date: Thu, 19 Apr 2012 14:34:33 -0700
- To: gijs@anysurfer.be
- Cc: public-comments-wcag20@w3.org
- Message-ID: <CAHu5OWaY1vHqvVs-CUfqe2kZjWULhvbtghZs03+pywYgBVK57w@mail.gmail.com>
On Wed, Mar 28, 2012 at 6:56 AM, <noreply@w3.org> wrote: > Name: Gijs Veyfeyken > Email: gijs@anysurfer.be > Affiliation: AnySurfer > Document: QR > Item Number: Success Criterion 2.4.3 > Part of Item: > Comment Type: technical > Summary of Issue: please add 'disabling focus outline with CSS' as a > Failure for SC 2.4.3 - Focus Order > Comment (Including rationale for any proposed change): > Please add an item to "Failures for SC 2.4.3 - Focus Order". Numerous > websites cannot be navigated with a keyboard because the designer behind it > hides the visual focus with CSS (outline:none). Also, many reset > stylesheets contain this CSS rule, and therefore it's usage is widespread. > > Proposed Change: > Add hiding keyboard-focus with CSS (outline:none) to "Failures for SC > 2.4.3 - Focus Order". > > ================================ Response from the Working Group ================================ Hiding the visual focus with CSS is not a failure of SC 2.4.3 (Focus Order), but it is a failure of SC 2.4.7 (Focus Visible). F78: "Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator" lists this use of outline:none as its first example. Loretta Guarino Reid, WCAG WG Co-Chair Gregg Vanderheiden, WCAG WG Co-Chair Michael Cooper, WCAG WG Staff Contact On behalf of the WCAG Working Group
Received on Thursday, 19 April 2012 21:35:02 UTC