W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 23612] New: problems with button example for accesskey

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Oct 2013 19:47:07 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23612-2486@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23612

            Bug ID: 23612
           Summary: problems with button example for accesskey
           Product: HTML.next
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Keywords: a11y, a11ytf, a11y_focus
          Severity: normal
          Priority: P2
         Component: default
          Assignee: chaals@yandex-team.ru
          Reporter: mark@w3.org
        QA Contact: public-html-bugzilla@w3.org
                CC: cooper@w3.org, ian@hixie.ch, joshue.oconnor@cfit.ie,
                    laura.lee.carlson@gmail.com, mike@w3.org,
                    oedipus@hicom.net, public-html-a11y@w3.org,
                    public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org, robin@w3.org
        Depends on: 10782
            Blocks: 10888

+++ This bug was initially created as a clone of Bug #10782 +++

QUOTE
In the following example, a button has possible access keys described. 
A script then tries to update the button's label to advertise the key 
combination the user agent selected.

<input type=submit accesskey="N @ 1" value="Compose">
...
<script>
 function labelButton(button) {
   if (button.accessKeyLabel)
     button.value += ' (' + button.accessKeyLabel + ')';
 }
 var inputs = document.getElementsByTagName('input');
 for (var i = 0; i < inputs.length; i += 1) {
   if (inputs[i].type == "submit")
     labelButton(inputs[i]);
 }
</script>

On one user agent, the button's label might become "Compose (&#8984;N)". On 
another, it might become "Compose (Alt+&#8679;+1)". If the user agent doesn't 
assign a key, it will be just "Compose". The exact string depends on 
what the assigned access key is, and on how the user agent represents 
that key combination.
UNQUOTE


PROBLEM 1: The user should be the ultimate arbiter of which accesskey
to apply, not the user agent

    The exact string depends on which of the suggested access key sets 
    is in use, and upon how the user agent represents the key 
    combinations that comprise that set of accesskeys.


PROBLEM 2: there are characters used in the last paragraph that are
not exposed when using a screen reader -- in particular: 

   "<samp>Compose (&#8984;N)</samp>". On another, it might become
   "<samp>Compose (Alt+&#8679;+1)</samp>"

since the use of special characters constitutes ascii art, the 
character entities should be glossed using ABBR as follows:

   "<samp>Compose (<abbr title="Command-Key">&#8984;</abbr>N)</samp>"
   "<samp>Compose (Alt+<abbr title="UpArrow">&#8679;</abbr>+1)</samp>"

such extended characters should NOT be used in UA notifications, as the
values expressed using symbolic characters will not be read by a 
screen reader -- it is better for the UA to report "CommandKey+N"
and "ALT + UpArrow + 1"


PROBLEM 3: currently, the draft states: "If the user agent doesn't 
assign a key, it will be just "Compose". The exact string depends on 
what the assigned access key is, and on how the user agent represents 
that key combination."

PROPOSED:
If a user has set their user agent to use a specific key or key 
combination as accesskey modifiers, or if no modifier key has been 
pre-set as a default by the user agent, the user agent must not 
assign a specifc key, but simply report "Compose". The exact string 
depends on what the assigned access key is, and on how the user agent 
represents that key combination.


PROBLEM 4: how does the user notify the script which set of access 
keys that user wishes to use?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 23 October 2013 19:47:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC