Note: Items highlighted in yellow (also marked with "@@") indicate action items that need to be completed before the issue can be closed.
| Issue Number | Summary | Disposition (rough) |
|---|---|---|
| Aggregation Issues | ||
| 464 | Clarify that if parts unknown - whole is unknown | Answer: New wording should make this clear. Author/creator is responsible. |
| 1168 | Conf if author uses tech where UA can stop blink? | Answer: If there is a mech to stop blinking then yes. AeWT list will address this. @@ keep open to address questions about what is sufficient for 2.2.2 |
| 1222 | Limit responsibiity of Author to what he authors | Not Accept. A page conforms or it doesn’t. |
| 1318 | No Clear how Aggregators can claim Conf. Examples. | Accept @@@ More information & examples provded in Understanding Conf 1332 |
| 1332 | Captions &AD too expensive to do in timely manner | [HANDLE IN LEVEL CHANGE. |
| Alternate Version Issues | ||
| 465 | Require reciprocal links between alternate versions | Partial: @@ add advisory tech for reciprocal links |
| 466 | 4.2.1 can be misinterpreted and require recip. Links | Partial New wording of CC-5 clarifies this, @@add Adv Tech for reciprical links |
| 514 | 4.2.1 Change "the content" to "each Web unit in the content" | Accept. We revised conformance to clarify. conformance is on a Web page basis. |
| 515 | 4.2.3 Change "the content" to "each Web unit in the content" | Accept. We revised conformance to clarify. conformance is on a Web page basis. |
| 545 | can be misinterpreted (4.2.1 and 4.2.3) | Accept. We revised conformance to clarify. conformance is on a Web page basis. |
| 762 | move criterion to conformance, clarify | Accept. We revised conformance to include criterion re conformance in a process. |
| 836 | move criterion about collections in 4.2 to conformance | Accept. We revised conformance significantly. clarified how claims for collections can be made. |
| 947 | add L2 to require that default version is accessible | Not Accept, but (@@) include as recc. In intent & as advisory techs for CC-5, CC-6 |
| 963 | Make Equiv. Facil. A principle, define user experience reqs by referencing UAAG | Partial_Accept. New wording & conformance criterion/techniques addresses this |
| 985 | require that alternate versions be identical | Accept: @@ reintroduce "alternate version" term to CC-5 & reference definition in response |
| 1149 | clarify if SC need to be met all the time | Accept: Addressed in new wording. |
| 1208 | rewrite conformance to accommodate alternatve solutions to access problems | Accept: CC-5 doesn’t specifically exclude alternatives that are not page for page. @@@ In Understanding this is made clear. |
| 1442 | clarify when fallbacks are sufficient | Accept: Addressed by CC-5 and new wording |
| Authored Unit Issues | ||
| 745 | Don't use 'web-unit or authored component' | Accept. Removed Authored component |
| 1179 | Authored Unit needs work Definition | Accept - LEAVE OPEN til will fix definition |
| 1319 | Authored Unit and Authored component look the same | Accept - LEAVE OPEN til will fix definition |
| 1493 | Authored Unit needs work Definition | Accept - LEAVE OPEN til will fix definition |
| Baseline Issues | ||
| 513 | require use of tech according to spec | Not accept. Group concluded that this is beneficial, but beyond what is required. |
| 530 | baseline could lead to belief that OK to create content inaccessible to some | Accept. Baseline has been replaced "assume" no longer used |
| 531 | assocate a "base accessibility value" to various baselines | Partial accept. Addressed by conformance criterion and AeWT |
| 565 | add SC prohibiting use of deprecated features at level 2 and L1 on layout tables | F46 covers layout table proposal, not all deprecated features are accessibility issues, those that are are addressed in failures |
| 588 | if there is a baseline, there should be a minimum req. for HTML | Not accept minimum requirement and explain that WCAG 2.0 should apply to all techs. Explain AeWT |
| 638 | require that users know what the baseline is | Not accept since conformance claims are optional |
| 643 | Reword to make clear that nonbaseline must conform too if possible | Partial: Reworded. moved to conformance. Recommend all be accessible as possible |
| 646 | No Baseline. Specify HTML as min requirement. | Not Acccept: WCAG 2.0 not technology specific. Must meet guidelines only. |
| 648 | Need to specify Minimum Baselines. Outside of WCAG OK | Accept: Sufficient techniques now allow WG to identify 'good enough' Sets of AeWT |
| 649 | Delete Baseline: too complex. Delete scoping: loophole | Partial: Baseline replaced "Scope out" language removed. |
| 652 | Don't keep baseline, do more than visual impairment, L3 should be 100% | Partial - now 100% for level 3, Baseline replaced We do many disabilities. |
| 737 | Need to have alt when baseline tech fails. No scoping out. | Partial: Baseline replaced w/ concept that addresses. "Scope out" language removed. |
| 750 | Clarify what 4.2.2 applies to | Accept. New language in conformance (where 4.2.2 was moved to) |
| 751 | Suggested a complete new version of conformance | Partial. Conformance completely reworked. Many issues raised were addressed. |
| 807 | Clarify baseline and give examples | Accept Concept reformulated, explained and "understanding' document introduced. |
| 812 | Change levels to include baseline | Partial: New formulation gets at part of this. But Levels must be stable. |
| 880 | Don't list 'relied upon'. List what in baseline was not RU. | Not accept:. The baseline was replaced. It may include 50 technologies. |
| 889 | Clarify the Baseline concept | Accept: Baseline has been removed and replaced with more concrete concept. |
| 902 | Clarify. If you mean 'must have AT support" then say that | Accept: Hopefully this is clearer in the new conformance section and UA definitions. |
| 908 | Conf. claim requires baseline - but WCAG doesn’t specify. | Accept: Baseline has been removed and replaced with more concrete concept. |
| 951 | Baseline concept still difficult to comprehend | Accept: Baseline has been removed and replaced with more concrete concept. |
| 953 | Baseline too hard to figure. Need context specific examples | Partial: Baseline has been removed and replaced with more concrete concept. |
| 997 | Need clearer statement of intent of baseline. To avoid abuse. | Accept: Baseline has been removed and replaced with more concrete concept. |
| 998 | Give baseline guidance. Publish reasonalbe baselines | Accept: Baselines replaced with guidance. "Sufficient" sets are in Understanding doc |
| 1007 | Move baselines, examples & 1.0 into "understanding" doc. | Partial: Some of this is done. @@@ Maybe do more? Keep claim examples??? |
| 1014 | Move examples and WCAG 1.0 info out. | Partial: Much removed. WCAG 1.0 reduced to paragraph and link to more info. |
| 1028 | remove baselne and only allow UAAG programs in baseline | Parital Accept: Baseline replaced with more concrete approach that avoids problem. |
| 1029 | remove baselne and only allow UAAG programs in baseline | Parital Accept: Baseline replaced with more concrete approach that avoids problem. |
| 1030 | Provide a definition for baseline | Accept: Baseline has been removed and replaced with more concrete concept. |
| 1031 | remove baselne and only allow UAAG programs in baseline | Parital Accept: Baseline replaced with more concrete approach that avoids problem. |
| 1032 | Develop a suitable baselines document and update annually | Accept: Baseline replaced with "list of AeWT that will be updated" |
| 1034 | remove baselne and only allow UAAG programs in baseline | Parital Accept: Baseline replaced with more concrete approach that avoids problem. |
| 1035 | remove baselne and only allow UAAG programs in baseline | Parital Accept: Baseline replaced with more concrete approach that avoids problem. |
| 1037 | Create a 'Guide to Policymakers" with external review | Accept: That is in our plans - but not yet done. |
| 1041 | Provide guidance on baselines (also to Policymakers) | Accept: Guidance now provided. Policymake guide planned for future. |
| 1088 | Specify if Scripts are part of baseline in Timing, Situation A | Not accept: Baseline is separate from SC. We have changed baseline concept. |
| 1145 | Clarify baseline requirements Vis-à-vis levels | Accept: this should be clearer in the new document |
| 1213 | Baselines unclear. Specify implmentation plan to test them | Partial: Baseline replaced with more concrete concept. CR exit criteria part of WCAG |
| 1220 | Baseline only good if not abused. Methods needed to prevent | Accept: New formulation and list of "sufficient" AeWT should help here. |
| 1246 | "Assume" is bad. No guidance on baselines. | Accept: Removed "assume". New formulation. Guidance included now. |
| 1247 | Baseline hare to understand. Needs examples too. | Accept: Baseline has been removed and replaced with more concrete concept. |
| 1248 | Another 2 examples of baselines for companies please | Partial: New concept replaces baseline and new "Understanding doc" to explain |
| 1270 | remove "assume" | Accept: "Assume removed and baseline concept changed to more concrete approach. |
| 1271 | Change "browser" to "user agent" | Accept: "Browser" removed. |
| 1273 | More Baseline examples, here or in another doc | Accept: New concept for Baseline and new section on it in "Understanding" doc. |
| 1274 | Baseline guidance, annual recommendations, explaination | Accept: New formulation and list of "sufficient" AeWT now provided |
| 1311 | Conformance Complex, Baseline guidance to avoid abuse. | Accept: New conformance. Baseline replaced and guidance & Sufficient now provided. |
| 1314 | Baseline doestn take User agent limitations into account. | Partial: New formulation and sufficientl AeWT lists address this. |
| 1315 | More emphasis on UAs that content was tested with. | Parital: UAs tested with is listed as an optional item directly in the guidelines. |
| 1316 | need more concrete and realistic examples of baselines | Partial: New concept replaces baseline and new "Understanding doc" to explain |
| 1411 | Jpeg is not one spec. Jpeg in baseline meaningless. | Partial: Baseline examples removed. More specifics can be provided in AeWT lists |
| 1494 | Baselines depend too heavily on "assumptions" | Accept: "Assume removed and baseline concept changed to more concrete approach. |
| Conformance Issues | ||
| 465 | Require reciprocal links between alternate versions | Partial: @@ add advisory tech for reciprocal links |
| 466 | 4.2.1 can be misinterpreted and require recip. Links | Partial New wording of CC-5 clarifies this, @@add Adv Tech for reciprical links |
| 507 | Scope out User input | Accept - |
| 514 | 4.2.1 Change "the content" to "each Web unit in the content" | Accept. We revised conformance to clarify. conformance is on a Web page basis. |
| 515 | 4.2.3 Change "the content" to "each Web unit in the content" | Accept. We revised conformance to clarify. conformance is on a Web page basis. |
| 539 | Timed tests could not pass Level 3 | Not accept. You are Correct - but that is our intent. |
| 545 | can be misinterpreted (4.2.1 and 4.2.3) | Accept. We revised conformance to clarify. conformance is on a Web page basis. |
| 692 | Testable conformance criteria should be added. | Partial: new conformance section includes Testable CC |
| 750 | Clarify what 4.2.2 applies to | Accept. New language in conformance (where 4.2.2 was moved to) |
| 751 | Suggested a complete new version of conformance | Partial. Conformance completely reworked. Many issues raised were addressed. |
| 762 | move criterion to conformance, clarify | Accept. We revised conformance to include criterion re conformance in a process. |
| 812 | Change levels to include baseline | Partial: New formulation gets at part of this. But Levels must be stable. |
| 830 | Remove ability to "scope out" | Partial Scoping out language removed. |
| 836 | move criterion about collections in 4.2 to conformance | Accept. We revised conformance significantly. clarified how claims for collections can be made. |
| 857 | Use NA instead of pass for SC that you don't use. | Not accept: You must conform to all SC. If NA is used, too much chance of abuse. |
| 862 | Nobody knows what the hell a web unit is | Accept - Using Web Page now. {resurvey the rest now} |
| 869 | No exemption for teaching. No accomodation for languageless docs. | Partial: Teaching exemption added. @@@ Languageless docs mostly resolve themselves |
| 880 | Don't list 'relied upon'. List what in baseline was not RU. | Not accept:. The baseline was replaced. It may include 50 technologies. |
| 896 | Note 1 referest to AAA conf but not yet defined | Accept: Note removed in new conformance section |
| 924 | Use a consistent prioritization scheme in all WAI specs | Accept: new format is consistent except to remove error: AAA very important for some |
| 939 | If diff languages negotiated all must have accessible version | Accept: New language cover this @@ |
| 947 | add L2 to require that default version is accessible | Not Accept, but (@@) include as recc. In intent & as advisory techs for CC-5, CC-6 |
| 949 | Explain Regular expressions | Accept: Moved to UNDERSTANDING DOC and examples provided. |
| 963 | Make Equiv. Facil. A principle, define user experience reqs by referencing UAAG | Partial_Accept. New wording & conformance criterion/techniques addresses this |
| 985 | require that alternate versions be identical | Accept: @@ reintroduce "alternate version" term to CC-5 & reference definition in response |
| 1023 | Treat L3 like every other level | Accept - now 100% required for level 3 |
| 1038 | Allow ability to specify which disabilities catered to | Partial: We removed the sentence. Nothing preventing people now from saying they cater. |
| 1040 | Vertical Scoping | Partial: "Scoping out" language removed. |
| 1042 | All versions from Accessible. L3 all version accessible. | Partial: All info must be in accessible version. But other version are allowed even at L3. |
| 1148 | Conformance and 4.2 contradict each other | Accept: We have combined them and resolved this conflict in new wording. |
| 1149 | clarify if SC need to be met all the time | Accept: Addressed in new wording. |
| 1208 | rewrite conformance to accommodate alternatve solutions to access problems | Accept: CC-5 doesn’t specifically exclude alternatives that are not page for page. @@@ In Understanding this is made clear. |
| 1210 | Date-qualified claims - earlier in doc. | Partial: This isn't part of conformance but @@@ added to Understanding Conformance. |
| 1211 | Problem with note saying "cannot talk about disabilities) | Accept; Sentence has been removed. |
| 1212 | Can't require 'informed testers'. Web authors often not. | Not Accept: Can't have a technical spec that is testable by people who don't understand it. |
| 1214 | Don't require processes to be accessible. Only recommend | Not Accept: Being able to complete tasks is key to conformance having meaning. |
| 1215 | Alternatives need to be at more levels than leaf level | Accept: CC-5 doesn’t specifically exclude alternatives that are not page for page. @@@ In Understanding this is made clear. |
| 1222 | Limit responsibiity of Author to what he authors | Not Accept. A page conforms or it doesn’t. |
| 1244 | WCAG 1.0 references can be confusing out of context | Accept: All WCAG 1.0 references are in separate section now or in Understanding doc |
| 1245 | Reduce wordiness of "sufficient' explaination | Accept: @@ use their wording |
| 1249 | Scoping language confusing. Explain. | Partial: Sentence has been removed. |
| 1250 | Conformance seems like it has a 'get out of jail free" card | Partial: Processes are now required to be accessible. |
| 1268 | Does "suffient" approach allow author to do anything | Partial: We don't want to stop equiv alternatives. But if not using 'sufficient' technique then burden of proof is on author. |
| 1309 | 50% too easy to meet. Requrie 100% | Accept - now 100% required for level 3 |
| 1311 | Conformance Complex, Baseline guidance to avoid abuse. | Accept: New conformance. Baseline replaced and guidance & Sufficient now provided. |
| 1411 | Jpeg is not one spec. Jpeg in baseline meaningless. | Partial: Baseline examples removed. More specifics can be provided in AeWT lists |
| 1442 | clarify when fallbacks are sufficient | Accept: Addressed by CC-5 and new wording |
| 1470 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| Level AAA Issues | ||
| 516 | A Level 3 equvalent to 4.2.1 and 4.2.3 | Accept - this is now provided by our new Conformance Section |
| 533 | 50% too easy to meet. Requrie 100% | Accept - now 100% required for level 3 |
| 539 | Timed tests could not pass Level 3 | Not accept. You are Correct - but that is our intent. |
| 605 | 50% too easy to meet. Requrie 100% | Accept - now 100% required for level 3 |
| 619 | Mechanism must be accessible mechanism | Done - but held up because L3 was not 100%. Now is 100% } |
| 621 | 50% too easy to meet. Requrie 100% | Accept - now 100% required for level 3 |
| 652 | Don't keep baseline, do more than visual impairment, L3 should be 100% | Accept - now 100% for level 3, Baseline removed, We do many disabilities. |
| 691 | 50% too easy to meet. Requrie 100% | Accept - now 100% required for level 3 |
| 888 | Need to decide which L3 are needed for conformance | Accept - now 100% required for level 3 |
| 1023 | Treat L3 like every other level | Accept - now 100% required for level 3 |
| 1264 | Why is L3 only SOME of l3 | Accept - now 100% required for level 3 |
| 1275 | change from 50% to "100% unless not applicable" | Accept - now 100% required for level 3 |
| 1309 | 50% too easy to meet. Requrie 100% | Accept - now 100% required for level 3 |
| Levels Issues | ||
| 482 | More clearly define what the levels are | Accept - new definitions and explaination provided in Understanding Levels |
| 614 | Reword what L3 Means - it is also Minimal | Partial - Accept. Changed to not say less important. Now says "very important" |
| 662 | Are levels truly different from WCAG 1.0? | Correct. Not very different. Differences are now outlined in Understanding Levels. |
| 737 | RE levels: too cryptic | Clearer descriptions of levels |
| 813 | Don't repeat SC on diff levels. | They are not repeated. They are different levels of implementation. |
| 831 | RE levels: too cryptic | Clearer descriptions of levels |
| 897 | Define levels in measurable parameters | Not Accept. The rationale for the levels is in Understanding Levels. Not formulaic |
| 898 | "can be reasonably" is too vague | Accept. Wording removed - Now reads: …. |
| 899 | Level descriptions not clear. What is benefit | Clearer descriptions of levels. Addional information now in Understanding Levels |
| 919 | Distinction betwee L1, L2, L3 is arbitrary. All hinder. | Clearer descriptions of levels. Addional information now in Understanding Levels |
| 1242 | Expand and explain the rationale for Levels | Clearer descriptions of levels. Addional information now in Understanding Levels |
| 1266 | All SC are essential contradicts L1 Minimum Level | Not Accept. There can be a minimum even though some need more. |
| 1303 | Remove levels or revert to WCAG 1.0 scheme | Not Accept. Very similar to 1.0 except acknowdge all levels important to someone. |
| Web-Unit Issues | ||
| 514 | Not clear that conformance is by web-unit in 4.2.1 | Accept - new language in conformance makes this clear. 4.2 moved to conformance |
| 515 | Not clear that conformance is by web-unit in 4.2.3 | Accept - new language in conformance makes this clear. 4.2 moved to conformance |
| 711 | {Held up just to settle "web-units" question | {change to Web-pages and send up for approval in survey} |
| 808 | Just use Web Page | Accept. Using Web page in these places now. {resurvey with Web Page } |
| 862 | Nobody knows what the hell a web unit is | Accept - Using Web Page now. {resurvey the rest now} |
| 895 | provide example of Web unit that is not web page | Accept. Using Web Page now. |
| 916 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 929 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 983 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 1193 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 1217 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 1241 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 1263 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 1410 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 1470 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |
| 1510 | {Held up just to settle "web-units" question | {Adopt Web-page term and send up for approval in survey} |