Minutes from WCAG2ICT Task Force meetings
Minutes | Topics | Resolutions
Resolutions reflect general consensus of participants present in a meeting. They are not formal decisions of the group. Refer to the Decisions page for formal decisions. Context for each resolution is available via its link into the minutes.
- 25 April 2024: Announcements - Do not make extensive changes to WCAG2ICT Draft due to DoJ's new Rule. This will be handled in other resources outside of the Note.
- 18 April 2024: Glossary term "conforming alternate version" - Leave the WCAG2ICT guidance on "conforming alternate version" as it is in the current editor's draft ("does not use the term...")
- 11 April 2024: Question 2: Addressing public comments on 1.4.10 Reflow - Incorporate Option 3A with edits of "40" to "256" and removing last paragraph to replace notes 6 and 7 of 1.4.10 Reflow.
- 11 April 2024: Question 3: SC Problematic for Closed: 2.4.4 Link Purpose (In Context) - Incorporate Option 3, that has the small edit to add “being” as shown in the meeting minutes.
- 11 April 2024: Question 4: SC Problematic for Closed: 1.4.5 Images of Text - Incorporate Option 12 as shown in the meeting minutes.
- 4 April 2024: SC Problematic for Closed – 2.1.1 Keyboard - Incorporate option 5 for 2.1.1 Keyboard into the SC Problematic for Closed Functionality section, as-is.
- 4 April 2024: SC Problematic for Closed Functionality – 4.1.3 Status Messages - Incorporate option 4 for 4.1.3 Status Messages into the SC Problematic for Closed Functionality section, as-is
- 4 April 2024: Question 7: Issue 26: Adjustments to 4.1.1 Parsing to address AG WG concerns - Incorporate adjustments to 4.1.1 Parsing general guidance using option 2 and editing to expand DOM
- 14 March 2024: Approve public comment responses - Issue 216 - Finalize the answer to issue 216, as-is.
- 14 March 2024: SC Problematic for Closed Functionality – 4.1.2 Name, Role Value - Keep text as-is (Option 0) for Name, Role, Value in the SC Problematic for Closed Functionality section, and add Option 5's additional text to the introductory paragraph of the section..
- 14 March 2024: SC Problematic for Closed Functionality – 1.3.1 Info and Relationships - Use text in Option 3 (Gregg's edit above) for Info and Relationships in the SC Problematic for Closed Functionality section, and add Option 1's additional text to the introductory paragraph of the section.
- 7 March 2024: SC Problematic for Closed Functionality - 2.1.2 No Keyboard Trap - Incorporate the proposal for SC 2.1.2 No Keyboard Trap (linked above from the comment in issue 272) into the SC Problematic for Closed Functionality section, as-is.
- 7 March 2024: SC Problematic for Closed Functionality - 2.1.4 Character Key Shortcuts - Incorporate the proposal for SC 2.1.4 Character Key Shortcuts into the SC Problematic for Closed Functionality section, as edited by Mitch (above).
- 7 March 2024: SC Problematic for Closed Functionality - 2.4.7 Focus Visible - Incorporate the proposal for SC 2.4.7 Focus Visible into the SC Problematic for Closed Functionality section, as edited above.
- 29 February 2024: Issue 243 – Revisit TF decision on inclusion of WCAG intent sections - We will remove including the Understanding Intent sections starting with the next public draft.
- 29 February 2024: (3 of 4) 1.4.12 Text Spacing - Review new proposed Note 3 - Change draft to have no word substitutions on the SC 1.4.12 Text Spacing.
- 29 February 2024: (3 of 4) 1.4.12 Text Spacing - Review new proposed Note 3 - Include Note 3, for SC 1.4.12 Text Spacing as edited in the minutes above.
- 29 February 2024: (4 of 4) 1.4.12 Text Spacing - SC Problematic for Closed Functionality section - Update the SC Problematic for Closed for SC 1.4.12 Text Spacing, as edited by Bruce above.
- 22 February 2024: SC 4.1.3: Word substitution language - Incorporate the word substitution (which is really no word substitution) as as shown in Option 1 as-is for SC 4.1.3.
- 22 February 2024: SC 4.1.3: Notes 1 and 2 - Incorporate Notes 1 and 2 for SC 4.1.3 as proposed in the survey.
- 22 February 2024: SC 4.1.3: content for SC problematic for closed functionality - Incorporate into the proposed SC problematic for closed functionality, the proposed content for SC 3.3.8 as-is.
- 22 February 2024: Survey results - Question 5 of the Review of proposed responses to public comments - group 1 - Finalize the proposed answer to Issue 308 with the changes proposed by Mitch (removing the two paragraphs polled above) and adding a link in the first sentence to the key term "software".
- 22 February 2024: Issue 77 - Making content usable - Accept the changes and issue answer for Issue 77 as proposed in the survey.
- 15 February 2024: SC 3.3.8: Note 3 - Incorporate Note 3 by adding “If the non-web software is an application” to the beginning of the sentence.
- 15 February 2024: SC 3.3.8: Note 4 - Incorporate Note 4 as proposed in the survey.
- 15 February 2024: SC 3.3.8: Part 1 - content in SC problematic for closed functionality - Incorporate part 1 of the SC problematic for closed functionality for SC 3.3.8 as proposed in Option 2 in the Google doc
- 15 February 2024: SC 3.3.8: Part 2 - Content in SC problematic for closed functionality - Incorporate part 2 of the SC problematic for closed functionality for SC 3.3.8 as edited in the text shown in IRC (Phil's entry).
- 8 February 2024: Comments on Closed Functionality, CfC on Option to incorporate - Incorporate Option 1 from pull request 254 to finish the update to Comments on Closed Functionality.
- 8 February 2024: Issue 230 – 2.6 Software definition - Finalize the proposed answer to Issue 225 with the edit to add “Conclusion:” to the last paragraph.
- 8 February 2024: Issue 227: CSS Pixels: How to measure CSS pixel equivalents for systems with closed functionality - Finalize the proposed answer to Issue 227 as stated above.
- 8 February 2024: Issue 225 – More affirmative examples – 3 answered accept as is, as Mitch updated the typo in the comment already. - Finalize the proposed answer to Issue 225 as proposed, making the edits Fernanda and Mitch suggest in the survey.
- 1 February 2024: Comments on Closed Functionality, definition of “closed functionality” - Incorporate PRs 306 and 307 for Comments on Closed Functionality and “closed products” definition updates.
- 1 February 2024: Survey results for 2.4.8 Target Size (Minimum) and 3.3.8 Accessible Authentication - Incorporate the above note proposed for 2.5.8 as-is to that SC and to 1.4.10 and "perimeter" definition.
- 1 February 2024: note 2 - Incorporate Notes 1 and 2 as edited above into the SC problematic for Closed functionality for SC 2.5.8 Target Size (Minimum).
- 1 February 2024: 3.3.8 accessible authentication - Incorporate guidance for SC 3.3.8 Accessible Authentication up to the notes (per question 4 in the survey) as-is.
- 18 January 2024: 2.1.4 Character Key Shortcuts (proposal from Friday sub-group) - Don't add a note to 2.1.4 Character Key Shortcuts general guidance.
- 11 January 2024: Survey results: Review of proposed responses to public comments - Accept the proposed answers to public comments in Issues 5, 6, 77, 229, 261, and 268 as proposed in the survey, without changes.
- 11 January 2024: Survey results: Review of updated draft for 3.2.6 Consistent Help - Incorporate the proposal for Applying SC 3.2.6 Consistent Help to Non-Web Documents and Software section as-is.
- 11 January 2024: Survey results: Review of updated draft for 3.2.6 Consistent Help - Incorporate proposed Note 3 for SC 3.2.6 Consistent Help as-is.
- 11 January 2024: Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 - Incorporate bullets for SC 3.2.3 and 3.2.4 into the SC Problematic for Closed Functionality, as-is.
- 4 January 2024: Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 - Incorporate 2.5.2 Pointer Cancellation option 2, as above as-is, into the SC problematic for Closed Functionality section
- 4 January 2024: Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 - Incorporate 3.1.1 Language of Page bullet using Option 3 as-is into the SC problematic for closed functionality section.
- 4 January 2024: Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 - Incorporate 3.1.2 Language of Parts bullet using Option 3 as-is into the SC problematic for closed functionality section.
- 4 January 2024: Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 - update the text for 3.1.1 bullet to replace the phrase "this criterion does not apply" to "the intent of this success criterion would be met".
- 14 December 2023: Survey results: Review of remaining new term definitions - Accept all 4 of the term definitions (encloses, focus indicator, minimum bounding box, and perimeter) proposed in the survey as-is.
- 7 December 2023: Announcements - meeting next week 12/14
- 7 December 2023: Announcements - Next meeting after 12/14 is 1/4/2024
- 7 December 2023: Question 3: Relevance of 3.2.6 Consistent Help to SC Problematic for Closed Functionality - Do not add a bullet for 3.2.6 Consistent Help to the SC Problematic for Closed Functionality section.
- 16 November 2023: Survey results: Update to 4.1.1 Parsing for WCAG 2.0 and 2.1 - Incorporate update to SC 4.1.1 changing first “should” to “is to” and second “should no longer” to “would no longer”.
- 16 November 2023: Question 3: Add new WCAG 2.2 term “cognitive function test” - Add term “cognitive function test”, changing “Web sites” to “Web sites, non-web documents, and software”.
- 9 November 2023: Survey results: Updated proposal for 2.5.7 Dragging Movements - Add 2.5.7 Dragging Movements SC guidance proposal 2 from the survey into the editor’s draft, as-is.
- 9 November 2023: Survey results: Updated proposal for 2.5.7 Dragging Movements - Do not add a bullet for 2.5.7 Dragging Movements to the SC Problematic for Closed Functionality section.
- 9 November 2023: Survey results: Updated proposal for 2.5.7 Dragging Movements - Add “dragging movements” term to the Glossary Items that Apply to All Technologies section.
- 9 November 2023: Survey results: Proposal(s) for 2.4.11 Focus Not Obscured (Minimum) - Incorporate proposal for 2.4.11 Focus Not Obscured (Minimum), as-is.
- 9 November 2023: Survey results: Proposal(s) for 2.4.11 Focus Not Obscured (Minimum) - Do not add a bullet for 2.4.11 Focus Not Obscured (Minimum) to the SC Problematic for Closed Functionality section.
- 9 November 2023: Handling of 4.1.1 Parsing for changes made to WCAG 2.0 and 2.1 in WCAG2ICT - Publish one document to cover all three WCAG 2 versions and rename document to be for WCAG 2
- 9 November 2023: Question 1: New title for the section - Rename section to Comments on Closed Functionality
- 2 November 2023: Survey results: Updated proposal for 4.1.1 Parsing - Incorporate changes to 4.1.1 Parsing guidance as proposed, using Option 2 in the survey, as-is.
- 2 November 2023: Survey results: Updated proposal for 4.1.1 Parsing - Remove bullet for 4.1.1 Parsing from the SC Problematic for Closed Functionality section
- 2 November 2023: Discussion on 1.4.4 Resize Text - Respond to point 1 with option 2, as edited above with dates fixed.
- 26 October 2023: Survey results: Proposed changes to definitions - Incorporate proposed changes for “satisfies a success criterion” as-is.
- 26 October 2023: Survey results: Proposed changes to definitions - Incorporate proposed changes for definition of “conformance” as-is.
- 26 October 2023: Survey results: Proposed changes to definitions - Incorporate proposed changes for definition of “structure”, with edit to remove “user”.
- 26 October 2023: issue 219 "not applicable" is a pass - Incorporate the proposed change for “not applicable” into the Comments on Conformance section, as edited in PR 247.
- 26 October 2023: issue 219 "not applicable" is a pass - Finalize response to Issue 226 with the edits proposed in the survey and adding a reference to the update to the Comments on Conformance section.
- 19 October 2023: Survey on Draft Responses - Finalize response to #231, with edits to improve first sentence repetitive "modification supported" and reiterate why "user" should not be added.
- 19 October 2023: Survey on Draft Responses - Finalize response to issue 224, with the addition of a reference to a new issue we open committing to re-evaluate inclusion of intent.
- 19 October 2023: Definition of “menu-driven interface - Incorporate “menu-driven interface” definition, removing “easy-to-use” and "simple".
- 19 October 2023: 2.4.5 Multiple Ways - Incorporate closed functionality bullet for 2.4.5 Multiple Ways, splitting first sentence as shown Olivia's survey comments.
- 12 October 2023: Draft response to Issue 228 on 2.1 Accessibility Services of Platform Software - Send response for issue 228 as-is.
- 12 October 2023: Proposed change to guidance heading text - Change Guideline and principle headings as posted above.
- 12 October 2023: Proposed change to guidance heading text - Update the headings for the SC guidance using option 1 above.
- 12 October 2023: Proposed change to guidance heading text - update term definitions to be consistent such as "Applying “accessibility supported” to Non-Web Documents and Software"
- 12 October 2023: Survey results: Closed functionality: SCs 2.1.1, 2.4.2, and 2.4.5 - Incorporate 2.1.1 Keyboard option 3 with edits, as above. 1) Yes 2) no
- 12 October 2023: Survey results: Closed functionality: SCs 2.1.1, 2.4.2, and 2.4.5 - Incorporate 2.1.1 Keyboard option 3 with edits, as above.
- 12 October 2023: 2.4.2 Page titled - Accept Option 2 for 2.4.2 Page Titled, as-is.
- 12 October 2023: 2.4.2 Page titled - Accept Option 2 for 2.4.2 Page Titled, as-is.
- 5 October 2023: public comment on 2.2.2 pause stop hide - For Issue 232 - open a WCAG issue on the verbiage "information", adjust the response per Chuck's suggestion, and add reference to the WCAG issue to the response.
- 5 October 2023: public comment on 1.4.12 Text Spacing - Send response with the addition in IRC above labeled "Add" and send.
- 21 September 2023: FPWD public comments - Additional email in response to Mary Jo’s email on 7 Sept. need no further response.
- 21 September 2023: 2.4.1 Bypass blocks - Update 2.4.1 Bypass Blocks bullet using Option 2 as shown in the minutes.
- 7 September 2023: FPWD public comments - Send response on kiosk comment received on 15 August, as updated with the additional comment.
- 7 September 2023: 1.4.13 Content on Hover or Focus - Update 1.4.13 Content on Hover or Focus - remove the bullet.
- 31 August 2023: Survey results: Review updated proposals for SC Problematic for Closed Functionality - Incorporate option 5 above, as is for 1.3.2 Meaningful Sequence. Editors will edit overall Closed functionality section for consistency later and bring those back to the group.
- 31 August 2023: 1.4.12 Text Spacing - Update 1.4.12 Text spacing with option 3 above as-is.
- 17 August 2023: 1.4.10 reflow - Update 1.4.10 Reflow bullet using Option 1, with minor edit as shown in the minutes above.
- 3 August 2023: Survey Results: Review proposal for key term “closed functionality” definition - Incorporate the key term “closed functionality” as proposed.
- 3 August 2023: Introduction - Use the drafted Introductory sentence, with the edits in Option 2, shown above.
- 3 August 2023: Non-text content - Use the drafted Introductory sentence Option 2 as-is, shown above.
- 3 August 2023: Audio-only and video-only - Incorporate 1.2.1 and 1.2.3 using option 3 above, as-is
- 3 August 2023: 1.3.4 Orientation - Update 1.3.4 Orientation bullet using Option 3 above
- 27 July 2023: CfC to publish the First Public Working Draft - WCAG2ICT TF supports the publishing of the FPWD
- 27 July 2023: Survey Results - Incorporate the proposed updates for the above list of SC as-is.
- 13 July 2023: Survey results for Notes 3 & 4: Review of Proposals for SC 1.4.10 Reflow - Incorporate Note 3 into the editor’s draft, as noted above in the minutes.
- 13 July 2023: Survey results for Notes 3 & 4: Review of Proposals for SC 1.4.10 Reflow - Incorporate Note 4 option 3 into the editor’s draft, as shown above.
- 13 July 2023: Survey results: Review of "style property" definition - Incorporate “style property” draft into the editor’s draft, with the edits, as shown in the PR linked above.
- 13 July 2023: Survey results: Review of "set of web pages" definition - Incorporate Option 3, as is into the editor’s draft.
- 13 July 2023: Closed functionality survey - Add 1.4.10 Reflow bullet to the closed functionality section, as edited.
- 6 July 2023: Survey results: Review of proposals for SC 1.4.10 Reflow - Do not include additional examples.
- 6 July 2023: Survey results: Review of proposals for SC 1.4.10 Reflow - Incorporate combined proposal for Non-web documents Note 2, copied above.
- 6 July 2023: Survey results: Review of proposals for SC 1.4.10 Reflow - Add in Software Note 1 as-is, with an editor's note asking whether the guidance for software is good.
- 6 July 2023: Survey results: Review of proposals for SC 1.4.10 Reflow - For software note 2, use option 3 (but save option 1 in case public review or AG WG prefer less fuzzy language)
- 6 July 2023: Survey results: Review of proposals for SC 1.4.10 Reflow - Incorporate Remove Note 2 bullet 1 and incorporate text in Option 3 above, as-is.
- 6 July 2023: Survey results: Review of proposals for SC 1.4.10 Reflow - Incorporate edited version of Note 2's 3rd bullet.
- 6 July 2023: Survey results: Review of proposals for SC 1.4.10 Reflow - Incorporate Note 3 using option 2 as-is
- 29 June 2023: Survey results: Review proposed update to SC 2.5.8 Target Size (Minimum) - Replace existing non-web document note for 2.4.8 Target Size (Minimum) with the above version.
- 29 June 2023: Survey results: Continue CSS Pixel definition draft review - Incorporate Note 2 with edits and the explanation of where 2688 came from, as shown above.
- 29 June 2023: Survey results: Continue CSS Pixel definition draft review - Incorporate Note 3 with Loic's changes to remove normative language.
- 22 June 2023: Survey results: Pixel definition draft review - Incorporate Note 1, as above, provided the examples given do approximate the CSS pixel for the given platforms.
- 22 June 2023: Survey results: Pixel definition draft review - Do not include note 2.
- 8 June 2023: Survey results: 2.5.8 Target Size (Minimum) draft review - Equivalent: The function can be achieved through a different control [in the same non-web document or software] that meets this criterion.
- 8 June 2023: Survey results: 2.5.8 Target Size (Minimum) draft review - modify definition as stated above, replacing "page" with "content"
- 8 June 2023: Survey results: 2.5.8 Target Size (Minimum) draft review - we will remove the example above
- 8 June 2023: Survey results: 2.5.8 Target Size (Minimum) draft review - Incorporate 2.5.8 Target Size (Minimum) with the changes we agreed on today. Software notes 1 and 2 are on the definition of css pixels, remove the example, and modify definition note for target as discussed today.
- 6 April 2023: Project standup (status of your assigned issues) - Incorporate 1.4.11 Non-text Contrast into the editor’s draft as proposed with the closed functionality content as surveyed without changes.
- 30 March 2023: SC 1.4.12 Text Spacing readiness to incorporate into editor’s draft - Incorporate both 1.4.12 Non-text Contrast with the changes indicated in the linked comment above and Mary Jo’s editorial change.
- 30 March 2023: SC 2.5.2 Pointer Cancellation readiness to incorporate into editor’s draft - Merge 2.5.2 Pointer Cancellation into the editor’s draft with the changes Mitchell proposed and Bruce’s update to Note 1 (text above).
- 30 March 2023: SC 4.1.3 Status Messages readiness to incorporate into editor’s draft - Merge Mary Jo’s proposal with Fernanda’s proposed change and Mitchell’s edits for 4.1.2 Status Messages into the editor’s draft.
- 2 March 2023: Review Survey results for Key Terms and Glossary Items Used Only in AAA Success Criteria sections - Incorporate both the Key Terms and Level AAA-only definitions sections with the note and example changes as edited in the meeting.
- 2 March 2023: Review Survey results for SC 1.4.13 readiness to incorporate into editors draft - Merge the proposal for 1.4.13 into the editor’s draft with the edited text in Mary Jo’s comment on the issue (linked above)
- 23 February 2023: Survey: Review of SC 2.5.3 readiness to incorporate into editor’s draft - Incorporate SC 2.5.3 with the changes noted in the minutes: Change to note in the "name" and addition of closed functionality verbiage.
- 23 February 2023: Survey: Review of SC 2.5.3 readiness to incorporate into editor’s draft - Incorporate SC 2.5.3 with the changes noted in the minutes: Change to note in the "name" and addition of closed functionality verbiage.
- 16 February 2023: Survey WCAG2ICT-Abstract and Comparison sections readiness to incorporate into editor's draft - Merge the draft Abstract into the Editor’s draft with the last sentence removed.
- 16 February 2023: Survey WCAG2ICT-Abstract and Comparison sections readiness to incorporate into editor's draft - Incorporate the Comparison section as-is.
- 16 February 2023: Survey WCAG2ICT-Introductory sections' readiness to incorporate into editor's draft - use option 2 above and incorporate introduction sections into the draft
- 9 February 2023: Survey: Review of SC 2.5.4 readiness to incorporate into editor’s draft - Incorporate SC 2.5.4 into the editor’s draft as-is
- 2 February 2023: Discussion: Readiness of SC 2.1.4 proposal to incorporate into editor's draft - Incorporate SC 2.1.4 into the document with the polled changes above.
- 26 January 2023: Survey: Readiness of Background section proposal to incorporate into editor's draft - Incorporate the background section with the edits noted in the survey by Mary Jo and Olivia.
- 1 December 2022: Survey: Review proposed changes to guidelines - : Incorporate the Guidelines changes as-is and open an issue on the WCAG understanding to address Gregg’s comment.
- 10 November 2022: Final Poll results & discussion - Add a Background section to the WCAG2ICT document to explain how and where the 2013 WCAG2ICT Note has been relied upon.
- 10 November 2022: Final Poll results & discussion - Add a “Comparison to the 2013 WCAG2ICT Note“ section to the WCAG2ICT Note.
- 10 November 2022: Final Poll results & discussion - Do not add a Change log section to the WCAG2ICT Note.
- 27 October 2022: Naming / referencing conventions - Change to WCAG 2.0 to WCAG 2.2 throughout
- 6 October 2022: Continue discussion on survey results from the work statement review - Accept Patent policy section.
- 6 October 2022: Continue discussion on survey results from the work statement review - The scope of ICT covered will remain in the note and not in the work statement.
- 6 October 2022: Continue discussion on survey results from the work statement review - We will keep AAA in scope, keep it separate with WCAG's strong warning, and address later after A and AA are addressed.
- 6 October 2022: Continue discussion on survey results from the work statement review - Agree to Scope section with any amendments in pull request 2682.
- 29 September 2022: Question 3. Approach section - Accept amended approach section
- 29 September 2022: Question 7. Participation section - Accept Timeline Section
- 29 September 2022: Question 7. Participation section - Accept Participation Section