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 10066 depends on 54 bugs:
view as bug list-
10066:
replace section 3.2.6 with the alternative spec text provided (ARIA)
[RESOLVED FIXED; assigned to ian; target: ---]
-
8000:
ARIA roles added to the a element should be conforming in HTML5
[RESOLVED FIXED; assigned to faulkner.steve; target: ---]
-
9817:
Details element Focus problem
[CLOSED WORKSFORME; assigned to faulkner.steve; target: LC]
-
10438:
math should be changed changed from no role to "math" role
[RESOLVED WONTFIX; assigned to faulkner.steve; target: ---]
-
10439:
<input type=file> has "button" role, but is typically a compound control
[RESOLVED FIXED; assigned to faulkner.steve; target: Unsorted]
-
10440:
menu type=context should have "menu" role
[RESOLVED WONTFIX; assigned to faulkner.steve; target: ---]
-
10441:
<link> that represents a hyperlink should probably have no role by default
[RESOLVED WONTFIX; assigned to faulkner.steve; target: ---]
-
10444:
ARIA section does not list elements that have no default role or role restrictions
[RESOLVED LATER; assigned to faulkner.steve; target: ---]
-
10445:
Certain elements with no role should have that as a strong semantic
[RESOLVED FIXED; assigned to ian; target: ---]
-
10446:
Consider limiting the roles of certain media and plugin elements
[RESOLVED FIXED; assigned to ian; target: ---]
-
10447:
<output> should not have a status role by default after all
[RESOLVED FIXED; assigned to faulkner.steve; target: ---]
-
10448:
Consider broadening the set of allowed roles for command elements
[RESOLVED FIXED; assigned to faulkner.steve; target: ---]
-
10449:
Consider allowing various command-like ARIA roles for h1-h6
[RESOLVED WONTFIX; assigned to faulkner.steve; target: ---]
-
10450:
Allow lists to be used as menus or tab sets
[RESOLVED FIXED; assigned to faulkner.steve; target: ---]
-
10451:
Consider restricting the roles allowed for the label element
[RESOLVED LATER; assigned to faulkner.steve; target: ---]
-
10452:
Consider documenting attributes that map to ARIA properties in a separate table
[RESOLVED WONTFIX; assigned to cyns; target: ---]
-
10462:
merge ARIA mapping tables and list
[CLOSED LATER; assigned to faulkner.steve; target: ---]
-
10463:
provide a comprehensive HTML5 to accessibility API mapping reference
[RESOLVED WONTFIX; assigned to faulkner.steve; target: ---]
-
10464:
provide clear user friendly links to WAI-ARIA documents in the ARIA section of the spec
[RESOLVED DUPLICATE; assigned to ian; target: Unsorted]
-
10465:
provide correct aria mapping and role info for the table element
[VERIFIED DUPLICATE; assigned to ian; target: ---]
-
10467:
provide headings in the WAI-ARIA section of the spec to make it easier to understand
[RESOLVED WONTFIX; assigned to ian; target: ---]
-
10478:
modify table, tr and td roles
[RESOLVED FIXED; assigned to faulkner.steve; target: ---]
-
10479:
add role=radiogroup to details element
[RESOLVED FIXED; assigned to faulkner.steve; target: ---]
-
10481:
Default role of <IMG> should be "img"
[RESOLVED FIXED; assigned to xn--mlform-iua; target: LC]
-
10485:
The img element with non-empty alt should default to the img aria role
[RESOLVED DUPLICATE; assigned to ian; target: ---]
-
10486:
References to "image" ARIA role should be "img"
[RESOLVED FIXED; assigned to ian; target: ---]
-
10487:
Allow radio buttons and checkboxes to be used as radio and check menu items respectively
[RESOLVED FIXED; assigned to ian; target: ---]
-
10493:
"ARIA restricts usage of this role to one per page" is an unclear statement
[RESOLVED FIXED; assigned to mike; target: ---]
-
10494:
modify aria example and fix spelling
[VERIFIED FIXED; assigned to ian; target: ---]
-
10496:
fix error in aria conformance checker advice
[RESOLVED FIXED; assigned to ian; target: ---]
-
10591:
conflicting info for table element in aria section
[RESOLVED FIXED; assigned to ian; target: ---]
-
10592:
"h1 to h6 element that does have an hgroup ancestor" not listed in ARIA section
[RESOLVED LATER; assigned to faulkner.steve; target: ---]
-
10593:
thead, tfoot and tbody conflicts in aria section
[RESOLVED WORKSFORME; assigned to ian; target: ---]
-
10594:
conforming use of various aria attributes not specified
[RESOLVED WONTFIX; assigned to ian; target: ---]
-
10600:
Strong semantics role="presentation" for <img alt="<empty>"> is wrong or inaccurate
[RESOLVED WONTFIX; assigned to ian; target: LC]
-
10603:
Clarify what default roles UAs may assign to elements not listed in the ARIA section
[RESOLVED FIXED; assigned to faulkner.steve; target: ---]
-
10614:
Clarify what <img role=presentation alt=<not-the-empty-string> > means
[RESOLVED WONTFIX; assigned to aria-ua-impl; target: Working Draft]
(*)
-
10618:
Use "no ARIA-defined role" rather than "no role" in the weak/strong ARIA tables
[CLOSED WONTFIX; assigned to faulkner.steve; target: ---]
-
10903:
provide an introduction to wai-aria in the wai aria section of the spec
[RESOLVED LATER; assigned to faulkner.steve; target: ---]
-
10905:
clarify how assigning an accesskey to an element affects the elements default role
[CLOSED DUPLICATE; assigned to chaals; target: ---]
-
10888:
Access Command Requirements for HTML5
[CLOSED MOVED; assigned to chaals; target: ---]
-
10779:
triggering the Action of the command via accesskey
[CLOSED WONTFIX; assigned to chaals; target: LC]
-
10780:
reference to definition of Action insufficient for definition of accesskey
[RESOLVED NEEDSINFO; assigned to chaals; target: LC]
-
10782:
problems with button example for accesskey
[CLOSED MOVED; assigned to chaals; target: LC]
-
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: ---]
-
23612:
problems with button example for accesskey
[RESOLVED FIXED; assigned to chaals; target: ---]
-
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: ---]
-
10779:
triggering the Action of the command via accesskey
[CLOSED WONTFIX; assigned to chaals; target: LC]
-
23613:
Access Command Requirements for HTML5
[RESOLVED MOVED; assigned to chaals; target: ---]
-
10779:
triggering the Action of the command via accesskey
[CLOSED WONTFIX; assigned to chaals; target: LC]
(*)
-
10780:
reference to definition of Action insufficient for definition of accesskey
[RESOLVED NEEDSINFO; assigned to chaals; target: LC]
(*)
-
10782:
problems with button example for accesskey
[CLOSED MOVED; assigned to chaals; target: LC]
(*)
-
10888:
Access Command Requirements for HTML5
[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: ---]
(*)
-
23612:
problems with button example for accesskey
[RESOLVED FIXED; assigned to chaals; target: ---]
(*)
-
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: ---]
(*)
-
10779:
triggering the Action of the command via accesskey
[CLOSED WONTFIX; assigned to chaals; target: LC]
-
10888:
Access Command Requirements for HTML5
[CLOSED MOVED; assigned to chaals; target: ---]
-
10914:
Allow multiple space separated values for the ARIA role attribute
[RESOLVED LATER; assigned to faulkner.steve; target: LC]
-
10919:
Allow role="presentation" to override the default role of any element
[RESOLVED NEEDSINFO; assigned to contributor; target: LC]
(*)
-
12590:
@role=presentation for IMG should also require that @title is empty
[RESOLVED WONTFIX; assigned to contributor; target: ---]
-
23611:
clarify how assigning an accesskey to an element affects the elements default role
[CLOSED DUPLICATE; assigned to chaals; target: ---]
-
10888:
Access Command Requirements for HTML5
[CLOSED MOVED; assigned to chaals; target: ---]
(*)
-
10905:
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: ---]
(*)
-
23616:
clarify how assigning an accesskey to an element affects the elements default role
[RESOLVED MOVED; assigned to chaals; target: ---]
-
10888:
Access Command Requirements for HTML5
[CLOSED MOVED; assigned to chaals; target: ---]
(*)
-
10905:
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: ---]
(*)
-
10888:
Access Command Requirements for HTML5
[CLOSED MOVED; assigned to chaals; target: ---]
-
10888:
Access Command Requirements for HTML5
[CLOSED 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: ---]
(*)
-
8000:
ARIA roles added to the a element should be conforming in HTML5
[RESOLVED FIXED; assigned to faulkner.steve; target: ---]
Bug 10066 blocks 4 bugs:
view as bug list-
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]
| Max Depth: |