ISSUE-1 |
CLOSED |
Use of “[Sufficient]” and “[Advisory]” in Introduction Success Criteria section |
2008-07-18 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-2 |
CLOSED |
Defining conformance level by limitations - Introduction: Success Criteria |
2008-07-18 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-3 |
CLOSED |
"Widest range of disabilities" - Introduction: Organization: Success Criteria Levels |
2008-07-18 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-4 |
CLOSED |
Description of SC AA isn't clear |
2008-07-25 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-5 |
CLOSED |
A.1. Overlap with A.2.3 |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-6 |
CLOSED |
A.1 Chrome as a term |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-7 |
CLOSED |
A.1.1 and A.1.2 reword so it is more obvious they are parallel. |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-8 |
CLOSED |
A.1.2 titles need work |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-9 |
CLOSED |
A.1.2 keyword for accessibility platform architecture. |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-10 |
CLOSED |
A.1.2.1 “or leverage existing implementations of the architecture.” is not clear |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-11 |
CLOSED |
A.1.2 conformance levels |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-12 |
CLOSED |
A.1.3: cite conventions |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-13 |
CLOSED |
A.1.3.2: Term: Keyboard Configuration is unclear |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-14 |
CLOSED |
SC A.2.1.1 and A.2.1.2: change order to improve clarity. |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-15 |
CLOSED |
SC A.2.1.1 needs to improve clarity |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-16 |
CLOSED |
SC A.2.1.2 (a) should reference or merge with A.2.3.1 |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-17 |
CLOSED |
SC A.2.1.2 (b) explanation of Time-Based Media |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-18 |
CLOSED |
A.2.2 Success Criteria don't follow numbering conventions |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-19 |
CLOSED |
A.2.3.3 needs a better title |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-20 |
CLOSED |
SC A.2.3.5 needs clarification |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-21 |
CLOSED |
A.2.3.7 move to Part B or A.1 |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-22 |
CLOSED |
SC A.3.1.1 Keyboard - Harmonize with UAAG |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-23 |
CLOSED |
SC A.3.2.1 needs clarification |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-24 |
CLOSED |
SC A.3.6.1 overlaps with A.2 |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-25 |
CLOSED |
A.3 New Success Criteria to support Speech Input users |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-26 |
CLOSED |
A.4.1 and A.4.4 merge |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-27 |
CLOSED |
A.4.2.1 also belongs in Operable Keyboard (A.3.1) |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-28 |
CLOSED |
A.4.3.3 Error is passed in text and available to accessibility architecture. |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-29 |
CLOSED |
Guideline A.4.3 broaden beyond text. |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-31 |
CLOSED |
A.1.1.1-3. Remove "Web-based" |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-33 |
CLOSED |
A.1.2.2 Conformance level |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-38 |
CLOSED |
A.2.1 Naming non-text-objects |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-41 |
CLOSED |
A.2.2.5 Why sign language |
2008-07-25 |
ATAG Part A |
0 |
| ISSUE-67 |
CLOSED |
A.3.7 Note – May not meet the needs of low-vision users |
2008-07-26 |
ATAG Part A |
0 |
| ISSUE-74 |
CLOSED |
B.1.2 needs to clarify when it is used |
2008-07-26 |
ATAG Part B |
0 |
| ISSUE-75 |
CLOSED |
B.1.2.1(a) Add: should be available to AT |
2008-07-26 |
ATAG Part B |
0 |
| ISSUE-76 |
CLOSED |
B.2.1.1 At most this is AAA – it tries to establish design principles in UI |
2008-07-26 |
ATAG Part B |
0 |
| ISSUE-77 |
CLOSED |
B.2.1.2 If user deactivates prompts, it is not tool's fault |
2008-07-26 |
ATAG Part B |
0 |
| ISSUE-79 |
CLOSED |
B.2.2.1 Makes HTML a gating factor – needs to be more general. |
2008-07-26 |
ATAG Part B |
0 |
| ISSUE-83 |
CLOSED |
B.2.4 is unclear what we are trying to establish. |
2008-07-26 |
ATAG Part B |
0 |
| ISSUE-84 |
CLOSED |
B.2.4.3 is unclear what is meant by “Object Database” |
2008-07-26 |
ATAG Part B |
0 |
| ISSUE-88 |
CLOSED |
B.2.5.3(a) is too difficult. Should be level AAA |
2008-07-26 |
ATAG Part B |
0 |
| ISSUE-98 |
CLOSED |
Label location missing from Part A |
2008-07-27 |
ATAG Part A |
0 |
| ISSUE-101 |
CLOSED |
Part A is missing an SC not to have autofills or changing content of preceding field. |
2008-07-27 |
ATAG Part A |
0 |
| ISSUE-104 |
CLOSED |
B.1.1 Rationale is unclear |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-105 |
CLOSED |
B.1.1.1 [Editorial] uses “automatically” twice in phrase. |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-106 |
CLOSED |
B.1.2.1(a) needs to be available to end users and programmatically to AT. |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-107 |
CLOSED |
B.2.2.9 Seems to contradict the following note |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-108 |
CLOSED |
B.2.4.3 seems too restrictive |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-109 |
CLOSED |
B.3.1.1 needs a different example |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-110 |
CLOSED |
B.3.2.2 Move to Level A |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-111 |
CLOSED |
B.3.3.3 is an annoying requirement. |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-112 |
CLOSED |
B.3.3.4 should be Level A |
2008-07-27 |
ATAG Part A |
0 |
| ISSUE-113 |
CLOSED |
B.3.5 Doesn't have the SC Conformance levels matching the SC level. |
2008-07-27 |
ATAG Part B |
0 |
| ISSUE-114 |
CLOSED |
Conformance → Benchmark Document -> Include section could be combined with the Required section. |
2008-07-27 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-115 |
CLOSED |
Conformance → Benchmark Document → Include #5. Is a normative requirement an SC or a Guideline? |
2008-07-27 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-142 |
CLOSED |
Appendix D: Add current members |
2008-07-27 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-144 |
CLOSED |
A.1.1 clarify the rational for why guidelines are divided into web-based v. non-web-based |
2008-07-28 |
ATAG Part A |
0 |
| ISSUE-145 |
CLOSED |
A.2 clarifications |
2008-07-28 |
ATAG Part A |
0 |
| ISSUE-146 |
CLOSED |
Conformance -> Benchmark #4 needs work |
2008-07-28 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-147 |
CLOSED |
Conformance -> Benchmarks Is ATAG requiring more than what is being required by WCAG? |
2008-07-28 |
ATAG 2.0 Guidelines |
0 |
| ISSUE-150 |
CLOSED |
B.1.2.2 may not be feasible |
2008-07-28 |
ATAG Part B |
0 |
| ISSUE-151 |
CLOSED |
B.2 Are we requiring validation be built in. Coordination with Note |
2008-07-28 |
ATAG Part B |
0 |
| ISSUE-152 |
CLOSED |
A.3 do we want to include the use of non-conventional keys if documented? |
2008-07-28 |
ATAG Part A |
0 |
| ISSUE-153 |
CLOSED |
A.4 [Editorial] |
2008-07-28 |
ATAG Part A |
0 |