This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
| Max Depth: |
Bug 23615 depends on one bug:
view as bug list-
23615:
Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp
[RESOLVED MOVED; assigned to chaals; target: ---]
-
11140:
Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp
[CLOSED MOVED; assigned to chaals; target: ---]
-
11140:
Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp
[CLOSED MOVED; assigned to chaals; target: ---]
Bug 23615 blocks 19 bugs:
view as bug list-
23615:
Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp
[RESOLVED MOVED; assigned to chaals; target: ---]
-
10888:
Access Command Requirements for HTML5
[CLOSED MOVED; assigned to chaals; target: ---]
-
10772:
accesskey and an ordered set of unique space-separated tokens
[RESOLVED MOVED; assigned to ian; target: LC]
-
10774:
fallback for accesskey insufficiently defined
[VERIFIED WONTFIX; assigned to ian; target: LC]
-
10775:
how is user to decide which set of access keys to use?
[VERIFIED FIXED; assigned to oedipus; target: LC]
-
10776:
accesskey value token subsets
[RESOLVED WONTFIX; assigned to ian; target: LC]
-
10777:
user agent assignment of modifier keys subset of accesskey processing subset
[RESOLVED FIXED; assigned to ian; target: LC]
-
10778:
use element.accessKeyLabel to generate list of available accesskeys
[CLOSED MOVED; assigned to ian; target: LC]
-
10905:
clarify how assigning an accesskey to an element affects the elements default role
[CLOSED DUPLICATE; assigned to chaals; target: ---]
-
10066:
replace section 3.2.6 with the alternative spec text provided (ARIA)
[RESOLVED FIXED; assigned to ian; target: ---]
-
10484:
default roles for figcaption and caption: Make it simple to achieve accessibility
[RESOLVED WONTFIX; assigned to faulkner.steve; target: LC]
-
10495:
default role(s) "inheriting" for figure - common use cases
[VERIFIED INVALID; assigned to ian; target: LC]
(*)
-
10497:
What happens to role of <img alt="non-empty"> inside a <figure role="img">?
[CLOSED WORKSFORME; assigned to faulkner.steve; target: LC]
-
10484:
default roles for figcaption and caption: Make it simple to achieve accessibility
[RESOLVED WONTFIX; assigned to faulkner.steve; target: LC]
-
23611:
clarify how assigning an accesskey to an element affects the elements default role
[CLOSED DUPLICATE; assigned to chaals; target: ---]
-
23616:
clarify how assigning an accesskey to an element affects the elements default role
[RESOLVED MOVED; assigned to chaals; target: ---]
-
10066:
replace section 3.2.6 with the alternative spec text provided (ARIA)
[RESOLVED FIXED; assigned to ian; target: ---]
-
10994:
accessKeyLabel can expose new information about the user and possibly also other origins
[RESOLVED DUPLICATE; assigned to chaals; target: ---]
-
23611:
clarify how assigning an accesskey to an element affects the elements default role
[CLOSED DUPLICATE; assigned to chaals; target: ---]
(*)
-
23613:
Access Command Requirements for HTML5
[RESOLVED MOVED; assigned to chaals; target: ---]
-
10772:
accesskey and an ordered set of unique space-separated tokens
[RESOLVED MOVED; assigned to ian; target: LC]
(*)
-
10774:
fallback for accesskey insufficiently defined
[VERIFIED WONTFIX; assigned to ian; target: LC]
(*)
-
10775:
how is user to decide which set of access keys to use?
[VERIFIED FIXED; assigned to oedipus; target: LC]
(*)
-
10776:
accesskey value token subsets
[RESOLVED WONTFIX; assigned to ian; target: LC]
(*)
-
10777:
user agent assignment of modifier keys subset of accesskey processing subset
[RESOLVED FIXED; assigned to ian; target: LC]
(*)
-
10778:
use element.accessKeyLabel to generate list of available accesskeys
[CLOSED MOVED; assigned to ian; target: LC]
(*)
-
10905:
clarify how assigning an accesskey to an element affects the elements default role
[CLOSED DUPLICATE; assigned to chaals; target: ---]
(*)
-
10994:
accessKeyLabel can expose new information about the user and possibly also other origins
[RESOLVED DUPLICATE; assigned to chaals; target: ---]
(*)
-
23611:
clarify how assigning an accesskey to an element affects the elements default role
[CLOSED DUPLICATE; assigned to chaals; target: ---]
(*)
-
23614:
accessKeyLabel can expose new information about the user and possibly also other origins
[RESOLVED MOVED; assigned to chaals; target: ---]
(*)
-
23616:
clarify how assigning an accesskey to an element affects the elements default role
[RESOLVED MOVED; assigned to chaals; target: ---]
(*)
-
10772:
accesskey and an ordered set of unique space-separated tokens
[RESOLVED MOVED; assigned to ian; target: LC]
-
23614:
accessKeyLabel can expose new information about the user and possibly also other origins
[RESOLVED MOVED; assigned to chaals; target: ---]
(*)
-
23616:
clarify how assigning an accesskey to an element affects the elements default role
[RESOLVED MOVED; assigned to chaals; target: ---]
(*)
-
10772:
accesskey and an ordered set of unique space-separated tokens
[RESOLVED MOVED; assigned to ian; target: LC]
-
23613:
Access Command Requirements for HTML5
[RESOLVED MOVED; assigned to chaals; target: ---]
(*)
-
10888:
Access Command Requirements for HTML5
[CLOSED MOVED; assigned to chaals; target: ---]
| Max Depth: |