ISSUE-30 |
OPEN |
Introduction->Organization->Part A #3 Authoring tool must be understandable |
2008-07-25 |
ATAG 2.0 Guidelines |
0 |
ISSUE-32 |
OPEN |
A.1.2 Success Criteria do not apply to content display. |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-34 |
OPEN |
A.1.2.3 Proper Use needs a definition |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-35 |
OPEN |
A.1.2.4 circumbents platform guidance |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-36 |
OPEN |
A.1.3 need to clarify this use of "platform" |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-37 |
OPEN |
A.1.3.2 Citing conventions |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-39 |
OPEN |
A.2.2.1 "identifiable by the authoring tool" is too ambiguous |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-40 |
OPEN |
A.2.2.4 terms for chrome and what is included in chrome |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-42 |
OPEN |
A.2.3.1 Setting Name, Role and Value in UI |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-43 |
OPEN |
A.2.3.4 Properties must be available programmatically |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-44 |
OPEN |
A.2.3.5 is not testable |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-45 |
OPEN |
A.2.3.7 unrealistic and should be moved to part B |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-46 |
OPEN |
A.2.4.1 can be combined with A.2.4.4 |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-47 |
OPEN |
A.2.4.2 differentiation of color |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-48 |
OPEN |
A.2.4.5 Audio display platform settings not inclusive |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-49 |
OPEN |
A2.4.6 and A.2.4.7 is not testable |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-50 |
OPEN |
A.2.4.8 needs example to clarify the need. |
2008-07-25 |
ATAG Part A |
0 |
ISSUE-51 |
OPEN |
A.3.1.1 Wording change to clarify UI and Content |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-52 |
OPEN |
A.3.1.4 Not testable |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-53 |
OPEN |
A.3.1.5 Forward and backward do not apply to 2D UI |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-54 |
OPEN |
A.3.1.7 Should not be Level AA |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-55 |
OPEN |
A.3.1.9 Difference between group and inter-group is unclear |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-56 |
OPEN |
A.3.2.1 The way it is phrased may not give the users what they want. |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-57 |
OPEN |
A.3.2.4 Doesn't allow for trial versions or multiple day time limts or expirations |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-58 |
OPEN |
A.3.4.1 Move to Part B |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-59 |
OPEN |
A.3.4.2 Move to Part B |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-60 |
OPEN |
A.3.4.3 How to define if implicit or explicit tree structure is available? |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-61 |
OPEN |
A.3.5.1 Too hard to implement, should be Level AAA |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-62 |
OPEN |
A.3.5 Note is unclear on UI functionality in browser |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-63 |
OPEN |
A.3.6.1 Don't think this is necessary – all tools do it |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-64 |
OPEN |
A.3.6.2 Should be level AAA |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-65 |
OPEN |
A.3.6.3 Need to add that a platform wizard satisfies this SC. |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-66 |
OPEN |
A.3.7.2 How can Previews meet Part A? |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-68 |
OPEN |
A.4.2.1 may not be testable |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-69 |
OPEN |
A.4.2.3 Not clear if it is consistent with the app. |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-70 |
OPEN |
A.4.2.4 needs an example |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-71 |
OPEN |
A.4.3.1 Not testable |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-72 |
OPEN |
A.4.3.2 Could be Level AA |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-73 |
OPEN |
A.4.3.7 Note 2: Needs to be generalized to cover more undo merge actions |
2008-07-26 |
ATAG Part A |
0 |
ISSUE-78 |
OPEN |
B.2.2 - All SC need to be read for testability |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-80 |
OPEN |
B.2.2.3 Has to be acceptable for items which cannot be realistically scanned. |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-81 |
OPEN |
B.2.2.7 Needs to support real-time checking |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-82 |
OPEN |
B.2.3 needs to be checked for testability |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-85 |
OPEN |
B.2.4.4 “Storing for Reuse” is ahead of its time |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-86 |
OPEN |
B.2.5.1. Needs better wording – doesn't apply to all content template situations |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-87 |
OPEN |
B.2.5.2 Not testable. |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-89 |
OPEN |
B.2.5.4 Recording the accessibility of a template is unrealistic |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-90 |
OPEN |
B.2.5.7 could result in overload problems for UI |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-91 |
OPEN |
B.3.2.1 “sequence” is unclear |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-92 |
OPEN |
B.3.2.2 Make Level A |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-93 |
OPEN |
B.3.5.1 needs to be restated so it keeps spirit without being so stringent |
2008-07-26 |
ATAG Part B |
0 |
ISSUE-94 |
OPEN |
Glossary – user Interface |
2008-07-26 |
ATAG 2.0 Guidelines |
0 |
ISSUE-95 |
OPEN |
General Part A: Refer to ISO 9241-171 or be as comprehensive |
2008-07-27 |
ATAG 2.0 Guidelines |
0 |
ISSUE-96 |
OPEN |
Introduction → Conformance: Objects to qualification about disabilities |
2008-07-27 |
ATAG 2.0 Guidelines |
0 |
ISSUE-97 |
OPEN |
Introduction → Conformance: Objects to partial conformance claiming |
2008-07-27 |
ATAG 2.0 Guidelines |
0 |
ISSUE-99 |
OPEN |
A.1.2 - web based authoring tools should not be exempt |
2008-07-27 |
ATAG Part A |
0 |
ISSUE-100 |
OPEN |
A.3.1 - keyboard functionality is incomplete |
2008-07-27 |
ATAG Part A |
0 |
ISSUE-102 |
OPEN |
A.3.5 - Provide text search should be Level A |
2008-07-27 |
ATAG Part A |
0 |
ISSUE-103 |
OPEN |
A.3.7.1 - Returning from Previews |
2008-07-27 |
ATAG Part A |
0 |
ISSUE-116 |
OPEN |
Conformance Claims → Required Components → #4.a [Editorial] consistency in naming levels |
2008-07-27 |
ATAG 2.0 Guidelines |
0 |
ISSUE-117 |
OPEN |
Glossary → Accessibility platform architecture. Remove platform. Include Mac OS APIs. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-118 |
OPEN |
Glossary → Accessibility problem [Editorial] Typo |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-119 |
OPEN |
Glossary → accessibility information needs to be more clear. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-120 |
OPEN |
Glossary → assistive technology voice recognition |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-121 |
OPEN |
Glossary → authoring tool user interface needs work. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-122 |
OPEN |
Glossary → Captions. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-123 |
OPEN |
Glossary → change of context. Negative examples don't make clear what it is. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-124 |
OPEN |
Glossary → checking accessibility. |
2008-07-27 |
|
0 |
ISSUE-125 |
OPEN |
Glossary → content generation. Not clear |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-126 |
OPEN |
Glossary – conversion: See “transformation” |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-127 |
OPEN |
Glossary – direct accessibility. Not clear what is meant. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-128 |
OPEN |
Glossary – display settings #2. [Editorial] Fix grammar |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-129 |
OPEN |
Glossary – documentation. Add video tutorials. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-130 |
OPEN |
Glossary – equivalent alternative. Doesn't include the time aspect of synchronization in the definition. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-131 |
OPEN |
Glossary – human language. As opposed to what? |
2008-07-27 |
|
0 |
ISSUE-132 |
OPEN |
Glossary – informative.[Editorial] Incomplete sentence |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-133 |
OPEN |
Glossary – non-text objects. Include more examples |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-134 |
OPEN |
Glossary – normative: Link to Conformance section. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-135 |
OPEN |
Glossary – platform. Needs to discriminate between OS and Accessibility APIs. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-136 |
OPEN |
Glossary – prominence. Add position in navigation hierarchy. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-137 |
OPEN |
Glossary – technology. Not clear |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-138 |
OPEN |
Glossary – user agent. [Editorial] Fix grammar |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-139 |
OPEN |
Glossary – user interface component. Remove “chrome”. |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-140 |
OPEN |
Glossary – view #1.a doesn't match definition of “mark-up” |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-141 |
OPEN |
Glossary – view #1.c. Typo: it's |
2008-07-27 |
ATAG Glossary |
0 |
ISSUE-143 |
OPEN |
make our list parallel the order of WCAG 2.0 - perceivable, operable, understandable, robust? |
2008-07-28 |
ATAG 2.0 Guidelines |
0 |
ISSUE-148 |
OPEN |
Conformance: Assumptions about User Agents |
2008-07-28 |
ATAG 2.0 Guidelines |
0 |
ISSUE-149 |
OPEN |
Need to clarify the distinctions between success criteria for Level A, AA, AAA success criterias for B.1.1 |
2008-07-28 |
ATAG Part B |
0 |
ISSUE-154 |
OPEN |
Raised by Cynthia about Part B - pushing feeds to provide accessible API |
2008-07-29 |
|
0 |
ISSUE-155 |
OPEN |
Should A.3.1.2 remain in Part A because it relates to the Editing view of the tool or deleted because it is covered elsewhere? |
2008-07-29 |
|
0 |
ISSUE-156 |
OPEN |
A.3.3.2 needs add an option to block rendering |
2008-07-29 |
|
0 |
ISSUE-157 |
OPEN |
A.1.2.2: Should this remain in Part A as it's an exception to following the accessibility platform architectures which we are substituting in for much of Part A. |
2008-07-29 |
|
0 |
ISSUE-158 |
OPEN |
A.1.2.3: Should this remain in Part A as it's an exception to following the accessibility platform architectures which we are substituting in for much of Part A. |
2008-07-29 |
|
0 |
ISSUE-159 |
OPEN |
A.1.2.4: Should this remain in Part A as it's an exception to following the accessibility platform architectures which we are substituting in for much of Part A. |
2008-07-29 |
|
0 |
ISSUE-160 |
OPEN |
A.3.2.2: Where else will this be covered if we remove it from Part A? Won't WCAG only cover timing in the content produced by the tool and not the tool itself? |
2008-07-29 |
|
0 |
ISSUE-161 |
OPEN |
A.3.2.4: Where else will this be covered if we remove it from Part A? Won't WCAG only cover timing in the content produced by the tool and not the tool itself? |
2008-07-29 |
|
0 |
ISSUE-162 |
OPEN |
Should there be separate conformance by parts? |
2008-07-29 |
|
0 |
ISSUE-163 |
OPEN |
Editorial - Should [For the authoring tool user interface] be removed? |
2008-07-29 |
|
0 |
ISSUE-164 |
OPEN |
Should the preview and editing modes of Authoring Tool be UAAG compliant? Would not be Level A. |
2008-07-29 |
|
0 |
ISSUE-165 |
OPEN |
Navigate identical elements |
2008-07-29 |
|
0 |
ISSUE-166 |
OPEN |
Navigate headings |
2008-07-29 |
|
0 |
ISSUE-167 |
OPEN |
Definition of "functional equivalent" |
2008-10-23 |
|
0 |
ISSUE-168 |
OPEN |
A.3.6 needs to be focused for needs specific to authoring tools |
2008-10-23 |
|
0 |
ISSUE-169 |
OPEN |
Look at detailed techniques for B.1.2.1 & 2 (at all levels) |
2008-10-24 |
|
0 |
ISSUE-170 |
OPEN |
Create an Appendix on Ageing population requirements in conjunction with WAI-AGE project |
2008-10-24 |
|
0 |
ISSUE-171 |
OPEN |
More strenuous support of alt in ATAG than in the WCAG guidelines. |
2008-10-24 |
|
0 |
ISSUE-172 |
OPEN |
Provide additional success criteria in B.2.3 on repair |
2008-10-24 |
|
1 |
ISSUE-173 |
OPEN |
Rework B.2.4 to be more clear |
2008-11-03 |
|
0 |
ISSUE-174 |
OPEN |
Add to Status section of next version: Integration of checking and repair tools in B.2.2 and B.2.3 |
2008-11-21 |
ATAG Part B |
0 |
ISSUE-175 |
OPEN |
Reorganizing the Conformance Levels - see email http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0004.html |
2009-04-06 |
|
0 |
ISSUE-176 |
OPEN |
Impact of conformance of the three levels, A, AA, AAA. http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0004.html |
2009-04-06 |
|
0 |