W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2010

[Bug 10782] problems with button example for accesskey

From: <bugzilla@jessica.w3.org>
Date: Tue, 28 Sep 2010 07:14:51 +0000
To: public-html-a11y@w3.org
Message-Id: <E1P0UOp-0005bW-DB@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10782

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-28 07:14:51 UTC ---
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: Rejected
Change Description: no spec change
Rationale: Invalid use of bug system. Please only report one issue per bug.


Regarding the listed problems:

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

The user agent acts on the user's behalf. It is up to the user agent
implementor to ensure that the user's wishes are represented here.


> 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>"

If screen readers do not read these characters to the user then they are buggy
and should be fixed.


> 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.

I don't understand what the problem is here.


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

The script just gets told by the user agent.

-- 
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 Tuesday, 28 September 2010 07:14:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:14 UTC