W3C home > Mailing lists > Public > public-html@w3.org > August 2011

[Bug 13568] New: use of "accessible" to refer to placement of UI controls is confusing

From: <bugzilla@jessica.w3.org>
Date: Wed, 03 Aug 2011 03:41:20 +0000
To: public-html@w3.org
Message-ID: <bug-13568-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13568

           Summary: use of "accessible" to refer to placement of UI
                    controls is confusing
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/spec/common-input-element-attr
                    ibutes.html#attr-input-autocomplete
        OS/Version: Windows NT
            Status: NEW
          Keywords: a11y, a11ytf
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: cyns@microsoft.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


"A user agent may allow the user to override the resulting autocompletion state
and set it to always on, always allowing values to be remembered and
prefilled), or always off, never remembering values. However, the ability to
override the resulting autocompletion state to on should not be trivially
accessible, as there are significant security implications for the user if all
values are always remembered, regardless of the site's preferences."

Please use a term other than "trivially accessible" and reserve the term
"accessible" for accessibility by users with disabilities.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 3 August 2011 03:41:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:37 GMT