[Bug 23612] problems with button example for accesskey


--- Comment #1 from Charles McCathieNevile <chaals@yandex-team.ru> ---
(In reply to Mark Sadecki from comment #0)
> +++ This bug was initially created as a clone of Bug #10782 +++

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

Yes, but this is a problem of implementation in the user agent, although the
specification should make it clear that this is an important issue. I'll raise
a separate bug.

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

This problem still exists.

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

This doesn't seem to be a good solution. On the other hand, the idea that
authors should be responsible for providing information about an activation
method controlled by the browser seems ridiculous. The whole example, and the
idea behind it that the user interaction behaviour is not the responsibility of
the browser, is broken and needs to be fixed.

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

That is again a user agent implementation issue - the user should not notify
the script, but only the browser. The script in this example doesn't set the
key, it merely repeats what the browser reports to it as the activation method.

You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 18 December 2014 14:55:47 UTC