WCAG2ICT Task Force Meeting Resolutions
Minutes | Topics | Resolutions
This page was last updated on 25 July 2025. For more recent meetings, see an alternative view of meeting minutes.
2025
-
24 July: WCAG2ICT Task Force Teleconference
- Issue 612 - 2.5.7 Dragging Movements - "underlying platform software" vs "user agent or platform software - Incorporate PR 734, making use of "underlying platform software" and "user agent or other platform software" consistent throughout
- Issue 740: 2.1.1 Keyboard - Should we add a precondition scoping this SC? - For 2.1.1 Keyboard, incorporate Proposal 4 into the editor's draft, as-is
-
17 July: WCAG2ICT Task Force Teleconference
- Issue 706 - 3.1.2 Language of Parts: EN 301 549 has an extra note for non-web docs - do we need it in WCAG2ICT? - Update Proposal 1 in PR 714 as noted above, and add this new note to SC 3.1.2
- Issue 691 - Differences between 2.1.1 keyboard guidance in WCAG2ICT and EN 301 549 content in clause 11.2.1.1 Keyboard - To incorporate Proposal 3 in PR 718 into SC 2.1.1 as-updated in the meeting.
-
10 July: WCAG2ICT Task Force Teleconference
- Editorial changes – covering Issues 699, 636, and for Issue 699: Changed notes would benefit from parenthetical "(Modifed)" - Merge editorial PRs 701 and 722 into the editor’s draft, as-is
- Issue 605 - 4.1.2 Name, Role, Value: clarify that non-web software does not have a user agent - For SC 4.1.2 - Make bolding changes noted above to PR 721 and then merge.
-
3 July: WCAG2ICT Task Force Teleconference
- Issue 702 - 1.3.1: The EN 301 549 added a note for non-web documents we should consider including in WCAG2ICT - Add the proposed Note 1 for non-web documents to SC 1.3.1, as-is
- Issue 691 - Differences between 2.1.1 keyboard guidance in WCAG2ICT and EN 301 549 content in clause 11.2.1.1 Keyboard - Modify Note 1 of 2.1.1 Keyboard to the text noted in IRC above
-
26 June: WCAG2ICT Task Force Teleconference
- Issue 707 – Add in "non-web" where needed for consistency with the EN 301 549 - Add in “non-web” in front of “document” per PR 694 to make WCAG2ICT consistent with the EN 301 549
- Issue 695 - 1.4.10 Reflow: Note 7 applies to non-web documents and to software but is listed under non-web software parenthetic - For 1.4.10 Reflow, implement proposal 1 in Issue 695, as-is
-
19 June: WCAG2ICT Task Force Teleconference
- Issue 620 – Closed functionality - To resolve issue 620, use the proposed answer, as-is
- Issue 696 - 2.2.2 Pause, stop, hide: Note 5 should provide the full info about the WCAG 2.2 Intent section - To resolve issue 686, merge PR 697, as-is
- Issue 618 - [Editorial issues (mostly consistency) within the WCAG2ICT language - To resolve issue 618, merge PR 689, as-is
- Issue 605 - Name, Role, Value: clarify that non-web software does not have a user agent - To resolve issue 605, merge PR 632, as-is
- Issue 606 - Revise word substitution in glossary "target" - To resolve issue 606, merge PR 698, as-is
-
12 June: WCAG2ICT Task Force Teleconference
- Adjustments to 1.4.2, 2.1.2, 2.2.2 and 2.3.1 for consistency and getting rid of "must" - To replace "must" with "it would be necessary for" in SCs 1.4.2, 2.1.2, 2.2.2, and 2.3.1
- Adjustments to 1.4.2, 2.1.2, 2.2.2 and 2.3.1 for consistency and getting rid of "must" - Word replacement language use proposal 2 changing "word "must"" to "normative term "must"".
- PR 683 - further changes to make the notes the same - Update SC 3.2.3 with changes from PR 687.
-
29 May: WCAG2ICT Task Force Teleconference
- Question 5: (3 of 3) Non-web Software - Notes - Do not have any notes for the newly created Non-web Software Titled criterion.
- Question 5: (3 of 3) Non-web Software - Notes - Remove the closed functionality bullet for 2.4.2 Page Titled.
-
22 May: WCAG2ICT Task Force Teleconference
- Survey results: Review proposed updates to 2.4.2 Page Titled - Use proposal 2 introductory verbiage replacing "This should not be applied" with "This success criterion is problematic to apply".
- (Question 2 of 3) Non-web Software - SC language - Use proposal 2 substituting "Named" with "Titled" in the short name.
-
15 May: WCAG2ICT Task Force Teleconference
- Question 1 - Formatting: Use of headings vs. parenthetic statements - Use headings to denote non-web document vs. non-web software guidance where it makes it clearer - including for 2.4.2.
-
24 April: WCAG2ICT Task Force Teleconference
- Issue #622: Edit to note in 2.1.1 Keyboard to make it more understandable - Accept the changes to 2.1.1 Keyboard Note 1, as proposed.
- Issue #625: Need further clarity in the key term definition of “content (on and off the web)” - Add note to key term "content" regarding 3rd party content as shown in the minutes above.
- Issue #625: Need further clarity in the key term definition of “content (on and off the web)” - Add the note "For non-web software, content also includes the user interface." to the key term "content (on and off the web)"
-
10 April: WCAG2ICT Task Force Teleconference
- PR to update WCAG2ICT overview page to incorporate our "explainer" content - Proposed update to the WCAG2ICT Overview (PR 1197), with the changes to the PR agreed in today’s meeting, can be incorporated into the WAI website.
-
9 January: WCAG2ICT Task Force Teleconference
- WCAG2ICT Phase 2 Work Statement - Once all of the noted edits have been incorporated into the work statement, it is ready to send to the AG WG for review and approval.
2024
-
21 November: WCAG2ICT Task Force Teleconference
- Working session: Update the work statement PR - Remove bullet on "providing a determination..." from out of scope to add phil's suggested language (above in minutes) to the in-scope list.
- Working session: Update the work statement PR - Move Level AAA to its own in-scope bullet and put it at the bottom of the list
-
14 November: WCAG2ICT Task Force Teleconference
- Part 2 – Proposed outline for the WCAG2ICT explainer - The proposed WCAG2ICT Explainer outline is ready to send to the AG WG for review, as-is.
-
5 September: WCAG2ICT Task Force Teleconference
- Question 1 - Issue 473 (Issue answer): Definitions and explanations for “Set of Documents” and “Set of Software Programs” produces strange corner cases that should be addressed or explained - Answer Issue 473 as proposed.
- Question 2 - Issue 427: 4.1.1 Parsing: does it need to be added in 'problematic for closed'? - Incorporate the content for 4.1.1 Parsing into the section SC Problematic for Closed Functionality using Option 4, as-is.
- Question 3 - Issue 383 part 1 (Text before the list): Adjust links in Guidance section to link to all task force and AG publications - Incorporate the changes to the text before the list as proposed and edited in Option 4 (text above) into the Guidance in this Document section.
- Question 4 - Issue 383 part 2 (Changing the bulleted list): Adjust links in Guidance section to link to all task force and AG publications - Update the document listing in Guidance in this document section using Option 3, as-is.
- Question 6 - Issue 427 – Issue 394 part 1 (Bullet for 1.4.10 in SC problematic): SC Problematic for Closed Functionality 1.4.10 Reflow: Note should include “or content” - Incorporate Option 2 changes for 1.4.10 Reflow into the SC Problematic for Close Functionality section.
- Question 7 - Issue 394 part 2 (General guidance for 1.4.10 Reflow): SC Problematic for Closed Functionality 1.4.10 Reflow: Note should include “or content” - Incorporate the proposed changes in Option 2 into 1.4.10 Reflow general guidance as proposed in the Google doc.
- Question 8 - Issue 394 part 3 (General guidance for 1.4.10 Reflow): SC Problematic for Closed Functionality 1.4.10 Reflow: Note should include “or content” - Answer Issue 394 using Option 2, edited to include the PR link.
- Answer for Issue 464 - Answer Issue 464 as proposed.
- Answer for Issue 466 - Answer Issue 466, as edited in the Google doc.
-
29 August: WCAG2ICT Task Force Teleconference
- Question 8 - Issue 436 part 1 (replacing "user agent"): The definition of 'large scale' needs substitutions or notes - Incorporate the changes proposed in Option 2 into the definition of 'large scale', as proposed in survey questions 8 and 9.
- Question 1, Issue 465 Part 2 (SC 2.1.1 and "keyboard interface"): Seeking clarity for key term 'underlying platform software' - Remove "Underlying" from the definition of "keyboard interface" and SC 2.1.1 Note 1, as proposed.
- Q11. Issue 421 part 1 ('keyboard interface' changes): In definition of 'keyboard interface' and in 2.1.1, "would satisfy the success criterion" is incomplete - Incorporate the changes in Option 3 into Note 1 in the definition of 'keyboard interface', as-shown above.
- 12. Issue 421 part 2 (SC 2.1.1 Keyboard changes): In definition of 'keyboard interface' and in 2.1.1, "would satisfy the success criterion" is incomplete - Incorporate Option 4 changes into SC 2.1.1, as posted in the minutes above, as-is.
- 3. Issue 465 Part 4 (Issue answer): Seeking clarity for key term 'underlying platform software' - Answer Issue 465, as edited in the meeting and posted above in the minutes.
- 2. Issue 465 Part 3 (SC 3.3.8): Seeking clarity for key term 'underlying platform software' (returning to previous question) - Incorporate the changes in Option 5 into SC 3.3.8 Accessible Authentication, as-is (also posted above in the minutes).
- 4. Issue 466: Closed functionality list - suggested additions - Incorporate Proposal 2 (new examples) as originally proposed in Option 2 into the definition of 'closed functionality'.
- 5. Issue 464: Suggest slight clarification of audience and outcomes - Incorporate the new sentence regarding developers and change "should" to "could", but not include "POUR" phrasing, as shown above in the minutes to the Background and Guidance sections.
- 6. Issue 463 (Issue answer): Programmatically determine the language of text - Answer Issue 463 using Option 2, as-is. (and as also posted above in the minutes).
-
22 August: WCAG2ICT Task Force Teleconference
- Question 1 - Update "virtual keyboard" definition's examples in the note - Merge in the changes to Note 1 of "virtual keyboard" - adjustments to the examples, as-is.
- Question 2 - Issue 437 (Add new note): Success Criterion Applying SC 2.4.2 Page Titled to Non-Web Documents and Software - Incorporate the alternative edit version (above) of the proposed Note to SC 2.4.2 Page Titled, as-is.
- Question 3 - Issue 437 (Issue answer): Success Criterion Applying SC 2.4.2 Page Titled to Non-Web Documents and Software - Answer Issue 437 as proposed above, making sure to substitute in the quoted note we added.
- Issue 464 (Add new note): Suggest slight clarification of audience and outcomes - Incorporate the changes from Option 2, as edited in the Google doc into the Guidance section and the change of "should" to "could" in the Background section.
- Question 5 - Issue 465 Part 1 (Addressing SCs 2.5.1, 2.5.2 and 2.5.7): Seeking clarity for key term 'underlying platform software' - No change to 2.5.1, 2.5.2 and 2.5.7 as a result of Issue 465.
-
15 August: WCAG2ICT Task Force Teleconference
- Question 6, Issue 431 – 2.5.2: An example has been inserted into a WCAG Note and not listed as a substitution - Move the example out of the note in SC 2.5.2 as demonstrated by Option 2 in PR 454.
- Question 4, Issue 419 – Definition of ‘style properties’ needs different word substitution - Update the definition of “user style sheets,” with the modifications as shown in Option 3 in the google doc (copied above in the minutes).
- Question 7, Issue 446 – Privacy considerations - Update the Privacy Considerations using Proposal 2 and Proposal 3 as-is.
- Question 8, Issue 446 – Proposed TF answer for a comment in the issue - Answer issue 446 as proposed in the Google doc, substituting the agreed text changes into the answer where noted.
- Question 1, Issue 397 – Key terms: “virtual keyboard” proposed rephrasing of examples - Issue 397: Make no changes to the note on "virtual keyboard" definition
- Question 2 - Issue 397 - Review proposed TF answer for a comment in the issue - Answer the issue stating the "virtual keyboard" definition's Note will not be changed and that we tried several iterations to attempt to reword. Provide some examples of what we tried in the answer.
-
8 August: WCAG2ICT Task Force Teleconference
- Question 3, Issue 414 – Issues with the ‘platform software’ notes for 2.5.1, 2.5.2, and 2.5.7 - Incorporate the changes to ‘platform software’ notes in 2.5.1, 2.5.2 and 2.5.7 using option 2, as-is.
- Question 5, Issue 428 – SC Problematic for Closed Functionality – add 3.2.6 Consistent Help - Incorporate the bullet for 3.2.6 Consistent Help into the SC problematic for closed functionality, as proposed.
-
18 July: WCAG2ICT Task Force Teleconference
- Issue 408 - Typo in 3.3.8 Accessible Authentication, Note 4 - Incorporate PR 442 as-is to remove “on”.
-
11 July: WCAG2ICT Task Force Teleconference
- Other open issues - Answer Issue 395 as proposed in the comment linked above.
- Issue 416 - The note should be removed for 'satisfies a success criterion' - Remove the note on "satisfies a success criterion" per issue 416.
- Issue 418 - Consider editing or removing the note for 'set of web pages' - Use proposal 1c above to replace the note in the definition of "set of web pages".
- Issue 423 - Definition of 'perimeter' should be removed - Remove guidance on the definition of "perimeter" and add that term to the section listing Level AAA terms.
- 20 June: WCAG2ICT Task Force Teleconference
-
14 June: WCAG2ICT Task Force Extra Friday Teleconference
- Issue 77: including WCAG supplements and Making Content Usable for People with Cognitive and Learning Disabilities - Incorporate Option 3 (the edited version of the COGA proposed content) into the Guidance in this Document, as-is.
- Issue 374: Focus Not Obscured needs a note for non-web software - Remove the note we added to 2.4.11 Focus Not Obscured from PR #378.
- Issue 374: Focus Not Obscured needs a note for non-web software - Answer Issue 374 with the text posted above in the minutes.
-
13 June: WCAG2ICT Task Force Teleconference
- Question 2 - (1 of 2) SC Problematic for Closed – 1.4.10 Reflow - Incorporate Option 3 for Note 5 into the general guidance section for 1.4.10 Reflow, as-is.
- Question 3: (2 of 2) General guidance for 1.4.10 Reflow – Note 7 proposed update to address Issue 377 - Incorporate Option 5 for Note 7 into the general guidance section for 1.4.10 Reflow, as-is.
- Question 4 – definition of key term “platform software” - Use option 5, as-is in the Google doc for the definition of "platform software"
- Question 1 – SC Problematic for Closed – 2.1.1 Keyboard - Incorporate Option 2, as-is for the SC Problematic for Closed - 2.1.1 Keyboard (as posted above in IRC)
-
6 June: WCAG2ICT Task Force Teleconference
- Question 1 – Update definition of “closed functionality” - Do not change the definition of “closed functionality”; leave as it is in the current editor’s draft.
- Question 2 - (1 of 2) SC Problematic for Closed – 1.4.10 Reflow - Incorporate proposal 5 for 1.4.10 Reflow into the SC Problematic for Closed Functionality section, as-is
-
30 May: WCAG2ICT Task Force Teleconference
- Question 2 - (2 of 3) Update to “closed functionality” examples - Update “closed functionality” examples using Option 3 from the survey, as is.
- Question 3 - (3 of 3) Move statement from Key term “closed functionality” to “Comments on Closed Functionality” - Move “closed functionality” cross-linking, using Option 2 from the survey, as-is
- Question 4 - (1 of 2) General Guidance – Note 8 of 1.4.10 Reflow - Update Note 8 of 1.4.10 Reflow using Option 2 from the survey, as-is.
- Question 5 – (2 of 2) General guidance – Note 1 for 2.1.1 Keyboard, and add “virtual keyboard” term - Update general guidance for 2.1.1 Keyboard and add the definition of “virtual keyboard” using Option 4 from the survey, as-is.
- Question 6 – (1 of 6) SC Problematic for Closed Functionality – intro and comments on closed sections changes - Update introductory content in SC Problematic for Closed Functionality and the Comments on Closed Functionality, using Option 3 from the survey, as-is
- Question 7 – (2 of 6) SC Problematic for Closed – 1.3.4 Orientation - Update the bullet for 1.3.4 Orientation in the SC Problematic for Closed Functionality using Option 5 from the survey, as-is.
- Question 13 – New proposed note for 2.4.11 Focus Not Obscured (Minimum) - Update the general guidance for 2.4.11 Focus Not Obscured (Minimum) using Option 3 from the survey, as-is.
- Question 12 – New proposed note for 3.3.8 Accessible Authentication (Minimum) - Update the general guidance for 3.3.8 Accessible Authentication (Minimum) using Option 7 from the Google doc, as-is.
- Question 11 – (6 of 6) SC Problematic for Closed – 3.3.1 Error Identification - Update the SC Problematic for closed – 3.3.1 Error Identification using Option 7 from the Google doc, as-is.
- Question 10 – (5 of 6) SC Problematic for Closed – 2.4.2 Page Titled - Update SC Problematic for Closed Functionality - 2.4.2 Page Titled using Option 3 from the survey, as-is.
-
16 May: WCAG2ICT Task Force Teleconference
- Survey results: Proposed editor's notes - Accept all of the proposed editor’s notes, as-is.
- Question (1 of 3) Guidance for 1.4.4 Resize Text due to Issue 4 - Remove Note 1 from 1.4.4 Resize Text.
- Question (2 of 3) Proposed changes to 1.4.4 Note 2 - Accept changes to 1.4.4 Resize Text Note 2, as-is.
- (3 of 3) Add new note to 1.4.4 Resize Text - Add new note from Proposal C, edited to use "text" instead of "content" to 1.4.4 Resize Text
- Question 4: Proposed edits to 1.4.10 Reflow content in SC Problematic for Closed Functionality - Incorporate Option 2, as edited (replacing two-directional with two-dimensional) for 1.4.10 Reflow into SC Problematic for Closed Functionality
- Question 5: Updates to guidance on 4.1.1 Parsing - Incorporate changes to 4.1.1 Parsing with the following edits: Add missing period on first bullet of note 4, changing phrasing in Note 3 to "and would be reported".
- Question 6 - Guidance for 2.4.11 Focus Note Obscured (Minimum) - Do not add the proposed new note to 2.4.11.
- Question 7 - Proposed update to 3.3.8 Accessible Authentication - Do not add newly proposed note to SC 3.3.8 Accessible Authentication.
- Question 8 - Edits to bullet in Comments on Conformance - Incorporate the proposed modifications to the 2nd sentence of Bullet 4 as-is into the Comments on Conformance section. Do not incorporate the additional sentence.
- Question 9 - Proposed change to 2.4.2 Page Titled content in SC Problematic for Closed - Accept change to 2.4.2 Page Titled as proposed in PR 352, as-is.
- Issue 257's response - Respond to issue 257 with reviewed response with minor edit proposed by Mike.
- Issue 221 Response - Respond to issue 221 as proposed, with the new text we approved today for the SC Problematic content for 1.4.10 Reflow substituted in.
- Response Issue 4 Point 6 - Answer point 6 in Issue 4 with proposed response, as-is.
- Response Issue 4 Point 6 - Approve the WCAG2ICT Document, once updated, to go to the AG WG to approve for publication
-
9 May: WCAG2ICT Task Force Teleconference
- Question (1 of 4) Point 3: SC 1.4.4 should require scaling to the extent supported by user settings of the platform - Use option 3, as edited in the Google doc with the “Addition to proposals” option 2B (in IRC above) as the response to Point 3 in Issue 4.
- Question (2 of 4) Points 4 & 5: Parts or all of the text is a sufficient size - Use Option 1 as the response to points 4 & 5 in the issue, as-is.
- Review: Proposed updates to Status of this Document - Accept the proposed edits to the SOTD in PR 344, as-is.
- Proposed answer to Issue 226 - Respond to Issue 226 using the proposed Option 2, with Bruce's and Olivia's edits shown in the Google doc.
-
2 May: WCAG2ICT Task Force Teleconference
- Question 1: Proposed updates to 5 SC that are applied to "sets of documents/software" - Incorporate proposal 3C in IRC above into the general guidance for the 5 SC that pertain to “sets of documents/software programs” with the editorial change.
- Question 2: Proposals for changes to the Guidance in this Document section - Incorporate the updated Proposal 3 (above in IRC), into the Guidance in this Document section.
- Question 3: Proposed changes to the introductory content in the SC Problematic for Closed Functionality section - Update the SC Problematic for closed functionality section using Proposal 4 with edits noted for consistency.
- 25 April: WCAG2ICT Task Force Teleconference
-
18 April: WCAG2ICT Task Force Teleconference
- 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: WCAG2ICT Task Force Teleconference
- 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.
- 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.
- Question 4: SC Problematic for Closed: 1.4.5 Images of Text - Incorporate Option 12 as shown in the meeting minutes.
-
4 April: WCAG2ICT Task Force Teleconference
- 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.
- 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
- 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: WCAG2ICT Task Force Teleconference
- Approve public comment responses - Issue 216 - Finalize the answer to issue 216, as-is.
- 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..
- 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: WCAG2ICT Task Force Teleconference
- 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, as well as the new note 3 for the general "Applying SC 2.1.2 No Keyboard Trap to Non-Web Documents and Software" section..
- 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).
- 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: WCAG2ICT Task Force Teleconference
- 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.
- (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.
- (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.
- (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: WCAG2ICT Task Force Teleconference
- 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.
- SC 4.1.3: Notes 1 and 2 - Incorporate Notes 1 and 2 for SC 4.1.3 as proposed in the survey.
- 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.
- 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".
- Issue 77 - Making content usable - Accept the changes and issue answer for Issue 77 as proposed in the survey.
-
15 February: WCAG2ICT Task Force Teleconference
- 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.
- SC 3.3.8: Note 4 - Incorporate Note 4 as proposed in the survey.
- 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
- 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: WCAG2ICT Task Force Teleconference
- 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.
- Issue 230 – 2.6 Software definition - Finalize the proposed answer to Issue 225 with the edit to add “Conclusion:” to the last paragraph.
- 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.
- 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: WCAG2ICT Task Force Teleconference
- Comments on Closed Functionality, definition of “closed functionality” - Incorporate PRs 306 and 307 for Comments on Closed Functionality and “closed products” definition updates.
- 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.
- 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).
- 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: WCAG2ICT Task Force Teleconference
- 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: WCAG2ICT Task Force Teleconference
- 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.
- 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.
- 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.
- 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: WCAG2ICT Task Force Teleconference
- 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
- 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.
- 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.
- 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".
2023
-
14 December: WCAG2ICT Task Force Teleconference
- 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: WCAG2ICT Task Force Teleconference
- Announcements - meeting next week 12/14
- Announcements - Next meeting after 12/14 is 1/4/2024
- 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: WCAG2ICT Task Force Teleconference
- 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”.
- 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: WCAG2ICT Task Force Teleconference
- 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.
- 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.
- Survey results: Updated proposal for 2.5.7 Dragging Movements - Add “dragging movements” term to the Glossary Items that Apply to All Technologies section.
- Survey results: Proposal(s) for 2.4.11 Focus Not Obscured (Minimum) - Incorporate proposal for 2.4.11 Focus Not Obscured (Minimum), as-is.
- 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.
- 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
- Question 1: New title for the section - Rename section to Comments on Closed Functionality
-
2 November: WCAG2ICT Task Force Teleconference
- 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.
- Survey results: Updated proposal for 4.1.1 Parsing - Remove bullet for 4.1.1 Parsing from the SC Problematic for Closed Functionality section
- Discussion on 1.4.4 Resize Text - Respond to point 1 with option 2, as edited above with dates fixed.
-
26 October: WCAG2ICT Task Force Teleconference
- Survey results: Proposed changes to definitions - Incorporate proposed changes for “satisfies a success criterion” as-is.
- Survey results: Proposed changes to definitions - Incorporate proposed changes for definition of “conformance” as-is.
- Survey results: Proposed changes to definitions - Incorporate proposed changes for definition of “structure”, with edit to remove “user”.
- 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.
- 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: WCAG2ICT Task Force Teleconference
- 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.
- 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.
- Definition of “menu-driven interface - Incorporate “menu-driven interface” definition, removing “easy-to-use” and "simple".
- 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: WCAG2ICT Task Force Teleconference
- Draft response to Issue 228 on 2.1 Accessibility Services of Platform Software - Send response for issue 228 as-is.
- Proposed change to guidance heading text - Change Guideline and principle headings as posted above.
- Proposed change to guidance heading text - Update the headings for the SC guidance using option 1 above.
- Proposed change to guidance heading text - update term definitions to be consistent such as "Applying “accessibility supported” to Non-Web Documents and Software"
- 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
- 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.
- 2.4.2 Page titled - Accept Option 2 for 2.4.2 Page Titled, as-is.
- 2.4.2 Page titled - Accept Option 2 for 2.4.2 Page Titled, as-is.
-
5 October: WCAG2ICT Task Force Teleconference
- 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.
- public comment on 1.4.12 Text Spacing - Send response with the addition in IRC above labeled "Add" and send.
- Survey Results: Review draft updates to SC Problematic for Closed Functionality - No bullet needed for 3.3.7 Redundant Entry in the SC Problematic for Closed Functionality section.
- Survey Results: Review draft updates to SC Problematic for Closed Functionality - Incorporate 3.3.7 Redundant Entry, using the alternate proposal in the survey, as-is (no word substitution).
-
21 September: WCAG2ICT Task Force Teleconference
- FPWD public comments - Additional email in response to Mary Jo’s email on 7 Sept. need no further response.
- 2.4.1 Bypass blocks - Update 2.4.1 Bypass Blocks bullet using Option 2 as shown in the minutes.
-
7 September: WCAG2ICT Task Force Teleconference
- FPWD public comments - Send response on kiosk comment received on 15 August, as updated with the additional comment.
- 1.4.13 Content on Hover or Focus - Update 1.4.13 Content on Hover or Focus - remove the bullet.
-
31 August: WCAG2ICT Task Force Teleconference
- 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.
- 1.4.12 Text Spacing - Update 1.4.12 Text spacing with option 3 above as-is.
-
24 August: WCAG2ICT Task Force Teleconference
- FPWD public comments - Send response on kiosk comment received on 15 August, as proposed in issue 215.
- 17 August: WCAG2ICT Task Force Teleconference
-
10 August: WCAG2ICT Task Force Teleconference
- 1.3.5 Identifying purpose - Update 1.3.5 bullet as edited above
- 1.4.2 Audio Control - Update 1.4.2 Audio Control bullet using Option 2 above
- 1.4.2 Audio Control - Update 1.4.3 and 1.4.11 bullets using text posted above
-
3 August: WCAG2ICT Task Force Teleconference
- Survey Results: Review proposal for key term “closed functionality” definition - Incorporate the key term “closed functionality” as proposed.
- Introduction - Use the drafted Introductory sentence, with the edits in Option 2, shown above.
- Non-text content - Use the drafted Introductory sentence Option 2 as-is, shown above.
- Audio-only and video-only - Incorporate 1.2.1 and 1.2.3 using option 3 above, as-is
- 1.3.4 Orientation - Update 1.3.4 Orientation bullet using Option 3 above
-
27 July: WCAG2ICT Task Force Teleconference
- CfC to publish the First Public Working Draft - WCAG2ICT TF supports the publishing of the FPWD
- Survey Results - Incorporate the proposed updates for the above list of SC as-is.
-
20 July: WCAG2ICT Task Force Teleconference
- Survey results: Review draft updates to Text / Command line / Terminal Emulator sections - Incorporate the introductory Text / CLI / Terminal Emulator content into the editor’s draft, with the edits and polls results above indicate.
- Survey results: Review draft updates to Text / Command line / Terminal Emulator sections - Incorporate the Background on Text / CLI / Terminal Emulators updates as-is into the editor’s draft, and capture proposed edits in Mitch’s GitHub content for a later update.
-
13 July: WCAG2ICT Task Force Teleconference
- 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.
- 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.
- 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.
- Survey results: Review of "set of web pages" definition - Incorporate Option 3, as is into the editor’s draft.
- Closed functionality survey - Add 1.4.10 Reflow bullet to the closed functionality section, as edited.
-
6 July: WCAG2ICT Task Force Teleconference
- Survey results: Review of proposals for SC 1.4.10 Reflow - Do not include additional examples.
- Survey results: Review of proposals for SC 1.4.10 Reflow - Incorporate combined proposal for Non-web documents Note 2, copied above.
- 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.
- 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)
- 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.
- Survey results: Review of proposals for SC 1.4.10 Reflow - Incorporate edited version of Note 2's 3rd bullet.
- Survey results: Review of proposals for SC 1.4.10 Reflow - Incorporate Note 3 using option 2 as-is
-
29 June: WCAG2ICT Task Force Teleconference
- 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.
- Survey results: Continue CSS Pixel definition draft review - Incorporate Note 2 with edits and the explanation of where 2688 came from, as shown above.
- Survey results: Continue CSS Pixel definition draft review - Incorporate Note 3 with Loic's changes to remove normative language.
-
22 June: WCAG2ICT Task Force Teleconference
- Survey results: Pixel definition draft review - Incorporate Note 1, as above, provided the examples given do approximate the CSS pixel for the given platforms.
- Survey results: Pixel definition draft review - Do not include note 2.
-
8 June: WCAG2ICT Task Force Teleconference
- 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.
- Survey results: 2.5.8 Target Size (Minimum) draft review - modify definition as stated above, replacing "page" with "content"
- Survey results: 2.5.8 Target Size (Minimum) draft review - we will remove the example above
- 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.
-
27 April: WCAG2ICT Task Force Teleconference
- Survey results and discussion on SC 2.5.1 Pointer Gestures - Incorporate 2.5.1 into the draft with Proposal 2 for non-web documents and Proposal 2 for non-web software.
-
6 April: WCAG2ICT Task Force Teleconference
- 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: WCAG2ICT
- 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.
- 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).
- 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: WCAG2ICT Task Force Teleconference
- 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.
- 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: WCAG2ICT Task Force Teleconference
- 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.
- 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: WCAG2ICT Task Force Teleconference
- 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.
- Survey WCAG2ICT-Abstract and Comparison sections readiness to incorporate into editor's draft - Incorporate the Comparison section as-is.
- Survey WCAG2ICT-Introductory sections' readiness to incorporate into editor's draft - use option 2 above and incorporate introduction sections into the draft
-
9 February: WCAG2ICT Task Force Teleconference
- 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: WCAG2ICT Task Force Teleconference
- 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: WCAG2ICT Task Force Teleconference
- 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.
2022
-
1 December: WCAG2ICT Task Force Teleconference
- 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: WCAG2ICT Task Force Teleconference
- 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.
- Final Poll results & discussion - Add a “Comparison to the 2013 WCAG2ICT Note“ section to the WCAG2ICT Note.
- Final Poll results & discussion - Do not add a Change log section to the WCAG2ICT Note.
-
27 October: WCAG2ICT Task Force Teleconference
- Naming / referencing conventions - Change to WCAG 2.0 to WCAG 2.2 throughout
-
6 October: WCAG2ICT Task Force Teleconference
- Questions 9. Patent Policy section - Accept Patent policy section.
- Question 2. Scope of Work section - The scope of ICT covered will remain in the note and not in the work statement.
- Whether to include AAA requirements - We will keep AAA in scope, keep it separate with WCAG's strong warning, and address later after A and AA are addressed.
- Whether to include AAA requirements - Agree to Scope section with any amendments in pull request 2682.
-
29 September: WCAG2ICT Task Force Teleconference
- Question 3. Approach section - Accept amended approach section
- Question 7. Participation section - Accept Timeline Section
- Question 7. Participation section - Accept Participation Section