This is an unpublished draft preview that might include content that is not yet approved. The published website is at w3.org/WAI/.

Accessibility Guidelines Working Group Meeting Resolutions

This page shows minutes of the Accessibility Guidelines Working Group. Minutes for task forces are available from their respective pages.

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.

Minutes | Topics | Resolutions

2025

4 February: AGWG Teleconference
- Silver Issues Ready To Close https://github.com/w3c/silver/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22survey%20%3A%20ready%20for%22 - Close Silver issues at https://github.com/w3c/silver/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22survey%20%3A%20ready%20for%22 as proposed
28 January: AGWG-2025-01-28
- Assertions and Best Practices https://github.com/w3c/wcag3/discussions/120#discussioncomment-11854616 - We agree to allow for "best practices", sub-groups will collect things that fit the approach, and we will review those and the terminology in a future meeting

2024

3 December: AGWG Teleconference
- WCAG 2.2 review of updates https://lists.w3.org/Archives/Public/public-wcag2-issues/2024Nov/0012.html - Approve PR 2858 to create an errata for Target Size Enhanced.
19 November: AGWG Teleconference
- Issue 2296 https://github.com/w3c/wcag/pull/2296/files - accept PR 2296 to update the Background section of WCAG 2.2 and 2.1
- WCAG3 - scope (to web) - Approval for merging the changes into the Editors draft in preparation for CFC for publication
12 November: AGWG-2024-11-12
- Discussion of Explainer w3c/wcag3#116 (comment) - Pending updates to Abstract, Explainer can go to CFC for publication.
22 October: AGWG Teleconference
- Requirements Publication w3c/wcag3#117 - Accept the suggestion to replace the current "Broad disability support"
15 October: AGWG Teleconference
- Discuss what to include for conformance in upcoming publications https://github.com/w3c/wcag3/discussions/121 - We will explore having a set of required provisions that is somewhat comparable to WCAG 2.2 A & AA and a set of provisions and assertions that can be used to build upon that through points, percentages, or predefined sets of provisions (modules).
1 October: AGWG-2024-09-30
- Deciding on outcome formatting - For the next publication, we will use "Outcome" (user-focused outcomes) to group the requirements and assertions. We will explore terminology for the requirement/assertion level in future.
10 September: AGWG Teleconference
- Terminology conversation https://github.com/w3c/wcag3/discussions/113#discussion-7138461 - Scope terminology 1. Item, 2. View, 3. Task Flow, 4. Product
27 August: AGWG Teleconference
- WCAG 3 Requirements updates https://github.com/w3c/wcag3/issues/44 - Move the Requirements updates to CFC.
25 June: AGWG-2024-06-25
- Introduce next steps in subgroups https://www.w3.org/2002/09/wbs/35422/subgroups-june-24/ - Publish the WCAG2ICT Draft Note for wide review from the Editor's Draft
11 June: AGWG Teleconference
- Conformance - What would a baseline include? - We progress with a baseline and make effort to make it even across functional needs. Prioritize requirements for safety, blockers and adaptation / author support for user agent features (within outcomes). Then another level (or two) which is scored, providing a means of progressing.
21 May: AGWG Teleconference
- 3.2.6 Consistent Help WCAG2ICT guidance - Approve issue 369
- Accessible Authentication (Minimum) WCAG2ICT guidance - Approve issue 368
- 4.1.1 Parsing WCAG2ICT guidance - Approve issue 364, with small amendments for wording on the WCAG errata/note
- Closed functionality - Approve issue 370
30 April: AGWG Teleconference
- Use of Color - Put Guidelines content in Editor's Draft following our standard procedures.
- Use of Color - Agree to have a Call for Consensus to move Guidelines content to Working Draft with additional wording to editors note about editor's note not being on specific items, additional research markings, removing the word "guidelines", and minor updates discussed in meeting.
23 April: AGWG Teleconference
- Introduce Outcomes Pull Request https://github.com/w3c/wcag3/pull/62 - Keep the audio-shifting outcome, and add "Important information is not presented in spatial audio alone." and "Important information does not require depth perception."
- Multi-step process - Keep multistep-process for now, and discuss further when we get to those outcomes.
12 March: AGWG Teleconference
- Next Publication - Updated Placeholder Guidelines and Outcomes https://github.com/w3c/wcag3/discussions/54 - We will bring a PR back to the group for the editors draft, then look at a refined update to the Working Draft.
27 February: AGWG Teleconference
- Structure with Examples https://docs.google.com/document/d/1tpgJaoIHC4IywvFkfXrfa8mEcSlEtAP-P0_46vNqynY/edit#heading=h.vc6kiqsxgozk - Explore options 2 and 3 for structure in the first subgroup and report back
13 February: AGWG Teleconference
- Outcome Language https://github.com/w3c/wcag3/discussions/49 - We will proceed with the "Technical Statement" for our first round of outcome work
23 January: AGWG-2024-01-23
- Decision about Publication Approach to WCAG 3 - Continue building on redesign effort (Silver, Outcomes, etc) as the way to create WCAG 3
- Decision about Publication Approach to WCAG 3 - Continue building on redesign effort (Silver, Outcomes, etc) as the way to create WCAG 3 (with objections)
16 January: AGWG Teleconference
- ACT-Rules Format 1.1 FPWD https://github.com/w3c/wcag/issues/3616 - Accept the updates to ACT Rules format 1.1

2023

31 October: AGWG-2023-10-31
- Adding why it is important to 2.1 SCs #3312 - Accept amended PR 3312 ("in brief")
- Adding why it is important to 2.1 SCs #3312 - Accept PR 3341 to address issue 3333
19 September: AGWG-2023-09-19
- Question 3 - Clarity for programmatically determined link context term example #3361 - Accept PR 3362 to address issue 3361
- Question 4 - Clarity around a "change initiated by the user" #3226 - Accept PR 3349 to address issue 3226
29 August: AGWG Teleconference
- WCAG 3 Issues - We will adopt the approach outlined in the document "Resolving WCAG 3 FPWD issues", closing them in favour new issues/discussions in the new repo
- Question 1 - Understanding for Contrast does not call out Color Blindness #2033 (take 3) - Accept PR 3284 to address issue 2033
- Question 2 - Update PDF techniques #3354 - accept amended PR 3354 to address updating PDF techniques.
- Question 3 - Use of Color Understanding doc: add note concerning same color case #3286 - Accept amended PR 3286 to address issue 1467
- Question 3 - Use of Color Understanding doc: add note concerning same color case #3286 - Accept PR 3277 to address issue 3187
22 August: AGWG Teleconference
- Question 1 - Understanding doc for 1.2.9 mentions video #1836 - Accept PR 1837 to address issue 1836.
- Question 2 - Non-text Contrast - Figure on background changes #2494 - Accept PR 2574 to address issue 2494
- Question 4 - Suggested improvement to Understanding 2.2.1: Timing Adjustable #1814 - Accept amended PR 3281 to address issue 1814.
25 July: AGWG Teleconference
- Question 1 - Success Criterion 1.4.10 Reflow - Accept amended SC 1.4.10 Reflow for WCAG2ICT wide review
- Question 2 - Success Criterion 1.4.11 Non-text Contrast - Accept SC 1.4.11 Non-text Contrast for WCAG2ICT wide review
- Question 3 - Success Criterion 2.5.1 Pointer Gestures - Accept SC 2.5.1 Pointer Gestures for WCAG2ICT wide review
- Question 4 - Success Criterion 4.1.3 Status Messages - Accept glossary term "style property" for WCAG2ICT wide review
- Question 5 - Glossary term: style property - Accept glossary term "style property" for WCAG2ICT wide review
- Question 6 - Glossary terms: "set of Web pages" and associated "set of" terms - Accept amended glossary terms "set of web pages" and associated "set of terms" for WCAG2ICT wide review
- Question 7 - Success Criterion 2.5.8 Target Size (Minimum) - Accept SC 2.5.8 Target Size (Minimum) for WCAG2ICT wide review and ask for comments and recommendations.
- WCAG2ICT Now what? - Take WCAG2ICT to pre-cfc, followed by CFC
18 July: AGWG Teleconference
- 4. Understanding doc for 1.2.9 mentions video #1836 - Adopt Understanding doc for 1.2.9 mentions video #1836 with change to audio conferencing.
- 5. Non-text Contrast - Figure on background changes #2494 - Accept PR 2574 to address issue 2494
- Adjustment to 'in brief' sections - Accept the new placement and structure of In Brief and work on emphasizing the SC
- Parsing update for WCAG 2.1 understanding #3280 - Accept Parsing update for WCAG 2.1 understanding #3280
11 July: AGWG Teleconference
- WCAG 2.x backlog issues https://www.w3.org/2002/09/wbs/35422/wcag2x-backlog1/ - Accept amended PR 3266 to update Focus-not-obscured note & understanding document.
- Understanding Focus Appearance CR3 updates #3259 - Accept PR 3259 for Focus Appearance CR3
27 June: AGWG Teleconference
- Question 3 - Separate techniques for Target Size #3231 - Accept amended PR 3231 to address issue 2433 and review in list
- Question 4 - Adding brief descriptions for all WCAG 2.0 A and AA requirements, understanding docs - Accept amended PR 3219 to add brief descriptions for all WCAG 2.0 A and AA requirements and review in list
20 June: AGWG Teleconference
- WCAG 2.x backlog issues https://www.w3.org/2002/09/wbs/35422/wcag2x-backlog1/results - Agree with using the W3C decision policy
- Is visited link color a failure of Use of Color? #905 - Accept PR 3222 with Bruce's editorial change, adjustment to clarify the difference between visited and unvisited links and file more issues if needed
13 June: SV_MEETING_TITLE
- Keep a custom decision policy or use the standard W3C approach - Further explore moving to the default W3C process next week
- Keep a custom decision policy or use the standard W3C approach - Further explore moving to the default W3C process next week
- C42 good for 2.5.5, not as example for 2.5.8 Target Size (Minimum) #2433 - Separate PR#3231 into two techniques and bring back for review.
- Add 'In brief' section at start of 2.1 SCs #3191 - Publish without the key beneficiaries, with the editorial changes suggested in the survey. Keep existing wording on "enlarging". Put in ticket to improve understanding document to include small viewports and other clarification. Revisit briefs with EO in the future.
6 June: AGWG Teleconference
- WCAG 2.x backlog issues, 7 questions https://www.w3.org/2002/09/wbs/35422/wcag2x-backlog1/ - Accept amended response to address issue 623, keep issue open and update appropriate understanding docs.
- Question 2 - How to work out 'three flashes' in modern terms - Accept PR 2127 which has already been merged and close issue 1132.
- Question 3 - Delete H45 (longdesc) #2502 - Accept PR 2503 to address issue 2502, create new issue/PR to remove longdesc in example from understanding conformance.
- Question 4 - Clarify 1.4.11 and 2.47 relationship in understanding doc #2146 - Accept PR 2146 to address issue 1385.
- Question 5 - Are browser/OS settings (prefers-* features) acceptable as a mechanism? #2909 - Accept response to address issue 2909.
- Question 6 - Mechanism provided by the platform AND stopping 1.4.2: Audio Control #1533 - Accept PR 2621 to address issue 1533.
- Question 7 - Does 1.3.1 apply to off screen content? #2520 - Update understanding document and response and review at a later date.
30 May: AGWG-2023-05-30
- WCAG 2.2 Issues, 1 question https://www.w3.org/2002/09/wbs/35422/wcag22-misc5/ - Add as informative, if there are disagreements, AGWG members can express in list when reviewing in list, and will review any disagreements in next call should any occur.
- WCAG 2.x backlog issues, 6 questions https://www.w3.org/2002/09/wbs/35422/wcag2x-backlog1/ - Accept amended PR 2827 to address issue 728.
- WCAG 2.x backlog issues, 6 questions https://www.w3.org/2002/09/wbs/35422/wcag2x-backlog1/ - Accept amended PR 1201 to address issue 1049.
- WCAG 2.x backlog issues, 6 questions https://www.w3.org/2002/09/wbs/35422/wcag2x-backlog1/ - Accept PR 1804 to address issues 1796, 1798, 1799, 1800, and 1801
- WCAG 2.x backlog issues, 6 questions https://www.w3.org/2002/09/wbs/35422/wcag2x-backlog1/ - Accept PR 1804 to address issues 1796, 1798, 1799, 1800, and 1801
23 May: AGWG Teleconference
- Does Target Size (Minimum) result in widespread failure of common dataviz? #3091 - Accept PR 3188 without change to limited motor control, create issues for 1) zoom recommendation and 2) one to discuss all functional needs across all issues in WCAG 2.2
- Accessible authentication - consider other phrase than one time password #3180 - Accept PR 3185 without Patrick's suggested edits, readdress additional edits outside of meeting as a new issue.
- Focus Not Obscured (Enhanced) should permit opaque overlays #3193 - Merge PR 3194 and PR 3195 with edits discussed in meeting and circulate by email for 2nd review.
- Clarification on 3.1.2 Language of Parts #297 - add code example, change content to "phrases, passages, and in some cases, words" and close issue. Open separate issue for examples
- 2.2.6: Timeouts - reference to compliance #421 - Accept PR 501. If someone finds a non-US example, please create new PR
- What is part of accname for Label in Name? #2302 #2276 - Continue to work on PR #2725 with Wilco and ACT's input
- Focus being set to the first interactive element in a dialog #2241 - Accept PR #2306, leave suggested change out
16 May: SV_MEETING_TITLE
- Failure technique for Focus-not-obscured - Accept failure technique with edits discussed in meeting and come back with update to cover the other SC
- Does 2.4.12 Focus not obscured encourage a keyboard anti-pattern #2809 - Accept PR 3163 and open new issue on lightbox and on substituting pointers.
- Changes/corrections to 1.4.3 and 1.4.6 understanding #3020 - Accept PR 3020 with a change to use a link to images of text instead of wording around required and open an issue about the challenges on contrast
- Inactive components in 1.4.3 & 1.4.6 Understanding #481 - Accept PR 3020 but open an issue examining inactive, disabled, and not available.
- 2.5.3 Label in Name - aria-hidden on part of visual label #2302 - Accept PR 2725 but request review from ACT before merging.
- Updating landmark techniques - Accept PRs 2435, 2338, 1269. Alastair will email update to list for additional review
9 May: AGWG-2023-05-09
- Question 1 - Rewrite technique C40 and associated example per discussion in #3026 - Accept amended PR 3112 to address issue 3026.
- Question 2 - Add 'In brief' section at start of 2.2 SCs #2905 - Accept PR 2905 to add an "in brief" section.
- Question 3 - G219 title for 2.5.7 Dragging Movement is misleading #3128 - Accept amended PR 3133 to address issue 3128.
- Question 4 - Rewrite OTP section in Accessible Authentication understanding #3150 - Accept amended PR 3150 to address issue 3095.
- Question 5 - Loophole in 2.5.8 Target Size (Minimum)? #3045 - Accept PR 3103 to address issue 3045 and 2755.
2 May: AGWG Teleconference
- WCAG 3 Editor and Working Drafts https://www.w3.org/2002/09/wbs/35422/working_draft_23/ - Approve moving the editor's draft content to the Working Draft
- WCAG 3 Editor and Working Drafts https://www.w3.org/2002/09/wbs/35422/working_draft_23/ - Approve moving the editor's draft content to the Working Draft
- 2.4.11 Focus Appearance exception doesn't match explanation #3016 - Address concern in #3016 in the understanding document
- Accessible Authentication failure techniques #1916 - Accept PR 2990 with comments addressed including resolving password inconsistency and circulate to group via email
25 April: AGWG Teleconference
- Adding references to cognitive SC - Accept PR 3146
- For 1.4.13 Content on Hover or Focus, note at bottom of Intent section should be moved up #3129 - Update the note and move to below the SC text
- 2.4.12 Focus not Obscured (Minimum) and user opened / controlled content #2751 - Accept PR #3083, Note 2 is updated by the text above
18 April: AGWG Teleconference
- Question 2 - Updating Editor Draft - Substantive Changes - Accept amended substantive changes to editors draft, and craft notes for further review by the group.
- Question 2 - Updating Editor Draft - Substantive Changes - Accept amended substantive changes to editors draft, and craft notes for further review by the group.
- WCAG 2 Wrap up all outstanding normative issues on WCAG 2.2 - Accept the focus appearance SC text, and review the understanding document, including what happens with individual buttons without comparitors
11 April: AGWG Teleconference
- WCAG2ICT Second Content Review Survey - Accept WCAG2ICT Content
- Does anyone have an issue with Moving Focus Visible back to AA? - Moving Focus Visible back to AA
- Add '(Minimum)' to the name of SC 3.3.8 Accessible Authentication #3087 - Add '(Minimum)' to the name of SC 3.3.8 Accessible Authentication #3087 to “Accessible Authentication (Minimum)”
- Programmatically Determined example describes outdated direct parsing of markup #3001 - Update the understanding document and bring proposal back to group. for Issue #3001
- Focus obscured understanding updates #3074 - Accept #3074 with slight wording changes
- Alignment of structure/wording of Target Size SCs #3086 - Resurvey this with the new wording and addressing the concern raised by Wilco regarding expanding the exception
- "Very similar" examples are actually "exactly the same" #2692 - Accept PR 3131
4 April: AGWG Teleconference
- WCAG 3 Review of revised conformance section survey https://www.w3.org/2002/09/wbs/35422/WCAG3_conformance_March_23/ - Accept that we are presenting pieces without a 'integrated whole', in order to further discussion with stakeholders.
- WCAG 3 Review of revised conformance section survey https://www.w3.org/2002/09/wbs/35422/WCAG3_conformance_March_23/ - Accept that we are presenting pieces without a 'integrated whole', in order to further discussion with stakeholders.
- Parsing note wording - Accept amended notes on 4.1.1 for WCAG 2.0 and WCAG 2.1
- Parsing note wording - Notes on 4.1.1 for WCAG 2.0 and 2.1 will not be used for WCAG 2.2
28 March: AGWG Teleconference
- 2.5.8 Target Size "overlapping any other target" does not work #3050 - Change the spacing exception language to proposed revision with an at risk option to fall back to existing (current CR) language
- 2.5.8 Target Size "overlapping any other target" does not work #3050 - Change the spacing exception language to proposed revision with an at risk option to fall back to existing (current CR) language, note that an objection raised about needing more time for review
- 2.5.8 Target Size "overlapping any other target" does not work #3050 - Change the spacing exception language to proposed revision with an at risk option to fall back to existing (current CR) language, note that an objection raised about needing more time for review
- 2.5.8 target size should not have a "lists" exception #3051 - Use "The target is in a sentence or its size is otherwise constrained by the line-height of non-target text; "
21 March: AGWG-2023-03-21
- WCAG 2.2 Focus appearance Survey: https://www.w3.org/2002/09/wbs/35422/focus-appearance/ - Move the SC to AAA
- WCAG 2.2 Focus appearance Survey: https://www.w3.org/2002/09/wbs/35422/focus-appearance/ - Explore removing the first part of the SC and strengthening the second part
- Question 1 - Review of Background section - Approve the amended background section of WCAG2ICT
- Question 2 - Success Criterion 1.3.4 Orientation - Approve the amended Success Criterion 1.3.4 Orientation guidance
- Question 3 - Success Criterion 1.3.5 Identify Input Purpose - Approve the amended Success Criterion 1.3.5 Identify Input Purpose guidance
- Question 3 - Success Criterion 1.3.5 Identify Input Purpose - Approve the amended Success Criterion 2.1.4 Character Key Shortcuts guidance
- Question 3 - Success Criterion 1.3.5 Identify Input Purpose - Approve the 2.5 Input Modalities guidance
- Question 3 - Success Criterion 1.3.5 Identify Input Purpose - Approve the amended Success Criterion 2.5.4 Motion Actuation guidance
7 March: AGWG Teleconference
- Announce: Upcoming schedule around CSUN - Continue to explore providing test files and sample code, provided by ARIA-AT, HTML5 and ACT within methods to support accessibility supported. Within that explore whether focusing on AT or the accessibility tree would need further discussion.
- Question 2 - Name of Test Types - Name of test types will be "Quantifiable"
- Question 3 - Accessibility Supported - Accept The editor's note on Accessibility Supported
- Question 1 - Does 2.4.12 Focus not obscured encourage a keyboard anti-pattern #2809 - Accept examples added in PR 3043, leave issue 2809 open
- Question 3 - One-time-passcodes and the test for when an activity requires 'transcription' #2866 - Accept amended PR 3046 and PR 2618 and leave issue 2866 open
- Question 4 - Target size - "in vertically set text" #2996 - Accept PR 3047 to address issue 2996.
- Question 5 - Programmatically Determined example describes outdated direct parsing of markup #3001 - Remove the SC text and leave a note (as 2.2 does), we will CFC before 2.2 goes to PR
28 February: (MEETING TITLE)
- 1. Suggest more structure to Intent section of 3.3.7 Understanding article #2650 - Accept PR 2988 with adjustments from mbgower, double-check that it answers issue 2650
- 1. Suggest more structure to Intent section of 3.3.7 Understanding article #2650 - Accept PR 2988 with adjustments from mbgower, double-check that it answers issue 2650
- 3. Example Could Be Replaced with an Example that Encourages Greater Equity #2550 - Accept PR #2753 with amendment to link to taskboard / kanban explanation.
- 4. Focus not obscured margin technique and working example #2746 - Accept PR #2746 with proposed amends to be done.
- 5. What are the user's solutions of Focus Not Obscured (minimum)? #2700 - Accept Detlev's response to the question, as amended.
- 6. Clarification sought on "set of web pages" #2298 - Accept PR #3008 and add as errata to 2.0 and 2.1
- 7. Dragging Movements - Carousels - Overflowed Containers #2684 - Accept PR 3040 and close issue 2684
- 8. Update focus-appearance - Accept PR 3017
21 February: AGWG Teleconference
- Removing all guidelines but exemplars - Remove all guidelines except exemplars
- Removing all guidelines but exemplars - Use Clear Language and Error Prevention as examplars, and add in a more common exemplar if there is time and people to work on it. We will revisit how best to get the targeted public review on conformance including equity.
- Google - Success Criterion 2.5.8 Target Size Minimum (AA) #2704 - Accept #2972 as amended above
- Google - Success Criterion 2.5.8 Target Size Minimum (AA) #2704 - Accept changes to #2704
- Definition of target offset returns wrong results #2973 - Alastair to update and send to email list for final review. If no objections, approve closing issue #2973
- Target offset can be determined only with complicated mathematical methods #2974 - Accept #2974
- 2.5.8 Target Size (Minimum) is ambiguous for non-rectangular targets #2803 - Accept #2803 with skewed example removed and as amended. Wilco's issue will be addressed later.
- Private Access Tokens will impact whether or not Captchas will be needed to be done #2524 - Accept #2524
14 February: AGWG Teleconference
- Question 2 - Subtle grammar issue in 3.2.6 #2688 - Accept PR 2735 to address issue 2688
- Question 5 - Dragging Movements needs some attention #1917 - Accept PR 2999 to address issue 1917
- Question 1 - Benefit text + Examples Understanding 3.2.6 Consistent Help not the right fit anymore?! #2414 - Accept amended PR 2998 to address issue 2414
- Question 3 - 2.5.8 Target Size (Minimum) understanding doc #2431 - Accept amended PR 3012 to address issues 2431, 2429 and 2432.
- Question 4 - Expect difference in Sufficient Techniques 3.3.7. and 3.3.8, at least one #2378 - Accept amended PR 2997 to address issue 2378
- Question 6 - Add "failure" to Understanding 2.4.12 Focus Not obscured #2418 - Accept amended PR 3009 technique to address issue 2418
7 February: AGWG Teleconference
- agenda+ WCAG 3 Review Test Section Editor’s Draft Survey: https://www.w3.org/2002/09/wbs/35422/updated_editor_draft/ - Agree to move the Testing section to "developmental", with an editorial update for the conditions examples and a new editor's note to allow exploration of multiple measures in addition
- agenda+ WCAG 3 Review Test Section Editor’s Draft Survey: https://www.w3.org/2002/09/wbs/35422/updated_editor_draft/ - Agree to move the Testing section to "developmental", with an editorial update for the conditions examples and a new editor's note to allow exploration of multiple measures in addition
- 2.4.11 text-decoration as focus indication for links #2679 - Approve PR 2772, and closing issue 2679
- Google - Success Criterion 2.4.11 Focus Appearance (Level AA) #2706 - Agree with the response for #2706
- Google - Success Criterion 3.3.7 Accessible Authentication (Level AA) #2707 - Agree PR 2811 and close #2707
- Google - Success Criterion 3.3.8 Accessible Authentication (Level AAA) #2708 - Agree to accept response to #2708
- Success Criterion 3.2.6 Consistent Help (Level A) #2709 - Agree to response for #2709
- Success Criterion 2.4.12 Focus Not Obscured (Level AA) #2710 - Agree to response for ##2710
- Google - Success Criterion 2.4.13 Focus Not Obscured (Level AAA) #2711 - Accept response for #2711
- Accessible Authentication disallows Security questions #2733 - Accept response to #2733
31 January: AGWG Teleconference
- Success Criterion 2.5.7 Dragging Movements (Level AA) #2705 - Accept PR #2705 with edits to address Wilco and Gundala’s comments
- Add "entirely" to Example 2.4.12: Focus Not obscured #2423 - Accept PR 2802 with edits discussed in meeting
- Accessibility vs Security again #2702 - Accept PR 2702 with a clarification that this SC does not include an essential security exception.
- Privacy considerations for redundant entry #2615 - Accept PR 2615
- Accessible Authentication needs better techniques #1916 - Accept PR #2920 with the addition of step 2 about pasting
- Last Benefit 3.2.6: Consistent Help not for this SC #2413 - Accept PR 2919 and circle back about chatbot
- Adding an "in brief" at the start of SCs - Add “in brief” section at the start of SC with specific content will be reviewed in the future. Style to stand out in the future. Add quotes under benefits section and link to WAI resource
24 January: AGWG Teleconference
- Pull Request from Test Types Subgroup https://www.w3.org/2002/09/wbs/35422/PR_Test_Types/ - Amend PR 666 and merge as exploratory
- Assertions https://www.w3.org/2002/09/wbs/35422/assertions-jan-12/ - Accept the new Assertions content as exploratory, acknowledging that the "what is a procedure" needs further definition.
- Question 1 - 2.5.8: Are all slider variants excluded or only sliders that look and are operated like sliders #2713 - Accept PR 2718 to address issue 2713.
17 January: AG teleconference
- Assertions https://www.w3.org/2002/09/wbs/35422/assertions-jan-12/ - Limit the documentation required to information about the assertion itself. Recommend that organizations maintain documentation on the assertions.
- Level Assertions Apply - Bronze level would be where most 'outcome' based requirements will go, but we are not ruling out some assertions going at bronze level
10 January: AGWG-2023-01-10
- Question 1 - New Rule: HTML page title is descriptive - Accept amended rule "HTML page title is descriptive
- Question 2 - New Rule: Image accessible name is descriptive - Accept amended rule "Image accessible name is descriptive"
- Question 6 - Streamline ARIA rule approval process - Grant standing approval to publish ARIA-specific ACT Rules, once approved by the ARIA Working Group, with the resulting rules distributed to the AGWG list
- Question 6 - Streamline ARIA rule approval process - AGWG grants ACT Task force amended standing permission to publish ARIA-specific rules as "approved" (posted to list and if concerns exist AGWG can comment)

2022

13 December: AGWG Teleconference
- New Rule Menu item has non-empty accessible name - Accept New Rule Menu item has non-empty accessible name, Wilco to bring back “” question to ACT for review and decision
- Update currently approved rules - accept New Rule: Iframe with interactive elements is not excluded from tab-order
- WCAG 2.2 https://www.w3.org/2002/09/wbs/35422/wcag22-misc-normative/results - Update rules approved today
- Removal or mark obsolete for 4.1.1 - Remove 4.1.1 in 2.2 and add note
29 November: AGWG Teleconference
- Initial equity group report (15 minutes) - group will continue to work for another 4 meetings and outbrief AGWG
22 November: AGWG-2022-11-22
- Evaluating Procedures - Accept amended PR 653 and merge with 2 notes to address the need for the definitions and to replace the examples long term (next update) with Coga's
- Evaluating Procedures - Accept amended PR 653 and merge with 2 notes to address the need for the definitions and to replace the examples long term (next update) with Coga's
- Question 3 - Removing 4.1.1 Parsing from WCAG 2.2 - Accept amended PR 2797 to remove 4.1.1 Parsing from WCAG 2.2.
- Question 4 - Focus Not Obscured (minimum) should not prohibit cookie popups #2551 - Accept amended PR 2611 to address issue 2551
- Question 6 - How does 2.4.12: Focus Not Obscured relate to opacity #2583 - Accept amended PR 2671 to address issue 2583
- Question 7 - An attempt to simplify/clarify 2.4.11 Focus Appearance #2687 - Accept proposed response to address issue 2687 and perform Wilco's proposed research in parallel.
- Question 8 - SC 2.4.11 "Focus Appearance" on WCAG 2.2 Candidate Recommendation #2689 - Accept proposed response to address issue 2689
- Question 9 - 2.5.8: Are all slider variants excluded or only sliders that look and are operated like sliders #2713 - Accept amended PR 2718 to address issue 2713
15 November: AGWG Teleconference
- Question 2 - Dragging movement definition might be improved #2669 - Accept PR2770 to address issue 2669
- Question 3 - Does 3.2.6 Consistent Help allow for content that is under disclosure widget on one page in a set but not another? #2303 - Accept amended PR 2612 to address issue 2303.
- Question 4 - Change definition and add parts to NOTE for "target offset" #2427 - Accept PR 2778 to address issue 2427.
- Question 6 - Accessible Auth understanding update #2355 - Accept amended PR 2391 to address issue 2355.
8 November: AGWG Teleconference
- Fall and Winter breaks https://www.w3.org/2002/09/wbs/35422/winter_break_22/results - Meet November 22 and 29th
- CSUN meeting https://www.csun.edu/cod/conference/sessions/ - Hold a hybrid meeting at CSUN on Monday March 13th
- Can adjectival be used at the test/method level with acceptable reliability? - No decision on adjectival ratings, need to prototype and request examples
- Adaptive requirements - We will try the following, acknowledging it may not work: Place parameters around scoring and how it should be done, address cumulative occurrences within outcomes instead of as part of scoring, require a perfect score at base level of conformance, continue to explore whether/how WCAG should use scoring in higher levels of conformance and for quality improvement.
- Adaptive requirements - Wait to make a decision on adaptive requirements until the subgroup creating prototypes comes back.
- Extensibility - Wait to make a decision on extensible requirements until the subgroup creating prototypes comes back.
25 October: AGWG Teleconference
- PR to Decision policy - Add PR 2739 with revisions and slight rewording of first sentence
18 October: AGWG Teleconference
- Review WCAG2ICT Work Statement https://www.w3.org/2002/09/wbs/35422/WCAG2ICT_Work_Statement/ - Approve the WCAG2ICT Work Statement (Work Statement will then go to CfC)
27 September: AGWG Teleconference
- Issue Severity Survey https://www.w3.org/2002/09/wbs/35422/issue-severity-post-tpac/ - Accept PR 661 (addition to the guidelines), with Gundula's additional point
- Issue Severity Survey https://www.w3.org/2002/09/wbs/35422/issue-severity-post-tpac/ - Accept PR 656, for the updates to methods, but removing the updates to the Requirements document
- ACT Survey https://www.w3.org/2002/09/wbs/35422/act-agwg-sept-2022b/ - Accept new rule - Object element rendering non-text content has non-empty accessible name
- Line height in style attributes is not !important - Accept rule "Line height in style attributes is not !important", ACT will look at the titles of all similar rules.
- New Rule: HTML graphics contain no text - Revisit 'expectations' section on this rule.
- Meta element has no refresh delay - Accept new rule - Meta element has no refresh delay
- - Accept new rule - Meta viewport allows for zoom
- Element with aria-hidden has no content in sequential focus navigation - Accept new rule - Element with aria-hidden has no content in sequential focus navigation. Add example for svgs inside of links.
- Equity Survey https://www.w3.org/2002/09/wbs/35422/equity-post-tpac/ - Accept PR 654 (https://github.com/w3c/silver/pull/654/files)
15 September: AGWG Teleconference
- Architecture - Set up a subgroup post TPAC to iterate style and how the documents link to each other. IA rework at a future time
- Is this too complex or are we working through complexity that we can later simplify? - Set up a subgroup to prototype the test matrix (slide 17) as methods and tests
13 September: AGWG Teleconference
- Issue severity presentation https://docs.google.com/presentation/d/1agb_XbMzroRtbscmDIMH1BxqZgDdWymqoxvLESN1LJA/edit#slide=id.p - Keep working on Accessibility Supported, discuss approach soon.
12 September: AGWG Teleconference
- Test Survey and Discussion https://www.w3.org/2002/09/wbs/35422/test-types/results - Move content into exploratory with edits from MaryJo and text that clarifies the confusion point from Gundula.
- Equity presentation https://docs.google.com/presentation/d/1H1UQshlV6MJqPiOYDlus1J-NuoRCP3JFTc74c12NBnI/edit#slide=id.p - Set up a temporary group under AGWG but separate from WCAG 3, to provide objective evaluation of wcag 3 equity decisions and also look into what type of group/process is needed to improve equity within AGWG and in a broader scope outside of AG
6 September: AGWG Teleconference
- Aligning the user-agent exception - Accept PR #2657 as an editorial update
- Is 'sometimes' accurate? #2305 - Use "Web pages that will later have additional content added can use a 'statement of partial conformance."
- Privacy considerations re: redundant entry #2615 - Use "Web pages that will later have additional content added can use a 'statement of partial conformance."
- Focus Visible should also apply when there is only one control #2653 - Accept PR2653
- WCAG 2.x Task Force - Group agreement for the need for a WCAG 2.x taskforce. Create a statement of work for a WCAG 2.x Taskforce with an end date to match the charter.
- Updating old links / references - Editorial updates in 2.x documents need an email to the group notifying of change with enough time to review and comment. Details to be determined and documented.
- Clarifying in the understanding - Clarifying updates in 2.x documents need a survey to the group with enough time to review and comment. Details to be determined and documented.
- Clarifying in the understanding - no addition of privacy language and continue to explore updating the understanding
23 August: AGWG Teleconference
- Question 1 - User agents pt2 - Leae the user-agents exception(s) unchanged, and move the current state forward to CR
- Question 1 - User agents pt2 - Leae the user-agents exception(s) unchanged, and move the current state forward to CR
- Question 3 - Making sub-components require focus indicators - Accept amended PR 2625.
- Question 4 - Tweaks to improve inter-rate reliability #2568 - Accept PR 2568
16 August: AGWG Teleconference
- Question 1 - Approve changes from previous meeting - Accept PR 2567 and create an errata for WCAG 2.1/2.0 for the note update
- Question 2 - Update to the red-flash note on general flash and red flash thresholds - Accept PR 2619 with the changed paragraph and the rest of the calculation goes into the understanding document. We come back with a change of L to Y later
- Question 3 - Problems with WCAG 2.0 Flash Definition #553 - Accept PR 2591 as an errata for WCAG 2.1/2.0 (and include in 2.2)
- Question 1 - Updating the publication of WCAG 2.1 - Re-publish WCAG 2.1 to include the errata
- Question 2 - Target definition: Change touch target to just target #1485 - Remove "touch" from the definition of target and remove touch from understanding as an errata for WCAG 2.1
- Question 3 - Expand/clarify "single pointer" definition #809 - Accept PR 809 as an errata for WCAG 2.1
- Question 4 - Consistency: "Resize text" > "Resize Text" #1941 - Accept PR 1941 as an errata for WCAG 2.1
- Question 5 - Rewording of normative text for 1.4.2 Audio Control #1825 - Errata not agreed, but happy to look at understanding doc updates.
- Question 3 - Persistent indicators - Change wording to "When the keyboard focus indicator is visible..." and ensure the understanding docs for 2.4.7 and 2.4.11 clarify that the focus remains persistent
- Question 5 - Complexity - Continue with the SC at risk (we will address the other survey questions via email and meetings and address objections through W3C process)
9 August: AGWG Teleconference
- Note 1 - Keep existing 75-85 ppi and change in WCAG 3, add clarification and explanation to understanding
- Note 1 - accept: "These calculations use the more conservative resolution of 75-85 ppi, which is lower than the nominal CSS pixel resolution of 96 ppi in CSS
- New Note A - Add note to draft understanding document for further discussion and full approval
- New note B - Add the Note B to understanding
- Note C - Add note C to understanding
2 August: AGWG 2 August 2022
- Add "Evaluating Procedures" Proposal into testing section (replacing procedures) as Exploratory - Add as exploratory but bring it back in 3 weeks with updates to terminology and the editor's note
19 July: AGWG-2022-07-18
- Charter: Decision policy https://www.w3.org/2002/09/wbs/35422/charter_July_22/ - Accept the amended draft decision policy, and move forward to CfC.
- WCAG 3: Natural Language How To https://www.w3.org/2002/09/wbs/35422/2022-07-14-WCAG3-Natural-Language-Howto/ - Accept moving Change of natural language how-to to exploratory
12 July: AGWG Teleconference
- Preferred starting point - The sub-group will draft initial text for the editor's draft for each proposal (separately).
14 June: AGWG Teleconference
- WCAG2ICT https://www.w3.org/2002/09/wbs/35422/WCAG2ICTV2/ - AGWG agrees to CfC the formation of a WCAG2ICT Task Force, TF will continue work on requirements doc for later approval by AGWG
- WCAG Editor's Draft Filter https://www.w3.org/2002/09/wbs/35422/filter/ - Expand the filter by default, add instructions on operation, continue working on options for later implementation with input from COGA, clearly mark sections to indicate where the content is within the process
- Question 1 - Add Changes to Natural Language Outcome as Exploratory - Accept amended name and changes to "Natural Language of Text" and add as Exploratory
- Question 2 - Add HTML lang attribute indicates the language of text Method - Add amended HTML lang attribute indicates the language of text Method as exploratory
7 June: 7 June 2022 AG Meeting
- WCAG 3 Placeholder for User Agents and AT https://www.w3.org/2002/09/wbs/35422/accessibility_supported_placeholder/results - Placeholder. We will be exploring this topic in future drafts. If you have input, please [chairs will figure this out]
- WCAG 3 Placeholder for User Agents and AT https://www.w3.org/2002/09/wbs/35422/accessibility_supported_placeholder/results - Add Placeholder text for User agents and AT
- New rule: SVG element with explicit role has non-empty accessible name - Accept new rule: SVG element with explicit role has non-empty accessible name
- New Rule: headers attribute specified on a cell refers to cells in the same table element - accept New Rule: headers attribute specified on a cell refers to cells in the same table element but add new example per Mary Jo's comment and run by Mary Jo and Gregg
- Update Approved ACT Rules - Accept Update Approved ACT Rules with Wilco's edits to fix Mary Jo's editorial concerns
- Does a Technique G219 example fail Pointer Gestures? #2248 - Accept PR 2356
- Dragging Movements needs some attention #1917 - accept Continuing with Dragging and update the understanding document to include that it is not widely supported by operating systems but when it is, that can be used to meet this.
31 May: AGWG Teleconference
- Removing guideline details and support materials - Approve, as amended today, the Maturity table, the editor's note process, and removing guideline details and support materials
- WCAG 2.2 Focus appearance https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced2/ - Approve the ACT Test Tools & Methodology Matrix, with some editorial changes to be applied (links and focus-handling)
- Separate WCAG Rules from Other ACT Rules - Separate WCAG Rules from Other ACT Rules, we will come back to the pre-amble / text explanations.
- Separate WCAG Rules from Other ACT Rules - Update ACT Rules Common Input Aspects
- Re-structure of bullets - Change "Except when" to "Exceptions"
- Re-structure of bullets - Change "can" to "may" in the last sentence
- Re-structure of bullets - Accept the structure update to focus appearance demonstrated in https://raw.githack.com/w3c/wcag/focus-appearance-structure/understanding/22/focus-appearance.html
- Re-structure of bullets - Move the last paragraph to above the exceptions.
24 May: AGWG Teleconference
- Question 1 - Approval to add testing section to editor's draft as exploratory - Approve adding testing section to editor's draft as exploratory with suggested changes or concerns in a note.
- Question 1 - Update Focus Appearance Enhanced and split Focus Not Obscured #2365 - Remove the last bullet of the exception because the 2px thickness makes it redundant
- Question 1 - Update Focus Appearance Enhanced and split Focus Not Obscured #2365 - Do not have an AAA version for this SC
17 May: SV_MEETING_TITLE
- Page break locators - Understanding doc scope update #2350 - Accept updated understanding per PR 2366 with GN's correction
- Are online word processing and slide applications in scope #2274 - Accept response, Alastair will wrap it up at the end of the thread.
- Multiple overlapping elements interact oddly with offset #2159 - Accept the response and changes but trop the “Targets other than A and B…” Change the sentence to “sizes of these targets differ.”
- Resolving 'common' objects #2386 - No change to current wording from this proposal. Anyone who has proposed alternate wording, submit against issue for consideration.
- Resolving 'common' objects #2386 - Approve PR 2386 to remove the word Common
- Update Focus Appearance Enhanced and split Focus Not Obscured #2365 https://usercontent.irccloud-cdn.com/file/Y7Y2K3Bt/image.png - Approve splitting apart the SC, resolutions on details to follow
- Update Focus Appearance Enhanced and split Focus Not Obscured #2365 https://usercontent.irccloud-cdn.com/file/Y7Y2K3Bt/image.png - Leave in the exceptions
- Update Focus Appearance Enhanced and split Focus Not Obscured #2365 https://usercontent.irccloud-cdn.com/file/Y7Y2K3Bt/image.png - Change the first bullet to "Encloses the visual presentation of the user interface component and is no thinner than 2 CSS pixels".
3 May: AGWG-2022-05-03
- Question 1 - Adjacent contrast - Accept normative change of PR 2341 to address issue 2333.
- Question 3 - Bounding box for separated links #2323 - Update the normative change to the SC, do not accept the changes to definition
- Question 1 - SC2.4.13 Page break locators technique #1226 - Accept amended PR 2130 to address issue 1226.
- Question 2 - Are CSS break-before/after indicators page break locators? #2259 - reject the proposed definition change
26 April: (MEETING TITLE)
- Should we leave in critical errors? - Remove ratings, critical errors, and scorings. Add editor's note similar to Critical errors was introduced as a concept in the FPWD. Although it not currently included, AGWG intends to re-asses this concept in the future.
- Should we leave in critical errors? - Remove ratings, critical errors, and scorings. Add editor's note similar to Critical errors was introduced as a concept in the FPWD. Although it not currently included, AGWG intends to re-asses this concept in the future.
- What are outstanding questions on the new approach? - Accept new questions in the survey, accept editorial content from the survey, add an outstanding question of whether to use "test" or "evaluation", add a question of "How tolerant are we of we of subjective tests and Should any test be not objective?
- Pursue or remove - We will try one last time but if no quick consensus next week, we will drop for 2.2
- bounding box defintion - GN will create an issue for the bounding box definition
- Against adjacent colors - Accept the understanding document update and survey Adjacent Colors, normative change of word "instead", and exception language (assuming we haven't surveyed them recently, if surveyed recently it will move to an issue)
19 April: AGWG Teleconference
- Out-of-viewport content #2204 - Accept response https://github.com/w3c/wcag/issues/2204#issuecomment-1096984939
- Updated understanding document for "encloses" - Approve the change to use "Encloses" and "adjacent colors" in the SC text.
- Updated understanding document for "encloses" - Approve the proposed update for "Minimum bounding box" definition.
- Updated understanding document for "encloses" - Include the proposed note on using declared values, on line 44 of the diff.
12 April: AGWG-2022-04-12
- Question 2 - Replace "encompasses" with "encloses" - Replace "encompasses" with "encloses" for Focus Appearance
5 April: AGWG Teleconference
- Risk of not pursuing WCAG 3 - Continue working on WCAG 3
29 March: AGWG Teleconference
- WCAG 2.2 Visual Controls https://www.w3.org/2002/09/wbs/35422/wcag22-visible-controls/ - Accept response and PR
22 March: AGWG Teleconference
- User Interface Component (UIC) measure as visual basis - Accept the visual display of the UIC as part of the assessment for Focus Appearance, with 1 objection that visual is not the correct approach
- User Interface Component (UIC) measure as visual basis - Accept the visual display of the UIC as part of the assessment for Focus Appearance
- Note on sub-components / active descendants - Add Wilco's text previously discussed into the SC text
- Not including the 1px perimiter metric - Add the 1px perimeter metric to the exception
- Definition of Encompasses - Accept shorter definition with 1 objection and a concern about handling focus on the whole page
8 March: AGWG-2022-03-08
- ACT Update (Wilco) - Approve the ACT update to go to CFC if there are no objections via email
- WCAG 3 Requirements Survey https://www.w3.org/2002/09/wbs/35422/WCAG3_requirements/ - Alastair will refine the question and pose the updated question to the group for later review.
- Question 2 - Revising true/false statement - Review existing PR and review proposed response later.
1 March: AGWG Teleconference
- WCAG 3 Protocols and Scoping Next Steps https://docs.google.com/presentation/d/1b5xHQWBzoYdKp7BfPgIUBCpz-yaDOx_kSq_HlQxcFh0/ - Group agrees to explore this direction, working on the next steps from the presentation
- Examples provided are not enough #1443 - Accept PR 2200
- Explicitly say that this mechanism is visible #2072 - Accept response to #2072
22 February: AGWG Teleconference
- Focus appearance and User-agents, again - Move forward with SC with an exception in the principle of "The focus indicator and its background color are determined by the user agent and are not modified by the author." or "The focus indicator is defined by the user-agent and cannot be adjusted by the author."
15 February: AGWG Teleconference
- 1. Status Level Names - Accept status level names
- 1. Status Level Names - Accept the levels assigned to the working draft
8 February: AGWG-2022-02-08
- Question 1 - 2.1 Readable - Discuss the intent, and revisit a response later.
- Question 2 - 2.2 Measurable Guidance - Suggest update as drafted in IRC and bring proposal back to Silver for wordsmithing in that taskforce.
- Question 1 - Change of context definition - Accept PR 1765 as an errata to alter the "Change of Context" definition
- Question 2 - Visible Controls clarifications and a user-agent example #1905 - Accept amended response to address issue 1905
1 February: AG teleconference
- Conflicting Goals #484 - Change repsonse to language at 11:20, detlev to add his comment to github issue
- Introduction: Explain how to solve Issue #41 - accept amended PR and revisit larger issue after Jake has proposed wording
- Recommended viewport size for testing? #1829 - Approve revised wording from 23 after the hour.
25 January: AGWG Teleconference
- WCAG 3 Requirements https://www.w3.org/2002/09/wbs/35422/WCAG3_requirements/ - Accept amended PR #586
- Scope of Guidelines #326 - Accept Rachael's response to address issue 326
18 January: AGWG Teleconference
- Question 1 - 380 - Question on Clear Words Revised - Accept amended response to address issue 380, and tag with input-for-future-version
- Question 2 - 169 - Consider "accessible name" instead of "alternative text" - Accept Alastair's response to address issue 169 and send back to the team working on text alternatives for additional review
- Question 2 - 169 - Consider "accessible name" instead of "alternative text" - Accept Alastair's response to address issue 169 and send back to the team working on text alternatives for additional review
- Question 3 - 257- Meaningful Text Alternatives - Return the issue to the team working on the response, and consider an adjective, and consider separating requirements.
- Question 4 - 457 - ITI Comments on flexible conformance - Accept amended responses to address issue 457, and tag issue as input-for-refinement
- Question 4 - 457 - ITI Comments on flexible conformance - Accept amended responses to address issue 457, and tag issue as input-for-refinement
- Size basis for focus-appearance - Carry on with the current approach, focused on 'component', tweaking the SC text to make clearer the basis for size.
11 January: SV_MEETING_TITLE
- Announcements and Reminders - revisit this when we move into CR or 3 months, whichever comes first
- Announcements and Reminders - revisit this when we move into CR or 3 months, whichever comes first
- Focus Appearance complexity #1842 - Accept note as ammende and survey AWK's suggestion with last bullet back in next week
4 January: AGWG-2022-01-04
- Question 1 - 256 - Clear Words vs Plain Language - Accept the amended response to address issue 256
- Question 2 - 359 - Measuring words question - Accept the amended response to address issue 359
- Question 1 - “Conformance Criterion” instead of “Conformance Requirement” used in the WCAG 2.1 Glossary #1758 - Address issue 1758 by amending and updating PR for WCAG 2.2 and include an errata in 2.1
- Question 2 - Incomplete/no techniques #1813 - Accept PR 2131 to address issue 1813
- Question 3 - Problems with WCAG 2.0 Flash Definition #553 - Accept amended PR 2127 to address issue 553 and 585

2021

21 December: AGWG-2021-12-21
- WCAG 2.2 Page break navigation (Q1 only) https://www.w3.org/2002/09/wbs/35422/wcag22-page-break-nav/ - Accept PR 2160 to address issue 2155, there will still be conversations regarding keeping or dropping this sc.
- Question 1 - Focus appearance and user-agents - Carry on with the SC as it is and provide guidance in understandings that browsers can fulfill the SC if you test it, with 1 objection requesting including a default indication. C
- Question 1 - Focus appearance and user-agents - Carry on with the SC as it is and provide guidance in understandings that browsers can fulfill the SC if you test it, with 1 objection requesting including a default focus indicator.
- Question 2 - Using target-area as the basis for size metrics - We love Wilco
- Question 3 - Insufficient requirement for focus indication via enlargement #1858 - Accept amended response from Alastair and David to address issue 1858.
7 December: (MEETING TITLE)
- Review Writing Testable WCAG 3.0 Outcomes Survey - AGWG approves amended Writing Testable WCAG 3.0 Outcomes for internal use
- Question 1 - Form field has non-empty accessible name - Accept publishing "Form field has non-empty accessible name"
- Question 2 - Attribute has valid value - Accept "Attribute has valid value"
- Question 2 - Attribute has valid value - Accept "Attribute has valid value"
- Question 3 - Element marked as decorative is not exposed - Accept amended "Element marked as decorative is not exposed"
- Question 4 - Letter spacing in style attributes is not important - Accept "Letter spacing in style attributes is not important"
- Question 5 - Word spacing in style attributes is not important - Accept "Word spacing in style attributes is not important"
3 December: AGWG WCAG 2.2 Issues
- Dragging Movements needs some attention #1917 - Carry on with SC
- Adobe Comment on 2.5.7 Dragging Movements #1886 - Accept PR 1961 as amended by the text above
- Is keyboard functionality acceptable if an on-screen keyboard can be used. #1978 - Accept PR 2009
- Exception for web content used by the author but generated by the user agent? #1977 - Agreed response to #1977
- Does the Definition of "Dragging Movements" Intentionally Limit the Scope to Moving Objects/Items? #1560 - Accept the amened PR, knowing that the document will be further reviewed soon.
- Exceptions seems like free form paths rather than dragging #1979 - Remove the example from the understanding document.
- Further guidance on 2-factor independent methods #1965 - accept PR as amended by survey comments
- Google feedback #1890 - Accept the response to 1890 and update the definition as amended
- Page break navigation https://www.w3.org/2002/09/wbs/35422/wcag22-page-break-nav/results - accept PR 1226 as is
- Overly prescriptive? #2026 - Accept response and add a link to the word “mechanism” in the SC and plan epub requirements discussion for 3.0
- Update page-break-navigation.html #2094 - Accept response, revisit the word “page” as used in this SC with Epub contribution or add a note to clarify what page means here.
- Update page-break-navigation.html #2094 - Accept PR with amendments as discussed
- Visible controls re-write - accepting this PR And including suggestions on how and where as part of understanding but not requiring it
- The first exception is difficult to understand #1760 - Accept response
- Subjective judgement is needed #1877 - accept response
- Understanding doc updates - Accept PR
- Controls that require scrolling to reach #1875 - Accept PR
- Clarify "available for the user to select." #1973 - Accept PR as ammended
- Remove explanation of help mechanisms #1881 - Accept PR as amended in survey
- Clarify situations where some pages in set provide no help #1972 - Accept PR
- Questions to resolve for consistent testing #2068 - Accept PR but keep question of SC text open until we look at other PRs
- Wording is perhaps confusing #2098 - accept PR 2145 as amended to close Issue 2098 and 1693
30 November: AGWG Teleconference
- Request to change web to digital in Abstract - Reject PR and send response as amended; then explore clarifying web based technology (possibly with W3C) and apply it throughout
- Name Change #1871 - Accept response with Mike Gower's amendment
- Using "should" in the Understanding doc is confusing #1874 - Accept PR and discuss wording choices further in a future meeting.
- Google feedback #1894 - Accept PR and response as amended.
- Adding diagrams that make the reality/consequences of target offset clearer #1848 - Accept the PR with the removal of last part of 103 (see survey) and Todd will take a last look at optimizing the experience between alt text and fig caption content.
- Dragging Movements needs some attention #1917 - Accept PR but add issue to give this PR more attention including the challenges that Mgower raises.
23 November: AGWG Teleconference
- Request to add a target increase in level of effort - Don't add to requirements document but schedule a conversation about the holistic cost of WCAG 3 after we make more progress (add to WCAG 3 schedule after conformance decisions for future discussion)
- Common Input Aspects note - Accept note as ammended
- Element with lang attribute has valid language tag - approve publishing Element with lang attribute has valid language tag
- Element with lang attribute has valid language tag - approve publishing Element with lang attribute has valid language tag
- Further Examples Required #1872 - Accept PR and response for 1872 as ammended
- Align Target Size (min) with Target Size (enh) #1721 - Accept PR for #1721
- Is "24 by 24 CSS pixels” reasonable? #1831 - accept response to 1831 as amended
- Minimum Component Size #1870 - Accept response to #1870 as ammended, and follow up on spacing issues raised by Abi
16 November: AGWG Teleconference
- Does the Silver scope covers closed systems / kiosk UIs? - Respond with "WCAG 3.0 could be useful for the web-based portion of closed systems that utilize web technologies, but it would not tackle issues around the physical aspects or user-agents of those systems."
- Backwards Compatibility Question - adopt updated response https://github.com/w3c/silver/issues/424#issuecomment-966166500
- Target Size addition of user agent and equivalent exceptions #1993 - Use proposed wording, add to understanding, and create an issue to explore the use of "not modified by author"
- Issue 1976 and same PR - The function can be acheived through a different control on the same page that has an area of at least 24 by 24 CSS pixels;
9 November: AGWG Teleconference
- Process approval survey - placeholder content will require WG approval, to be sought asynchronously, and any content that does not get asynch approval will be discussed. Chairs take an action to bring back asynchronous options with feedback from COGA so the working group can select an option for asynchronous decision making
- Process approval survey - Try out adding all levels of content to editor's draft using working group agreement (asynchronous for placeholder if possible, survey+meeting for placeholder when needed and for all other levels) and to the working draft using working group agreement+CFC , with full level markings and warnings and then revisit this in a few months to see how its working. We will explore filtering within the editor's draft as part of this
- Difficult to understand meaning #1840 - Rework to address concerns raised outside of meeting and resurvey
- Confirmation on navigation menus #1845 - Accept ammended response (Gregg's suggestion added)
2 November: AGWG Teleconference
- Use of the word “state” is not sufficiently consistent #2049 - Adopt the revised wording "Contrast: The area has a contrast ratio of at least 3:1 between the colors when the component is focused and when not focused
- Focus indicators for large editing areas #2017 - Adopt PR with slight addition to be made by Mike to explain insertion point
- Exception may not align with understanding text #1980 - Accept PR 1990 and adjust other areas as needed
26 October: AGWG Teleconference
- Whether to require working group agreement to add placeholder content - placeholder content will require WG approval, to be sought asynchronously, and any content that does not get asynch approval will be discussed. Chairs take an action to bring back asynchronous options with feedback from COGA so the working group can select an option for asynchronous decision making
19 October: AGWG Teleconference
- What is a complex shape? #2050 - Accept revised wording and add circular focus examples to understand doc
- Focus indicators for large editing areas #2017 - Agree that we don't think this is an issue but need additional text around defining UI component
- Focus appearance should be in Perceivable - Leave focus appearnance operable
- Focus appearance should be in Perceivable - Leave focus appearance in operable
- Focus appearance should be in Perceivable - Leave focus appearance in operable
- Need more info on adjacent contrast #1929 - Accept the updates in PR2060 and 2097
12 October: AGWG Teleconference
- Question 1 - Inline elements that wrap over multiple lines #1328 - Accept PR 2040 to address issue #1328 and consider a failure technique in the future
21 September: SV_MEETING_TITLE
- WCAG 2.2 Accessible Authentication (Q1-2) https://www.w3.org/2002/09/wbs/35422/wcag22-accessibile-auth/results - Accept the updates to AA and AAA SC and understanding documents for Accessible Authentication as in PR 2046
- Note for WCAG 2.2 - Accept Alastair's proposed text.
- Update Technique G195 procedure #1931 - Accept technique update with Patrick's edits and changing the color from red to another color
- Make clearer the method of calculating the minimum area #1883 - Accept the response
- Sizing impresise and fairly complicated #1718 - accept the proposed response and keep "perimeter"
14 September: AGWG Teleconference
- Question 1 - Recognizing common objects path forward - to propose a AA level SC that allows for recognizing common ob
- Question 1 - Google feedback - Accept amended response to address issue 1896.
7 September: AGWG Teleconference
- WCAG 2.2 focus-appearance: https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced2/results - to accept the proposed updates with suggested edits and address substantive issues in new SC
- Confusing wording due to unconventional state requirement #1859 - Accept proposed response and PR
- 4. Gradient Focus Indicators #1861 - Accept proposed response to #1861
- 2. Understanding document updates - Accept PR2000
31 August: AGWG Teleconference
- Merge AGWG and Silver after delivery of WCAG 2.2 - Approve merging groups after WCAG 2.2 moves to horizontal review (Additional details to be worked out including how to handle the community group, how to address ATAG and UAAG content within the charter and WCAG 3 process, and meeting schedules)
24 August: AGWG Teleconference
- Approach to publishing WCAG 3 https://www.w3.org/2002/09/wbs/35422/approach/results - adopt Proposed steps: 1. Publish the current work (new guideline plus user generated comment, and explainer and note) in September. 2. One (or more) goal-based milestones related to conformance and some critical mass of draft guidelines/outcomes.
17 August: AGWG-2021-08-17
- Error Prevention guideline and associated methods - Move amended Error Prevention Guideline to CFC for addition to the next update of WCAG 3.
- Editors Note about Approach - Slip next WCAG 3 heartbeat to mid-September.
- Question 1 - Consistent Help note doesn't make sense to me #1924 - Accepted as amended
- Question 2 - Success Criterion 3.2.6 Consistent Help (A) #1892 - Accept amended PR 1968 and response to address issue 1892.
- Question 2 - Ensuring single transactions (from the user's perspective) are covered #1880 - Accept amended option 1 and PR 1992, scope in 3rd party providers
- Question 3 - Does redundant entry require saving PII? #1843 - Accept Alastair's response to address issue 1843
- Question 1 - Are pages with print CSS that includes page breaks excepted? #1868 - Accept response to issue 1868
- Question 2 - Is EPUB Web Content? #1869 - Accept amended PR 1994 to address issue 1869
- Question 3 - Google feedback - Accept amended proposed response to address issue 1869
- Question 4 - What is and is not programmatically determined #1969 - Accept amended PR 1995 to address issue 1969
10 August: AGWG Teleconference
- CSUN meeting (survey, 5 minutes) https://www.w3.org/2002/09/wbs/35422/csun_2022/results - probably no, reevaluate in December
- Glossary Definition of User Generated Content - Move the amended User Generated Content section to CFC for addition in the next update of WCAG 3.
- Glossary Definition of User Generated Content - Accept: The publisher in this definition is the owner of the website providing content, not the owner of a paid platform used for website creation.
- Glossary Definition of User Generated Content - Accept sending amended glossary definition with editors note to CFC for inclusion in the next version of WCAG 3
3 August: AGWG Teleconference
- Explainer note https://www.w3.org/2002/09/wbs/35422/2021-07-Explainer-Note/ - Move the modified WCAG3 Explainer to CFC for addition to the next update of WCAG3 as a first draft of what will be a Working Group Note, including a yet to be agreed upon note calling out the various moving parts.
- Question 1 - Minimum Area clarification #1806 - Accept PR 1966 to address issue 1806
- Question 2 - Browser default focus indicators #1854 - Accept Alastair's response to address issue 1854
- Question 3 - Gradient Backgrounds #1862 - Accept update to PR 1967 and response to address issue 1862
- Question 1 - Consistent Help note doesn't make sense to me #1924 - Leave the note and update the understanding document
27 July: AGWG Teleconference
- Error Methods Prevention Guideline - Move the Guideline to CFC after the link is fixed, placeholders are added, and "Outcome:" is added to template.
- Approval to move ACT/Silver Method Proposal to CFC - Move the proposed ACT structure (not content) to CFC for use going forward [12:01]
- Approval to move ACT/Silver Method Proposal to CFC - Resolution: Move the proposed ACT structure (not content) to CFC for use going forward [12:01]
- "the value of spacing" confusing wording #1852 - Accept PR 1853
- Adobe Comment #1889 - Accept as amended
- User-agent components that can't be styled #1904 - Accept as amended<strong>Necessary:</strong> A particular presentation of the target is essential or is legally required for the information being conveyed;</li>
20 July: AGWG Teleconference
- Question 1 - Adobe Comment on 3.3.7 Accessible Authentication #1885 - Accept updated response to address issue 1885
- Question 2 - Add requirement / control to "show password" for end-users #1912 - Accept amended PR 1940 to address issue 1912
- Question 3 - Ensuring copy-paste is not blocked #1878 - Accept PR 1960 to address issue 1878
- Question 1 - Undefined term to define a term, and needs to clarify #1927 - Accept amended PR 1962 to address issue 1927
13 July: AGWG Teleconference
- Concerns about 3rd party - For next heartbeat publication, concentrate on user generated content only. Discuss how authoring tools can prompt or fix. Save paid content and services for further discussion. Name "User generated" vs "End user generated" to be decided in the future.
- Concerns about 3rd party - For next heartbeat publication, concentrate on user generated content only. Discuss how authoring tools can prompt or fix. Save paid content and services for further discussion. Name "User generated" vs "End user generated" to be decided in the future. Reference IRC chat for conversation.
- "single pointer" definition not quite accurate? #749 - Accept PR 809
- 'Headings' are enough to pass 2.4.1: Bypass Blocks #1712 - Accept PR 1946
- is it acceptable to only support niche, propriety, OS specific, and potentially inaccessible methods? #1899 - Accept revised response https://github.com/w3c/wcag/issues/1899#issuecomment-866716764
- Are system-level tests out of scope? Are PINs and Passwords synonymous? #1900 - Accept https://github.com/w3c/wcag/issues/1900#issuecomment-861909232 and https://github.com/w3c/wcag/pull/1909/files
- supporting copy-paste, example with memorable information, and specific characters #1901 - accept response https://github.com/w3c/wcag/issues/1901#issuecomment-868693998
- Clarification on USB-based 2FA #1903 - Accept response https://github.com/w3c/wcag/issues/1903#issuecomment-868707632
6 July: AGWG Teleconference
- Question 2 - Do the 'Dynamic Examples' satisfy WCAG 1.4.11? #1670 - Accept PR 1672 to address issue 1670
- Question 1 - confusion about "paste" #1855 - accept amended PR 1898 to address issue 1855
- Question 2 - Other Methods #1879 - Accept response to address issue 1879
29 June: AGWG Teleconference
- "Changes of color" applied to motion definition #1535 - Motion animation does not include changes in an element's color, blurring or opacity, where the change does not alter the perceived size, shape, or position of the object.
- "Changes of color" applied to motion definition #1535 - Motion animation does not include changes in an element's color, blurring, or opacity where the change does not alter the perceived size, shape, or position of the object.
- "Changes of color" applied to motion definition #1535 - Update both
- Carousels fail 2.2.1: Timing Adjustable? #1658 - Amended PR 1688 to address Issue 1658.
22 June: AGWG Teleconference
- Question 2 - Can text buttons fail 1.1.1 and 3.3.2? #985 - Accept amended PR 1568 to address issue 985
8 June: AGWG Teleconference
- Reporting in 3.0 discussion - Gather more tests, etc then revisit in1-2 months to see if a subgroup can work on it
1 June: AGWG-2021-06-01
- Question 1 - 1. Target size understanding review #1770 - Accept amended PR 1770.
- Question 1 - 1. Target size understanding review #1770 - Accept amended PR 1770
- Question 1 - 1. Target size understanding review #1770 - Accept the draft response for issue #930
- Question 1 - 1. Target size understanding review #1770 - Accept Rain's amended draft response for issue #930
- Question 3 - Update benefits of 2.5.1 pointer gestures #747 - Accept PR 1569 to address issue 747
- Question 4 - Text spacing: does it require compatibility with one or all methods? #975 - Accept amended PR 1687 to address issue 975
25 May: AGWG Teleconference
- Question 1 - Text spacing, "setting all of the following" to "any" (NORMATIVE) #930 - The intent of the SC was to set all 4 simultaneously. We will not change, and we will review the proposed response at a later date.
11 May: AGWG Teleconference
- Continue next steps and WCAG 3.0 discussion - Work through headings as a group and then figure out next steps
- Errata on contrast variable https://www.w3.org/2002/09/wbs/35422/WCAG22-Misc-items/ - Accept amended PR 1780 to address issues 1213 and 360
4 May: AGWG Teleconference
- WCAG 3.0 topics survey https://www.w3.org/2002/09/wbs/35422/Follow-on-topics/ (60 min) - Use the WCAG 3 FPWD scope to views and processes and better define both.
29 April: AGWG Teleconference
- Testing objectivity - For WCAG 3, testing will aim to improve intertester reliability and will work on testing to determine this
- Which tests to include in conformance - For WCAG 3, testing will aim to improve intertester reliability and will work on testing to measure this
- Session 3 - Conformance - We support a simpler on ramp below bronze that is not conformance, and will explore this further later
- Session 3 - Conformance - The maturity model may be published as a separate document.
27 April: AGWG Teleconference
- 264 - Accept the updated responses & PR
- New technique for new contrast formula (threshold value) #1213 - Create (proposed) editorial errata that updates value, update G18 to include new value (for WCAG 2.0/1/2) with note that says "Prior to May 2021 there was a different value..."
- Understanding 1.4.3 and 1.4.6 should refer to 1.4.11 #1261 - Accept PR and close issue
20 April: AGWG Teleconference
- #507 Email: Siteimprove Comments on WCAG 3.0 Draft (1 - The proposal fundamentally alters the way in which WCAG is tested) - Close 495, Leave 507 open, close 510 and 458 to either a milestone or ovearching issue to track
- WCAG 2.2 Redundent entry (Q1 only) https://www.w3.org/2002/09/wbs/35422/wcag22-redundant-entry-updates/results - Move forward with concept of version 2
- WCAG 2.2 Redundent entry (Q1 only) https://www.w3.org/2002/09/wbs/35422/wcag22-redundant-entry-updates/results - adjust the language to Except when with bulleted list
- Target size (Q1) https://www.w3.org/2002/09/wbs/35422/wcag22-target-spacing-issues/results - Accept this updated understanding. Create a new PR with an additional map example using pins, additional measurement example, Rain and Michael's suggested edits and creating an issue on maps as an exception for future discussion
13 April: AGWG Teleconference
- WCAG 2.x issues https://www.w3.org/2002/09/wbs/35422/WCAG22-Misc-items/ - Reject this PR and explore other solutions, perhaps an errata
- WCAG 2.x issues https://www.w3.org/2002/09/wbs/35422/WCAG22-Misc-items/ - Reject this PR and explore other solutions, perhaps an errata
- Decision Policy - Move Decision Policy to CFC with proposed removals
6 April: AGWG Teleconference
- Focus appearance survey https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-updates/results - Accept the amended updates to the SC Text and understanding document for Focus Appearance
- The math is difficult to understand and explain #1439 - Accept the proposed response to address issue #1439
- Target size/spacing (Q1 only) https://www.w3.org/2002/09/wbs/35422/wcag22-target-spacing-issues/results - Agree with the updated and amended SC text for Pointer Target Spacing
30 March: SV_MEETING_TITLE
- WCAG 2.2 Target size/spacing (Q1 only) https://www.w3.org/2002/09/wbs/35422/wcag22-target-spacing-issues/results - Use "target offset" and work on definition via email list for next week
- Fixed reference points https://www.w3.org/2002/09/wbs/35422/wcag22-fixed-ref-points-updates/results - Accept MG's suggestion to change title to "Page Break Navigation", and to update response accordingly
- Tal Persona - Use TAL's name and no pronouns for TAL, and to not create a pronoun statement.
16 March: AGWG Teleconference
- Focus appearance enh https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced/results - Accept amended PR 1623 to facilitate Focus Appearance Enhanced more closely matching the AA version.
- Focus appearance enh https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced/results - Accept amended PR 1623 to facilitate Focus Appearance Enhanced more closely matching the AA version.
- Dragging update https://www.w3.org/2002/09/wbs/35422/wcag22-dragging-issues/results - Accept amended PR 1649 to update the cross reference of Dragging / gestures
- Visible controls https://www.w3.org/2002/09/wbs/35422/hidden-controls-12-2020/results - Accept amended PR 1648 to update the examples for visible controls
9 March: AGWG Teleconference
- Member driven agenda additions - Adjust meeting to add introducation and announcements, no more than 5 minutes
- AG Decision policy update https://www.w3.org/2002/09/wbs/35422/ag-decision-policy-update2/results - Rework this content and bring back.
- Renaming Findable Help - Change name to Consistent Help
- Make changes to SC text - Accept proposed wording: For each web page within a set of web pages that provides one or more of following ways of finding help, access to at least one form of help is included in the same relative order on each page
- Findable Help - Goal of Criterion Ambiguous #1435 - Accept response and pull request with discussed revisions
- Responding to Issue 1148 clarifying questions and suggestions - Accept the response along with text from mgower
- Adding exception for continuous regions - Accept adding a note instead of an exception. Wording above.
- Add exception for equivalent functions - Do not include an exception for equialent functions but address in understanding
- Add exception for equivalent functions - Do not include an exception for equialent functions but address in understanding
- Changing the name of the SC - Rename the new SC to Target Size (Minimum); Rename 2.5.5 Target Size (Enhanced)
- Changing the name of the SC - Rename the new SC to Target Size (Minimum); Rename 2.5.5 Target Size (Enhanced)
2 March: AGWG Teleconference
- Updated SC text for closing issues (revised again) - Accept the amended update and response to address issues 1361, 1381, 1384, 1433 and 1444 and create a new issue for sliders
- Rewording Findable Help to address scoping questions - Agree with Bruce's amended rewording to address issues 1436 and 1367
- Re-name the SC? - Keep the name the same
- Google feedback #1453 - Accept amended PR 1639 to address the suggestions, and accept the response to address issue 1453
- Adjust process definition example - Accept PR 1640 and response to address issue 1453
- Re-entry and security #1346 and #1431 - Accept the proposed response to address issues 1346 and 1431
23 February: AGWG Teleconference
- Updated SC text for closing issues - Merge changes, bring back with new understanding doc updates, prior to CFC
- Minimum pointer clearance needs better empirical backing #1445 - Accept the amended response to address issue #1445
- Google feedback #1456 - Accept amended draft response to address issue #1456
- Re-entry and security #1346 and #1431 - Leave SC text as it is
16 February: AGWG Teleconference
- Question 2 - Google feedback #1451 - Accept amended draft response and PR 1624 to address issue 1451.
- Question 3 - Suggest including the first note AAA as well. #1405 - Accept PR 1625 to address issue 1405
- Question 4 - C41 does not fulfil SC 2.4.12 #1306 - Accept PR 1626 to address issue 1306
- Question 5 - Update G195 - Accept PR 1627 to update technique G195
- Question 1 - The term "minimum focus indicator area" is confusing #1544 - Reject PR 1628, leave SC and modify the understanding document, to be reviewed in call later.
- Question 1 - Change "Operated" to "Achieved" - Accept Michael Gower's recommended change of "Operated" to "Achieved", and create issue that requests erratum for 2.5.1.
- Question 2 - Dragging and its reference to single pointer #1225 (take 2) - Accept draft response and PR 1636 to address issue 1225, and Sarah Horton will provide new PR with additional improvements.
9 February: AGWG Teleconference
- Dragging and its reference to single pointer #1225 - Keep the definition as is, amend PR to update understanding, and draft new response.
- Dragging - essential example #1336 - accept ""There may be cases where a dragging movement is essential, for example, drawing a free-form figure, or playing a game where the aim is to follow a particular path as accurately as possible."
- Google feedback on dragging #1454 - Accept draft response to address issue 1454.
- WCAG 2.2 Accessible authentication (Q1 only) https://www.w3.org/2002/09/wbs/35422/wcag22-accesssible-auth-updates/results - Accept PR 1611 and response to address issue 1256 with the sentences swapped
- WCAG 2.2 Visible controls (Q1 only) https://www.w3.org/2002/09/wbs/35422/hidden-controls-12-2020/results - Add a sentence clarifying that the other SC apply and Rain will craft updates for issue 1455 and team will review in a subsequent call.
- UPDATED: Google feedback on Fixed Reference Points #1449 - Accept response and work on understanding and page break locator terminology
- "on the same page" #1302 - Accept previous resolution as solution to this issue.
2 February: AGWG Teleconference
- Silver requirements updates survey https://www.w3.org/2002/09/wbs/35422/2020-01-silver-requirements-update/results - Take Detlev's proposal back, request comment from people who requested the change.
- AG decision policy update https://www.w3.org/2002/09/wbs/35422/ag-decision-policy-update/results - Update policy again, return soon
- Visible controls https://www.w3.org/2002/09/wbs/35422/hidden-controls-12-2020/results - Accept the new text from the mailing list
- Using 'controls' in the SC text again - No change
- Update to the note - Use "User interface components can be available through other visible components such as sub-menus, edit buttons, tabs, or thumbnails of media."
- Fixed Reference Point wrap up https://www.w3.org/2002/09/wbs/35422/wcag22-fixed-ref-points-updates/results - Accept new text
26 January: AGWG meeting
- Question 1 - Redundant entry, term "step" is ambiguous #1345 - Update PR 1597 and update draft response to remove "step" to address issue #1345
- Question 2 - Comment from IBM: Redundant Entry needs to be more tightly scoped in the SC language - Accept PR 1487 to address issue #1410
- Question 3 - 3.3.8: Redundant entry - session term #1335 - Accept Alastair's response to address issue #1335
- Question 4. Redundant entry - Accept amended response to address issue #1446
- Question 1 - New version: Visible Controls - Accept amended SC change and note using the word "component" uniformly.
19 January: AGWG Teleconference
- Updating the size metric - Accept change to minimum area
- Must a focus indicator always be displayed? #1387 - Continue with wording in Focus Appearance that addresses sticky footer
- Understanding 2.4.11 minimum area - focused/unfocused? #1552 - Accept PR 1577
- 2.4.11 Unobscured bullet will fail the common chatboxes widgets #1502 - Accept the response for #1502
- Adjacent contrast and unobscured clauses #1399 - Accept the response for #1399
- Adjacent contrast and unobscured clauses #1399 - Accept the response for #1399
- A point for the Understanding doc #1227 - Accept PR 1579
5 January: AGWG-2021-01-05
- WCAG 3.0 objection update Survey: https://www.w3.org/2002/09/wbs/35422/2020-12-editorsnote/ - Accept the proposed Editor's note in WCAG 3 FPWD on inclusion
- Notable Contributions Section and Editor's Note - Accept the amended "Notable Contributions Section and Editor's Note"
- Question 1 - Updates to G183 remove the focus step in the procedure - Accept the response and amended PR and close issues 1118 and 1272
- Question 2 - Clarity for 1.3.3: Sensory Characteristics needed #1532 - Accept Alastair's amended update to second example in PR 1571
- Question 1 - Some suggested editorial changes for clarity Issue #1462 - Accept Alastair's proposed response to issue #1462
- Question 2 - Does this SC really apply to "single page" web applications? #1427 - Accept Alastair's proposed response to issue #1427

2020

15 December: AG Meeting 15 December 2020
- Use of color & contrast survey https://www.w3.org/2002/09/wbs/35422/wcag22-color-updates/results - Create new issue to fix the gap in Example 1 which does not fully support screenreader users
- Use of color & contrast survey https://www.w3.org/2002/09/wbs/35422/wcag22-color-updates/results - Accept PR 767 to address issues #750 and #1532
- Note and benefits contradict each other in 1.4.1 #1032 - Accept PR 1500 to address issues #1032, #1076 and #1370
8 December: AG teleconference
- December 22nd Meeting - Last meeting of 2020 is on the 15th, 1st meeting 2021 is Jan 5th.
1 December: AGWG-2020-12-01
- Response to #1437 - Accept the suggested response from Scha14 to address issue #1437
- Response to #1367 about "Set of Web Pages" - Update response to issue #1367 and include additional examples in understanding docs, and review in a subsequent meeting.
- Question 4 - Response to #1434 - Accept the amended suggested response from Alastair to address issue #1434
- Question 5 - Response to #1394 - Accept the amended suggested response from Alastair to address issue #1394
- Question 6 - Understanding update to address #1347 and #1368 - Accept the amended suggested response from Alastair, and update PR #1538 to address issues #1347 and #1368
- Question 7 - Group of changes together #1242 - Follow up with Guy Hickling on the amended proposed text, and disregard PR.
- New formulation of the SC text - Accept Michael Gower's amended update to the SC text, with additional note per David MacDonald
24 November: AGWG 24 November 2020
- Focus appearance (question 1 only) https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-updates/ - Accept PR.
10 November: AGWG-2020-11-10
- Question 1 - Add mechanism text #1418 - Accept the suggested text available in PR 1505 to address issue #1418.
- Question 2 - Accessible Authentication #1318 - Accept Alastair's modified draft response to issue #1318
- Question 3 - Clarify whether copy/paste is a cognitive function test #1359 - Accept the accepted change in PR 1419 to address issue #1359
- Question 4 - Far too fundamentally restrictive for a Level A #1364 - Accept Alastair's draft response to issue #1364
- Question 5 - Concerns and clarifications #1470 - Accept Alastair's draft response to issue #1470
- Question 6 - Conflict with legal and contractual obligations #1430 - Accept Alastair's draft response to issue #1430
- Question 7 - Feedback from Google #1452 - Accept Alastair's draft response to issue #1452 and accept PR 1508.
- Question 1 - Must a focus indicator always be displayed? #1387 - Review and return with a modified response for the group to review.
- Question 2 - Consider distance between component and indicator #1382 - Accept Detlev's amended draft response to issue #1382
- Question 3 - Does a change of background pass Focus Appearance (Minimum) #1278 - Accept amended PR 1495 to address issue #1278
- Question 4 - Example 2 for G195 is too inaccurate #1305 - Update the second example to include visuals and review later.
- Question 5 - UPDATED: Exception for the default focus indicator? #1341 - Add the proposed text to the understanding document to address issue 1341.
- Question 6 - Example calculations do not account for corners #1324 - Accept amended PR 1498 to address issue #1324
- Question 7 - Understanding rewording suggestions #1501 - Review Michael Gower's changes to PR 1501 next meeting
3 November: SV_MEETING_TITLE
- Focus-appearance and Non-text-contrast relationship #1490 - Accept the SC update as amended, and the understanding document update.
- Focus: should indicator be unique? #1383 - Agree with updated response
- Contrast for aliased pixels #1348 - Accept update #1493
- Non-modal dialogues and Unobscured #1352 - Accept update as ammended
27 October: AGWG 27 October 2020
- Dragging Movements (1st question only) https://www.w3.org/2002/09/wbs/35422/wcag22-dragging-issues/results - Approve the changes for issue #1316
- Pointer Target Size (1st question only) https://www.w3.org/2002/09/wbs/35422/wcag22-target-spacing-issues/results - Use Andrew's suggested response: The definition of target is: "region of the display that will accept a pointer action, such as the interactive area of a user interface component". If a label and the input form one target and if user-agents support making the label clickable as a mechanism to take an action on a user interface component, then the label's area can contribute to the target size.
20 October: AGWG-2020-10-20
- Dragging on mobile apps #1307 - Accept Detlev's response to 1307 with modifications
- Adding the word "Pointer" to "2.5.7 Dragging" #1397 - Approve changing title to Dragging Movements.
- Cross-reference Dragging and Pointer Gestures in Understanding #1316 - Accept PR 133416 to address 1316
- Relationship/overlap between 2.1's "Pointer Gestures" and 2.2's "Dragging" #1398 - Accept PR 1423 to address Issue #1398 with Alastair's modifications
- Updated proposal for "Target Size" - Continue working and review later.
13 October: AGWG teleconf
- Silver scoring survey: https://www.w3.org/2002/09/wbs/35422/wcag3_Scoring/ - Include existing scoring example in FPWD with to be determined and approved framing
29 September: AGWG-2020-09-29
- Question 4 - Button has non-empty accessible name - Rule has been approved for publishing
- Question 1 - HTML page has non-empty title - Rule has been approved for publishing
- Question 2 - Image has non-empty accessible name - Rule has been approved for publishing
- Question 3 - Link has non-empty accessible name - Rule has been approved for publishing with amendments
- Question 5 - Form control has non-empty accessible name - Rule has been approved for publishing
- Question 6 - Meta viewport does not prevent zoom - Rule has been approved for publishing
- Question 6 - Meta viewport does not prevent zoom - Rule has been approved for publishing
- Moving Silver Requirements to a group note - Approved to move Silver Requirements to a group note
- Location of Examples of Silver Scoring - Improve content and include as a separate document referenced by draft or by announcement. Will be reviewed by group.
- Normative / informative discussion - Accept Michael's changes to use of non-normative.
22 September: AGWG teleconference
- Change "must" to "is" in the SC text #1280 - accept pull request 1408
- Clarify exceptions in definition #1310 - Accept amended pull request 1411, close issue 1343 and incorporate feedback from 1344
- Understanding flow #1313 - Accept amended pull request 1412
- Confusing example: properly marked up email and password #1363 - Accept pull request 1415
- Clarify whether copy/paste is a cognitive function test #1359 - Do not accept the PR, propose a new understanding update, allowing for copy/paste.
- Include each step in an authentication process #1358 - Accept pull request 1414
- Does this include CAPTCHAs? #1256 - Accept amended pull request 1407 and we will update the understanding doc instead.
15 September: AGWG-2020-09-15
- Question 1 - Revised MVP - Reduce MVP to 5 guidelines, 3 of which will have how-to's, future guidelines will be complete in future drafts
- Question 1 - Revised MVP - Reduce MVP to 5 guidelines, 3 of which will have how-to's, future guidelines will be complete in future drafts
- Question 4 - Introduction - Discussion incorporated into new draft and brought back for review.
- Question 5 - Structure of these guidelines - Discussion incorporated into new draft and brought back for review.
- Question 6 - Normative requirements - Discussion incorporated into new draft and brought back for review.
- Question 7 - Guidelines (Not linked content) - Discussion incorporated into new draft and brought back for review.
8 September: AGWG 8 September 2020
- Changing the option term - Accept option 1 of AWK's amended language for PR #1356
- Same relative order term #1230 - Agree with proposed response
- Is one option enough? #1235 - revise response for later review
- Available or provided? #1232 - Use AWK's proposed wording to respond
- What is self-help? #1229 - Use Alastair's proposed response "Help content provided by the author"?
- Being responsible for content #1303 - Accept PR #1366 and additionally Rachael's proposed amendment to the response
- re-review Is one option enough? #1235 - Accept Sukriti's amended response
- re-review Is one option enough? #1235 - Accept Sukriti's amended response
- Understanding note gives the wrong rationale? #1362 - Accept PR 1379
- Pointer Target Spacing - target size #1311 - Accept proposed response
- Overlapping Spacing #1312 & #1361 - Put AGWG team together to continue review and craft a proposal.
25 August: AGWG-2020-08-25
- Could autocomplete meet the redundant entry SC? #1194 - Accept new line to understanding document of redundant entry to address issue 1194.
- When information previously entered has been saved #1239 - Accept Alastair's response to the issue.
- Are redundant resumes/curriculum vitae in online job applications a failure? #1293 - Accept Sukriti's new line to understanding document of redundant entry to address issue 1293.
- Add mobility use case #1276 - Accept new line to understanding document of redundant entry to address issue 1276.
- Unobscured: request to raise requirement #1271 #1304 - Accept the proposed alternative answer for issues 1271 and 1304.
- Not fully obscured wording (Normative) #1291 - Accept the recommended changes to address issue 1291.
- Add example of 8px side border #1279 - Accept the recommended changes to address issue 1279.
- Possible grammatical error in UIC definition #1296 - Accept the change with quotes to the terms for user interface components to address issue 1296.
- How should 2.4.11 / 2.4.12 be applied to inline elements that wrap over multiple lines? #1328 - Accept the changes to the understanding of focus appearance to address issue 1328.
18 August: 18 August 2020 AG Meeting
- Representative Sampling - Include note on representative sampling in draft recognizing it will come back to this group for further review.
- Testing Editors Note - Use edited wording for Testing note and work on "rubrics and scales"
- Depreciation - Including a date stamp, no depreciation, add editor's note
11 August: Silver Deep Dive
- Discussion on Representative Sampling - Move topic to back of queue
- Scope & Definitions - We won't be weighting guidelines by disability for the FPWD
4 August: AG meeting
- Review and approve response to Issue 1156 "Loophole in SC2.4.11 allows almost invisible focus indicators" - Approve respose, but instead of a note, the understanding document will be updated to reflect commentary currently in note, and present to group for later review and approval.
- Dragging movement glossary definition: Deleting reference to intermediate point - Accept new definition for Dragging movement: "an operation where the pointer engages with an element on the down event and the element (or a representation of its position) follows the pointer"
- Clarity on Understanding 1.4.11 regarding hue #868 - Accept response and update the caption to figure 7 as above.
- exception for logos (1.4.3, 1.4.11) #902 - accept Alastair's proposed response and close issue 902
- Meet 1.3.5 via name attributes mapping to schema.org? #935 - Accept response and update understanding document for later review, close issue 935.
- Cross behavior between focus and hover (1.4.13) #1196 - Amend response based on either hover or focus applying, and review amended response later.
- SC 1.3.5 fields with correct autocomplete inside form with autocomplete="off" #1197 - Accept amended proposed response and close 1197.
- Removing application as a landmark from ARIA11 #780 - Approve pull request and close issue 780.
- Remove misleading/incorrect statement from 1.4.11 understanding #1058 - Accept proposed response and close 1058.
- Changes to examples in Understanding 1.4.11 #1065 - Accept proposed change and close 1065.
- Removing Flash Techniques #1142 - Agreed to remove flash techniques from WCAG 2.1 and WCAG 2.2, close #1142.
- Update link-purpose-in-context.html #1164 - Continue conversation for proposed response to 1164 at a later date.
28 July: AGWG
- question 1 - SC 1.3.5 Technique "Use type attribute on fields in simple login forms"? #504 - Accept response to question #1.
- question 2 - labelled navigation landmarks should be added to sufficient techniques for 2.4.4 #619 - Accept Detlev's response.
- question 3 - 1.4.11 hover state clarification #849 - Accept Laura's response.
- question 4 - Clarity on 1.4.11 as it applies to "Cards" #856 - accept response and ammended. Defer evaluating changing understanding document.
21 July: SV_MEETING_TITLE
- Revisit reflow question: Include 'down to' or not - Consensus is to not change "at" to "down to", and to review possible research and date for a later version.
- Question 1 - Adding fstorr's updates - border note in focus-visible-enhanced - Accept MG's proposed changes to focus-visible-enhanced.
- Question 2 - Focus appearance rewording of bullet 2 #1212 - accept Alastair's proposed text change for question 2.
- Question 3 - Review and approve response to Issue 1156 "Loophole in SC2.4.11 allows almost invisible focus indicators" - Leave Issue 1156 "Loophole in SC2.4.11 allows almost invisible focus indicators" open and revisit next week with revised text
- Question 4 - Review and approve response to GitHub issue 1067 "2.4.11 Focus Visible (Enhanced) Remove F78 and F55" - Accept response to GitHub issue 1067 "2.4.11 Focus Visible (Enhanced) Remove F78 and F55"
- Question 5 - Review and approve response to GitHub Issue 1049 Language of 1.4.10/Reflow exception seems broader than intended - Accept response to GitHub Issue 1049 Language of 1.4.10/Reflow exception seems broader than intended
- Question 6 - Update to reflow exception - Accept first sentence as amended and second paragraph in the question response.
- Question 7 - Dragging movement glossary definition: Deleting reference to intermediate point - review and address next week.
14 July: AGWG teleconference
- Updates to touch target spacing https://www.w3.org/2002/09/wbs/35422/Pointer-target-spacing-update/results - accept changes and publish pointer target spacing as amended
- Focus visible SC at AAA - Include the new AAA version of focus visible in WCAG 2.2
- Naming the focus visible criteria - Accept option 4 for naming.
7 July: AG Working Group 7 July 2020
- ACT rules integration review https://www.w3.org/2002/09/wbs/35422/2020-07-ACT/results - Move forward with integrating ACT Rules into WCAG Materials with changes discussed today
30 June: AGWG teleconference
- Note that we'll be versioning the informative documents - Implement versioning for informative documents.
- Add 'unobscure' bullet - Add the bullet "Unobscured: The item with focus is not entirely hidden by author-created content" and add understanding content (tbd).
- Add an AAA version? - agree to work on an AAA version of 2.4.11
- 3. Do we try to mitigate the tricky examples? - answer wtih proposed response, including a comment that we will update the understanding document.
- 3. Do we try to mitigate the tricky examples? - answer wtih proposed response, including a comment that we will update the understanding document.
- 4. Change "border" to "perimiter" - No change of "border" to "perimiter", we will review some draft changes to understanding.
- 4. Change "border" to "perimiter" - No change of "border" to "perimiter", we will review some draft changes to understanding.
- 1. Expand 1.4.10 to apply 'down to' instead of 'at' 320px (#698) - agree to explore ways to add "down to"
- 2. Level(s) for 1.4.10 Reflow #1050 - Unresolved, continue next week.
23 June: AGWG teleconference
- Making Content Usable Wide Review https://www.w3.org/2002/09/wbs/35422/content-usable-June-17/results - Publish "Making Content Usable" for wide review.
- Add Findable help to WCAG 2.2 draft https://www.w3.org/2002/09/wbs/35422/findable-help-finalisation/results - "Add Findable Help" is ready for CFC and wide review
- Add another size metric - Add the metric with an editors note to point out the need for feedback on the values, for public review.
- Matching the start of 2.4.7 - Re-introduce the following text "When a User Interface Component displays a visible keyboard focus, all of the following are true:"
16 June: AG 16 June 2020
- Update to Redundant entry - move forward with original text with link to process and steps undefined
- Proposed definition of "inactive" - To add the definition of Inactive in this week's survey, including the three Notes listed in the survey results, and the change of 'visible' to 'present' as a normative definition in WCAG 2.2
- Add another size metric - Keep open and try other wording.
9 June: SV_MEETING_TITLE
- Focus visible update - level of 2.4.7 in WCAG 2.2 https://www.w3.org/2002/09/wbs/35422/focus-visible-enh-issues2/ (1st question only) - Move 2.4.7 to A and add the new SC?
- Question 1 - Errata/clarification of 2.2.1 Timing Adjustable extension - PR not accepted, leave open for new option
- Question 2 - Formatting of Exceptions - Close GitHub issue.
- Question 3 - Add clarification of "inactive" to user interface component glossary definition - Andrew to work on "inactive" definition.
2 June: AGWG teleconference
- Redesign of support materials https://www.w3.org/2002/09/wbs/35422/redesign-requirements/ - Leave open
- COGA Usage re-review https://www.w3.org/2002/09/wbs/35422/2020-05-content-usable/results/ - Ready for CFC after today's edits are made
- Sticky headers/footers violation of SC 2.4.7 - A sticky footer/header which temporarily obscures the focus indicator does NOT cause a failure of 2.4.7
- Understanding addition about mode of operation - Accept new text as amended
26 May: AG Meeting 26 May 2020
- Conformance Challenges Update https://www.w3.org/TR/accessibility-conformance-challenges/ - New survey to act as CFC to close Thursday with todays changes
19 May: AGWG-2020-05-19
- Focus visible updates https://www.w3.org/2002/09/wbs/35422/focus-visible-enh-issues2/ - Chairs will create a simpler survey to review changes
- Understanding addition about mode of operation - Leave open
12 May: AGWG teleconference
- WCAG 2.2 Visual Indicators, last week (really) to agree SC text https://www.w3.org/2002/09/wbs/35422/Visual_indicators/results - Defer, not ready for WCAG 2.2
- Sticky headers/footers violation of SC 2.4.7 - Find some examples, leave open
- Focus visible not required whilst element focused - Accept response
5 May: SV_MEETING_TITLE
- Discuss results for COGA content usable note https://www.w3.org/2002/09/wbs/35422/2020-04-content-usable/ - Continue to review the content of Content Usable
- WCAG 2.2 Visual Indicators, last week to agree SC text https://www.w3.org/2002/09/wbs/35422/Visual_indicators/ - leave open
- WCAG 2.2 Focus indicator (enh) issues https://www.w3.org/2002/09/wbs/35422/focus-visible-enh-issues1/ - adoption Option 3 for more refinement
28 April: AG 28 April 2020
- Silver FPWD MVP discussion https://docs.google.com/document/d/1tQHgVFaJYS1WWs9BKucZxWboMNVuclvdNqnQuzPbWwY/ - This document is sufficient to define what is in the FPWD
- WCAG 2.2 Finding help - https://www.w3.org/2002/09/wbs/35422/findable-help/ - Accept SC into working draft
21 April: AGWG meeting
- Finding help https://www.w3.org/2002/09/wbs/35422/findable-help/results - leave ope
14 April: AG WG
- Survey Results for AGWG/Silver meeting times https://www.w3.org/2002/09/wbs/35422/2020-04-silverpoll/results - Re-work, re-word survey
- Public Working Draft of 2.2 and standing consent to publish - To do CFC to the larger group for standing consent for WCAG 2.2 draft publication
- Public Working Draft of 2.2 and standing consent to publish - A CfC to larger group for standing consent for WCAG 2.2. draft publication
- Conformance challenges re-review https://www.w3.org/2002/09/wbs/35422/Conformance-Challenges-FPWD3/ - publish the conformance challenges doc as a FPWD
- WCAG 2.2 Touch target spacing (Adjustment to errata): https://www.w3.org/2002/09/wbs/35422/target-spacing/ - Move the SC forward to public review. Remove the exception and add note about the exception.
25 March: AGWG extended meetings pt3
- Touch target spacing - Accept Touch Target Spacing pending technique creation
- WCAG 2.2 Error Correction (was Confirm before submission): https://www.w3.org/2002/09/wbs/35422/wcag22-confirm-before-submission/ - Accept Error Correction as Amended (pending editorial updates)
- WCAG 2.2 Fixed reference points: https://www.w3.org/2002/09/wbs/35422/page-break-nav/ - Include accessible page location in 2.2. draft
24 March: AGWG extended meetings day 1
- Custom interactions: https://www.w3.org/2002/09/wbs/35422/Custom_interactions/results - Defer this SC
- Dragging: https://www.w3.org/2002/09/wbs/35422/wcag22-dragging/results - Include in the WCAG 2.2 draft, after understanding & techniques reviewed
- Touch target spacing: https://www.w3.org/2002/09/wbs/35422/target-spacing/results - Leave open
3 March: AG Working Group
- Publishing ACT Rules https://www.w3.org/2002/09/wbs/93339/PublishACTRules/results - Publish Rule "Image button has accessible name" as amended
- HTML Page LANG is valid https://act-rules.github.io/rules/bf051a - Publish rule "HTML page LANG is valid" as amended
- HTML lang and XML lang match - Publish "HTML lang and XML lang match" and "HTML page has LANG attribute"
- ID attribute value is unique - Not to publish until discussion about 4.1.1 is resolved for WCAG 2.2
18 February: Accessibility Guidelines working group
- WCAG 2.2 Information in steps https://www.w3.org/2002/09/wbs/35422/info-in-steps/results - Accept Success Criteria pending technique
- WCAG 2.2 Fixed Reference Points https://www.w3.org/2002/09/wbs/35422/page-break-nav/results - Leave open to address techniques
- WCAG 2.2 Dragging https://www.w3.org/2002/09/wbs/35422/wcag22-dragging/results - Leave open
- WCAG 2.2 Confirmation before submission https://www.w3.org/2002/09/wbs/35422/wcag22-confirm-before-submission/results - leave open
11 February: AG working group
- WCAG 2.2 hidden controls https://www.w3.org/2002/09/wbs/35422/silver-naming/results - Leave open, but almost ready
4 February: Accessibility Guidelines Working Group
- Silver naming - Accepting New Name for Silver
- WCAG 2.2 Findable help: https://www.w3.org/2002/09/wbs/35422/findable-help/ - Leave open
21 January: Accessibility Guidelines Working Group
- Important controls (re-review) https://www.w3.org/2002/09/wbs/35422/essential-controls/ - leave open
14 January: Accessibility Guidelines Working Group Teleconference
- ACT TF Work Statement https://www.w3.org/2002/09/wbs/35422/ACTTF_New_WorkStatement/results - Accepted and run CFC
- Adding a research aspect to SC requirements https://github.com/w3c/wcag/pull/1006 - Accepted as amended
- WCAG 2.2 Accessible Authentication (re-review) https://www.w3.org/2002/09/wbs/35422/accessible-auth/results - SC Text is ready for external review, need to finalize understanding and build techniques to get this SC into the editor's draft.
- WCAG 2.2 Important controls (re-review) https://www.w3.org/2002/09/wbs/35422/essential-controls/results - Leave open

2019

17 December: Accessibility Guidelines Working Group Teleconference
- WCAG 2.2 Confirmation before submission (2nd week). https://www.w3.org/2002/09/wbs/35422/wcag22-confirm-before-submission/results - leave open
- WCAG 2.2 Visual indicators https://www.w3.org/2002/09/wbs/35422/Visual_indicators/results - Leave open
- WCAG 2.2 Custom interactions https://www.w3.org/2002/09/wbs/35422/Custom_interactions/results - Leave open
10 December: Accessibility Guidelines Working Group Teleconference
- Non-text contrast update https://www.w3.org/2002/09/wbs/35422/ntc-updates-dec-2019/results - Publish PR 931 as amended
29 October: Accessibility Guidelines Working Group Teleconference
- ACT survey on new rule https://www.w3.org/2002/09/wbs/35422/ACT-Rules_Oct2019/results - The rule with the iframe change as discussed will be published Thursday and further comments will be routed through the taskforce for updates.
- WCAG 2.2 Criteria review – Icon Description https://www.w3.org/2002/09/wbs/35422/icon-desc-acceptance/results - Leave open
22 October: Accessibility Guidelines Working Group Teleconference
- WCAG 2.2 Criteria review – Focus Visible (Enhanced) (2nd week) https://www.w3.org/2002/09/wbs/35422/focus-vis-enh-acceptance/results - Resolved to include in the WCAG 2.2 editors draft.
- WCAG 2.2 Criteria review – Essential controls. (2nd week) https://www.w3.org/2002/09/wbs/35422/essential-controls/results - put on hold
15 October: Accessibility Guidelines Working Group Teleconference
- WCAG 2.2 Criteria review – Focus Visible (Enhanced) (2nd week) https://www.w3.org/2002/09/wbs/35422/focus-vis-enh-acceptance/results - leave open
1 October: Accessibility Guidelines Working Group Teleconference
- Failure technique for 1.3.5 https://www.w3.org/2002/09/wbs/35422/MiscItems09022019/results - Accept pull request 890 as ammended on call
19 September: Accessibility Guidelines Working Group Teleconference
- Custom Interactions - More work will be required on this SC.
- Page break navigation - continue working on page break navigation
- Page Break Locators - Continue working on page break locators
- Information In Steps - Leave Open
- Information in steps - Looking for additional use cases.
- Visible Labels - Review questions, update document.
- Orientation (Enhanced) - Compare to previous understanding update, bring that and the SC back for consideration
- Dragging - Need more examples, need to think about the questions.
18 September: Accessibility Guidelines Working Group Teleconference
- Silver topics - Accept conformance model noting Jemma's Condition
10 September: Accessibility Guidelines Working Group Teleconference
- Small errata for 1.4.10 reflow https://www.w3.org/2002/09/wbs/35422/SeptemberErrata/ - Accept erratum as proposed
- 1.3.5 failure - Do not accept 1.3.5 failure technique as proposed
- Failure for 2.5.1 - accepted as amended.
- Failure for 2.5.4 - accepted as amended
3 September: Accessibility Guidelines Working Group Teleconference
- Adding exceptions to F40, F41, F54, F58, and (new) F95 - Accept Pull Request #879.
- Failure of Success Criteria 1.4.12 due to clipped or overlapped content when text spacing is adjusted - Accept 881 Failure of Success Criteria 1.4.12 due to clipped or overlapped content when text spacing is adjusted
27 August: Accessibility Guidelines Working Group Teleconference
- 1. Failure of Success Criterion 4.1.3: Status Messages #853 - Accepted as amended.
20 August: Accessibility Guidelines Working Group Teleconference
- WCAG 2.1 Techniques and Understanding survey (https://www.w3.org/2002/09/wbs/35422/AGWG_T_U_Aug2019/) - leave open
- Errata, glossary definition for "images of text" #264 - Clarify in Understanding doc 143. Reject pull request 777.
- Failure of Success Criterion 4.1.3: Status Messages #853 - leave open
- Updating Understanding 1.4.11 Text Spacing #860 - accepted as amended
- Adding extra paragraph to F94 for issue 854 #863 - accepted as amended
13 August: Accessibility Guidelines Working Group Teleconference
- Updating Understanding 1.3.3 Sensory Characteristics #767 - Accept PR 767 ammended to keep F26
- Errata, Motion actuation #733 - On hold pending further comments
- Errata, glossary definition for "images of text" #264 - On hold pending comments from people dis-agreeing.
- Updating pause-stop-hide-understanding #778 - Accept PR 778
- DHTML roadmap techniques? #289 - Accept PR 779
- Updating an example for buttons. #813 - Accept PR 813
6 August: Accessibility Guidelines Working Group Teleconference
- WCAG 2.1 Techniques and Understanding survey https://www.w3.org/2002/09/wbs/35422/AGWG_T_U_Aug2019/ - Accept questions 3 to 5 as unanimously agreed
- Motion actuation failure technique - On hold
- Second item on survey - Accept PR 843 as amended
30 July: Accessibility Guidelines Working Group Teleconference
- Holiday calls - no calls September 24th, December 24th, and December 31st.
- Updates to WCAG 2.1 SCs in 2.2 https://www.w3.org/2002/09/wbs/35422/updating-wcag2-requirements2/results - WG agrees that updating SC is a possible option. But no decision was made on updated on SC 1.4.10 at this time.
- Technique remap or turn off character key shortcuts - Accepted as proposed.
- Must the visible label of site logos be in the accName #722 - Leave open
- h57, h58 and xml:lang - Accepted as amended.
- F63 shouldn't indicate use of preceding heading to meet 2.4.4 #819 - Accepted as proposed.
- Non-text contast - Adjacent colors and example clarifications. #681 - accepted as proposed.
- Errata, add advice to Large scale (text) > Note 1 in the glossary #228 - Reject PR so that this is not an errata, but rather put the change in the Understanding document
- Must the visible label of site logos be in the accName #722 - Accept as amended
- Updating Understanding 1.3.3 Sensory Characteristics #767 - Leave open
- H80 Example 3 needs updating #233 - Accept as amended
23 July: Accessibility Guidelines Working Group Teleconference
- Failure of 2.5.2 - Publish PR 815 as ammended
- G131 Test Procedure - Accept Jake’s suggestion as amended and create a pull request
- 3. Are Reflow, Text Size and Orientation cumulative? #391 - Accept the proposed response to 391
- Change to normative text of 1.4.12: at least > up to #637 - leave open
- Expand 1.4.10 to apply 'down to' instead of 'at' #698 - Leave open pending survey.
- ARIA in HTML conformance to conform WCAG ? #717 - Accept q 6 and 7 as proposed.
16 July: Accessibility Guidelines Working Group Teleconference
- Updating WCAG 2.x requirements: https://www.w3.org/2002/09/wbs/35422/updating-wcag2-requirements/results - Choose Option 2 for focus visible SC
- Control Orientation - Approve Tech Control Orientation as amended
- Tech Failure Doorslam - Accept Tech Failure Doorslam
- Providing a control slider that offers single point activation - Accept PR 760 Providing a control slider that offers single point activation
9 July: Accessibility Guidelines Working Group Teleconference
- Technique - Content on focus or hover - accepted as amended pending changes to use of popup.
- Technique - Failure of character key shortcuts - accepted as amended
- Technique - Two color focus indicator #583 - Accepted as amended
- Issues resolution https://www.w3.org/2002/09/wbs/35422/issues-2019-07/ - Accept numbers 1, 2, and 4 as proposed.
- Is H33 still valid #305 - Accept response to #305 and leave H33 in place
- G131 Test Procedure #339 - Leave G131 open
25 June: Accessibility Guidelines Working Group Teleconference
- Charter discussion - WG agrees to update the charter to include Silver but not including REC and to use that draft as the Wide Review Charter draft
- Technique - Tech Control Orientation - Leave open Tech control orientation
- Technique - Tech Failure Doorslam - Leave open Tech Failure Doorslam
18 June: Accessibility Guidelines Working Group Teleconference
- WCAG 2.2 requirements - Accept requirments document as ammended
- accessible authentication - Continue with the Accessible Authentication SC
- Touch Target Spacing - There are questions about the testability that need further work
- WCAG 2.1 Techniques, 1st question only. https://www.w3.org/2002/09/wbs/35422/Techniques-June-2019/results - Accepted as amended
- WCAG 2.x issue resolutions, 1-5 only https://www.w3.org/2002/09/wbs/35422/Tech_Und_survey/ - Accept as amended.
- Public comment: Security implications of autocomplete - Accept PR as amended
- 3. SC note and understanding update: Orientation (Issue 416 / PR 724) - Accept PR 724
- Public comment: Adding weight/typeface to the contrast test (Issue 665) - Accept proposed response
- Public comment: Maximum contrast (Issue 675) - Accept response to 675
11 June: Accessibility Guidelines Working Group Teleconference
- WCAG 2.1 Techniques survey: https://www.w3.org/2002/09/wbs/35422/Techniques-June-2019/results - Approve PR 714 as amended
- Two color focus indicator #583 - Leave open
4 June: Accessibility Guidelines Working Group Teleconference
- Path Based Gestures - the approach is agreed-upon and it will be written up
- Understanding update: Reflow doc referencing 1.4.4 (PR 715) - accept pull requests 715
- Motion Actuation (PR 693) - accept PR 693
- Non-text contrast (PR 701) - accept PR 701
- Should non-drafted techniques be included? - Michael Cooper to compile a list of the techniques that were deleted.
- Bypass blocks (PR 721) - Accept PR 721
28 May: Accessibility Guidelines Working Group Teleconference
- Pointers gestures clarification path base gestures. - The WG intended that path-based gestures in 2.5.1 does not include gestures that only depend on the start and end points.
21 May: Accessibility Guidelines Working Group Teleconference
- WCAG 2.1 techniques overview - Complete 2.1 techniques before TPAC
- New technique: Failure technique for 2.5.6 Concurrent Input Mechanisms (PR 690) - Leave open pending Mike Gower and Patrick working on comments
- New technique: Using native controls to ensure up events (PR 726) - Accept PR 726 as amended
14 May: Accessibility Guidelines Working Group Teleconference
- Failuretechniques for input mechanisms - leave open pending updates
- New technique: Using native controls to ensure up events (PR 726) - Leave open pending updates.
- Understanding update: Pointer Gestures clarity (PR 714 / 725) - Leave open pending updates
- Understanding update: Content on Hover or Focus (Issue 605) - Accept pull request 73 as ammended
7 May: Accessibility Guidelines Working Group Teleconference
- Silver requirements update - WG is happy with the updated to the silver requirements and we will do a CFC
- Pull Request 649: General techniques for label in name - Accept as amended from survey responses.
- Pull Request 531: Semantically identifying a font icon with role="img" - Accept pending edits form the survey as well as the additions to the second paragraph from the call.
30 April: Accessibility Guidelines Working Group Teleconference
- 522: Pointer Gestures: clarity on path-based language in Understanding document - Except respons and create PR
- Issue 687: Non-text contrast - Adjacent colors and example clarifications. - Remove " or selecting a close button" from the Understanding document, create a PR and then post the official response
- Pull request 658 - Accept pull request 672
23 April: Accessibility Guidelines Working Group Teleconference
- Design Principles - Accept Design Principles as amended, pending changes we've discussed
- Requirements - Accept requirements as amended
- Requirements - Accept requirements as amended, send to CFC. Some concerns noted.
9 April: Accessibility Guidelines Working Group Teleconference
- New Technique for Device Motion Actuation - Leave open.
- Issues resolutions - Accept issues 638, 652, 660, 671, and 678 as unanimous.
- New Techniques for Label in Name - separate techniques
2 April: Accessibility Guidelines Working Group Teleconference
- TPAC 2019 (https://www.w3.org/2002/09/wbs/35422/AGWG_TPAC_2019/results) - WG will meet at TPAC
26 March: Accessibility Guidelines Working Group Teleconference
- Issues survey https://www.w3.org/2002/09/wbs/35422/technique-approvals9/results | - Accept items 1 3 4 and 5 as proposed due to unanimous concent.
- Issues survey https://www.w3.org/2002/09/wbs/35422/technique-approvals9/results | - Accept proposed response to issue 593.
- Issues survey https://www.w3.org/2002/09/wbs/35422/technique-approvals9/results | - Accept pull request 664.
11 March: Accessibility Guidelines Working Group Teleconference
- Design Principle 1 - Jeanne/Shawn to clarify “intersectional” and think about a glossary.
- Design Principle 2 - Overall agreed on the design principle itself. But need to make the including statement more inclusive.
- DESIGN PRINCIPLE 3 - accepted
- Design 4 - Move (later) to requirements.
- Design Principle 5 - In agreement this is a good thing to have. More points to consider in how you would measure if this were a requirement, but it is a principle.
- Design Principle 6 (moving to creation process for the guidelines) - We have agreement that this is an important principle. There is room for clarification.
- Design Principal 7 - We have agreement on this principle, with possible wording tweaks
- Design Principle 8 - We are in agreement, with the caveat to not let data-driven process exclude minority groups of people with disabilities
- Additional principles - The Silver group will discuss a new Design Principle
- Requirement 1 - Silver will check in with the group to make sure that additions to this requirement are incorporated.
- Flexible structure - Shift in focus of framing from structure to maintenance model so we can include process and terms for inclusion
- Multiple ways to display - Largely agreed, but we have notes of what to change
- Technology neutral - agreed with some minor wording changes
- Readability/Usability - Language needs to be tweaked to clarify scope and working with experts in plain language for how we would measure success
- Regulatory Environment - Agreed on the main purpose, but have to work through some solid discussions
5 March: Accessibility Guidelines Working Group Teleconference
- Issue Survey https://www.w3.org/2002/09/wbs/35422/technique-approvals8/results (#4 only) - Accept as amended pending changes described on the call
- F3 - Andrew will investigate Pull Request 120
26 February: Accessibility Guidelines Working Group Teleconference
- Issue 538 - Accept response as proposed.
- Issue 538 - Accepting items 5-8.
- New Technique: Boundary contrast - Accept as amended.
- New Technique: Boundary contrast - Accepted as amended.
19 February: Accessibility Guidelines Working Group Teleconference
- Issue 619 - leave open
- Issue 618: definition of presentation in SC 1.3.1 - accepted as proposed
- Issue 613: 1.3.4 Orientation - applicability to native apps - accepted as proposed
- Issue 612: Fixes to WCAG 2.1 Understanding 2.4.6 and 3.3.2 - accepting as amended with Rachels change
- Issue 599: Is using the track element to provide audio descriptions sufficient? (Was "Retire H96?") - accepting as proposed
- ERRATA – Issue 582: 1.4.13 Content on Hover or Focus - hoverable requirement, clarification of point "persistent" - Alastair and Andrew will add response on basis of Mike Gower's response
- Issue 581: Misleading info in "Understanding 2.4.4: Link Purpose (In Context)" - accept as proposed
12 February: Accessibility Guidelines Working Group Teleconference
- Errata Links to Understanding docs - Accept Issue 595
- Errata Better Link Text - Accept response for issue 608
- Issue 540 - Accept Issue 540
- Issue 602 - Accept Issue 540
- Issue 538 - Leave open Issue 538
- Issue 165 - Accept pull request 604
- Retire H96 - Keep H96 ammended by note
- Feedback on approach to Issue 610 - accept PR 606 as erratum, as amended
5 February: Accessibility Guidelines Working Group Teleconference
- Errata - Update Content on Hover or Focus - Leave open. Mike will work on understanding doc.
- Remove technique: H4: Creating a logical tab order... - Remove H4
- Issue 544 on Autocomplete - Accepted as amended.
29 January: Accessibility Guidelines Working Group Teleconference
- Issue 568 - Accept pull request 568
- Issue 568 - Accept pull request 575
- Technique in 584 - Leave open
- Technique in pull request 455 - Publish as amended.
22 January: Accessibility Guidelines Working Group Teleconference
- Issue 567 - Labels of inactive inputs - accepted as proposed
- Issue 538 - modal on load failure - Leave open
- Issue 400 - SC 1.4.11 contrast on hover included or not - accepted a proposed
15 January: Accessibility Guidelines Working Group Teleconference
- Understanding update Non-text Contrast - Accepted as amended pending final edits by Alastair
- Technique Border Contrast - Leave Open
8 January: Accessibility Guidelines Working Group Teleconference
- AccName update - CfC accepted without objection, publish PR 555
- Technique Reduce Motion - Accept as amended

2018

18 December: Accessibility Guidelines Working Group Teleconference
- Understanding non-text contrast update - SC 1.4.11 does not require differentiation inside the component between states
- Failure due to locking the orientation to landscape or portrait view - Accept pull request 545
- Technique for reducing motion/sc 2.3.3 - Leave pull request for reducing motion open
11 December: Accessibility Guidelines Working Group Teleconference
- Understanding Update Non-Text COntrast - Leave open and send email to list for thoughts on feedback
- Technique Icon Contrast - Accepted as amended pending image change
27 November: Accessibility Guidelines Working Group Teleconference
- Technique: Ensure the "accessible name" includes the visible text - Address comments in the survey.
- Technique: Using CSS width, max-width and flexbox to fit labels and inputs - Accept Issue 456 as ammended
- Ensuring that drag-and-drop actions can be cancelled - Accepted as proposed.
- Technique: Failure due to "accessible name" not containing the visible label text - Keep open
- Technique: Failure of Success Criterion 1.4.13 due to content shown on hover or focus not being hoverable - Accepted as amended
- Failure due to "accessible name" - Accepted as amended
20 November: Accessibility Guidelines Working Group Teleconference
- Type attribute for purpose - Input type is not sufficient for identifying purpose, understanding document to be updated
- Bad link in G158 Edit - Remove link from G158
- Understanding update Non text contrast, clarifying active state - Accept pull request 530.
13 November: Accessibility Guidelines Working Group Teleconference
- Technique for media queries for sticky elements - Accept pull request 389 as amende
- Tech spacing override - To publish 386 as amended
- Technique fitting images viewport - Accept pull request 494 as amended
- Technique fitting images viewport - Accept pull request 495 subject to future discussion
6 November: Accessibility Guidelines Working Group Teleconference
- TPAC update: https://www.w3.org/WAI/GL/wiki/Write_up_from_TPAC_2018 - Chairs will codify editor requirements and publish them
- TPAC update: https://www.w3.org/WAI/GL/wiki/Write_up_from_TPAC_2018 - Chairs will finish any minor edits and routed the CFC for the decision policy.:
22 October: Accessibility Guidelines Working Group Teleconference
- Process Update Discussion - Incorporate the feedback from today into another iteration of the AGWG process comments
16 October: Accessibility Guidelines Working Group Teleconference
- PR 516 - Editorial, Editors will resolve
- PR 515 - accepted as proposed
9 October: Accessibility Guidelines Working Group Teleconference
- Understanding text-spacing, stylish to stylus update - Publish PR487
- Technique: wrapping long URLs for reflow - Publish PR486 as amended
- Technique: wrapping long URLs for reflow - Publish PR486 as amended
- Technique: media queries for sticky elements - Leave open, finalize next time.
- Technique: failure for hover / focus content not dismissable - leave open and detlev will think about improving procedure or convert to success technique.
2 October: Accessibility Guidelines Working Group Teleconference
- Pointer Gestures - accept PR484 as amended
- Tech using role log - accept PR435 as amended
25 September: Accessibility Guidelines Working Group Teleconference
- Technique F87 - Accepted as amended
- updated technique example for SCR29 - accepted changes to SCR29 as proposed
- https://github.com/w3c/wcag/issues/460 (an editorial errata?) - accepted proposal two as editworial errata on principle three
4 September: Accessibility Guidelines Working Group Teleconference
- Techniques and Understanding updates survey https://www.w3.org/2002/09/wbs/35422/TechniquesforApproval/ - except for publication PR387 as amended
- Using CSS Flexbox to reflow - publish PR388 as amended
- Failure of viewport units, is ready - publish PR417 as amended
- Understanding Text Spacing: Removed fixed text example. - publish PR385 as amended
28 August: Accessibility Guidelines Working Group Teleconference
- Autocomplete - Publish the autocomplete technique as amended
21 August: Accessibility Guidelines Working Group Teleconference
- Update to 1.3.5 Understanding doc, Survey: https://www.w3.org/2002/09/wbs/35422/TechniquesforApproval/results - publish understanding 135 after removing related resources comment and fixing the error Mike Gower identified
7 August: Accessibility Guidelines Working Group Teleconference
- Techniques needing work/review - Pull request 431 has more than 5 approvals and will be decided next meeting.
31 July: Accessibility Guidelines Working Group Teleconference
- Marking WCAG 1.0 Obsolete. - Michael will check with Judy and we will send the CFC after that about whether to obsolete WCAG 1.0
- Reviewing open issues - https://github.com/w3c/wcag/issues/433 - Leave open for input from LVTF and COGA.
- Reviewing open issues - https://github.com/w3c/wcag/issues/433 - leave open for input from LVTF and COGA
- Reviewing open issues - https://github.com/w3c/wcag/issues/425 - Leave open and JF to investigate and update Understanding.
- Reviewing open issues - https://github.com/w3c/wcag/issues/420 - Accept issue 420 as editorial errata
24 July: Accessibility Guidelines Working Group Teleconference
- Errata update - MC will run the list by the group as a CFC
17 July: Accessibility Guidelines Working Group Teleconference
- Drag and Drop in Pointer SC - Accept proposed response and pull request 379.
5 June: Accessibility Guidelines Working Group Teleconference
- Techniques & Understanding docs process - No more Thursday calls are planned.
- Issue resolution: 913 & 914 (Non-text contrast understanding doc) - accept proposed response for 914
31 May: Accessibility Guidelines Working Group Teleconference
- Understanding changes and CFC - Editor's to included note in 1.4.11 if language changes, and also to try to reach consensus on changes beforehand (thus eliminating the need for the note)
29 May: Accessibility Guidelines Working Group Teleconference
- Publishing Understanding - Accept change to 1.4.11 Non-text contrast in order to better reflect the intent of the WG, and propose change to W3M.
- Publishing Understanding - send out CFC for publication of understanding documents with the rec
24 May: Accessibility Guidelines Working Group Teleconference
- https://www.w3.org/2002/09/wbs/35422/Understanding_Updates5/results - Accepted as proposed
- Issue 903 Abstract - accept edited version posted at by AWK at 11:45am central time
22 May: Accessibility Guidelines Working Group Teleconference
- Understanding Orientation - accept pull request 922 as amended
- Non-text contrast - accept Pull Request 924 subject to updating graphical examples
- CHanges to understanding timeouts - Accept pull request 925 as ammended.
- Identify Purpose - accept pull request 929 as ammended.
17 May: Accessibility Guidelines Working Group Teleconference
- Understanding Orientation - Accepted PR 922 as ammended by the comments
15 May: Accessibility Guidelines Working Group Teleconference
- Changes to Understanding Concurrent Input Mechanisms - Accepted as amended
- Changes to Understanding Concurrent Input Mechanisms - Accepted Concurrent Input Mechanisms and merge 915 as amended
- Changes to Understanding Orientation - Accept pull request 916 as amended (Orientation) with the understanding that further edits are needed for the "functionality" question
- Motion Actuation - Accept pull request #917
- Status Messages - Accept pull request #918 as amended
10 May: Accessibility Guidelines Working Group Teleconference
- Changes to Understanding Text spacing - Accept pull request 905 as amended.
- Changes to Understanding Content on Hover or Focus - Accept pull request 906 as amended.
- Understanding Animation from Interactions - Accept pull request 907 as amended
- Changes to Understanding Character Key Shortcuts - Accept implementing the changes discussed and not withdrawing the pull request
- Understanding Target Size - Accept pull request 908 as amended
- Understanding Pointer Gestures - Accept pull request 909 as amended
8 May: Accessibility Guidelines Working Group Teleconference
- Changes to Understanding conformance - Merge pull request 543
- Changes to Understanding conformance #2 - Leave open.
- Changes to Understanding conformance #2 - Accept pull request.
- Changes to Understanding conformance #2 - to accept pull request
- Changes to Understanding conformance #2 - Accept pull request
- Understanding Label and Name - Merge pull request 897
- Understanding conformance #2 - merge PR 545
3 May: Accessibility Guidelines Working Group Teleconference
- Issue 850 (https://github.com/w3c/wcag21/issues/850) - Kathy and Jon and David (mike gower offered to review) will take a crack at understanding changes for the group.
12 April: Accessibility Guidelines Working Group Teleconference
- Issue 773 - Accept response to 773 as proposed
- SC reorg - Accept proposal with ammendment to move character key shortcuts to 2.1
- SC reorg - Working group approves leaving some or all of the SC in place if there are deemed to be too many changes by the director for the transition.
- Edits to Intro - Accept changes to introduction as ammended
- Edits to Intro - Move to PR with contingencies
10 April: Accessibility Guidelines Working Group Teleconference
- Survey on At Risk items: https://www.w3.org/2002/09/wbs/35422/AtRiskItems/results - Do not take the CR ¨at risk¨ action to remove SC 1.3.5
- At risk SC 1.4.11 Non-text Contrast - Do not take the CR at risk action to remove SC 1.4.11
- At risk SC 1.4.11 Non-text Contrast - Do not take the CR at risk action to remove SC 2.2.7
- Issues survey https://www.w3.org/2002/09/wbs/35422/CloseCRIssues/results - Accept all comment responses in survey as proposed
3 April: Accessibility Guidelines Working Group Teleconference
- 839 - Accept response for 754 and use for 839 also
- 836 - 844 accepted as proposed.
- 827 - Accepted as amended
- 827 - 829 proposed response accepted as proposed
20 March: Accessibility Guidelines Working Group Teleconference
- 808 - follow up with Steve about proposed response and report back
- 805 - defer issue to silver, clarify definition in 143, 146, 1411 Understanding.
- 763 - note that is in 251 should also be used in 252. and change Pointer Gestures to Pointer Inputs in both SC
- 778 - Accept response as amended in https://github.com/w3c/wcag21/issues/778#issuecomment-374672047
- Non-text contrast - accept Glenda's edit to 1.4.11 understanding https://github.com/w3c/wcag21/blob/non-text-contrast/understanding/21/non-text-contrast.html
- Issue 772 - label issue 772 for future understanding work.
- 803 - working group decides to move the list into an appendix of wcag 2.1 unless that change contravenes cr status.
- 806 - add "and physical reactions" and corresponding change to the GL text language "or physical reactions" and adding 2.2.7 Animation from Interactions to GL 2.3 providing this does not contravene CR.
19 March: Accessibility Guidelines Working Group Teleconference
- https://github.com/w3c/wcag21/issues/753 - Accepted as proposed
- https://github.com/w3c/wcag21/issues/753 - Accepted as proposed - Issue #754 - with AWK edits
- https://github.com/w3c/wcag21/issues/753 - Accepted as proposed - Issue #753
- https://github.com/w3c/wcag21/issues/753 - Leave Open - Issue #753 - for review by Chris McM, Patrick
- https://github.com/w3c/wcag21/issues/753 - Leave Open - Issue #753 - for review by Chris McM, Patrick
- issue 765 - Change SC title to Status Messages, and follow up with commenter about changes
- issue 765 - Change SC Title to Status Message (including loading) and follow up with commenter about response - Issue #765
13 March: Accessibility Guidelines Working Group Teleconference
- Possibly moving 1.3.4 https://github.com/w3c/wcag21/issues/768 - CFC for not moving 1.3.4
- Possibly moving 3.2.6 https://github.com/w3c/wcag21/issues/802 - Move 3.2.6 to 4.1.3 (CFC)
- Understanding Pointer Cancellation - https://www.w3.org/2002/09/wbs/35422/Clearing_Understanding/#wbsq13 - Merge Pointer Cancellations into editors draft.
- Understanding Motion Actuation - https://www.w3.org/2002/09/wbs/35422/Clearing_Understanding/#wbsq16 - leave open
- Understanding Concurrent Input Mechanisms - https://www.w3.org/2002/09/wbs/35422/Clearing_Understanding/#wbsq14 - Leave open
- Understanding Character Key Shortcuts - https://www.w3.org/2002/09/wbs/35422/Clearing_Understanding/#wbsq9 - Leave open.
- Understanding Non-text Contrast - https://www.w3.org/2002/09/wbs/35422/Clearing_Understanding/#wbsq4 - Merge into editors draft.
8 March: Accessibility Guidelines Working Group Teleconference
- comment on reflow https://github.com/w3c/wcag21/issues/757 - 757 will become the official response
13 February: Accessibility Guidelines Working Group Teleconference
- Survey for ACT TF: https://www.w3.org/2002/09/wbs/35422/ACT_draft_review2018/ - Permission to publish draft of rules format and updated demo rules site.
- 761 - Accepted as proposed
- 760 - Accept as amended
- 759 - Accept response as amended
- 758 - Accept response as amended
- 756 - Accept response as amended
6 February: Accessibility Guidelines Working Group Teleconference
- Issue 745 - https://github.com/w3c/wcag21/issues/745 - Accepted as proposed.
- Issue 744 - https://github.com/w3c/wcag21/issues/744 - Accept as amended
- Issue 746 - https://github.com/w3c/wcag21/issues/746 - Accept as amended. Includes link back.
- Issue 747 - https://github.com/w3c/wcag21/issues/747 - Accepted as amended.
- Issue 733 - https://github.com/w3c/wcag21/issues/733 - Accepted as amended
23 January: Accessibility Guidelines Working Group Teleconference
- Wrapping up CFCs - mark the following SC “at risk” animations, non-text contrast and identify common purpose
16 January: Accessibility Guidelines Working Group Teleconference
- leave open 1.3.4
- Target Size Proposals - leave open Target size.
- Graphics Contrast - Leave open
- Text spacing - Accepted as ammended with exception language
- reflow - Leave open
- pointer gestures - Reissue CFC with updated definition
11 January: Accessibility Guidelines Working Group Teleconference
- Reflow survey: https://www.w3.org/2002/09/wbs/35422/resolving_issues_reflow/results - accept response to Issue 589 as proposed
10 January: Accessibility Guidelines Working Group Teleconference
- issue 296 & 315 glossary items - not modifying definitions
- Issue 620 - leave open
- issue 622 - accept as amended "Ensure that device sensor inputs are not a barrier for users"
- 631 - Send option 2 out to CFC.
9 January: Accessibility Guidelines Working Group Teleconference
- Issue 408 - Accepted as amended
- Issue 520 - Leave open.
- Issue 605 - Accepted as amended
- Issue 656 - Accepted as proposed
- Issue 656 - accepted as amended
2 January: Accessibility Guidelines Working Group Teleconference
- 150 - accept 150 response
- 619 - accept 619 as amended
- 620 - Accept 619 with additional edits.
- 620 - leave 620 -22 open
- 630 - accept 630 as amended
- 631 - Leave open, will get back to it later
- 624 - Leave open pending JF edits.
- Comment about needing an identifier for common control concepts - Add an identifer for each common purpose

2017

21 December: Accessibility Guidelines Working Group Teleconference
- Interruptions (minimum): https://www.w3.org/2002/09/wbs/35422/interruptions-minimum-review/results - No consensus
- Accessible Authentication: https://www.w3.org/2002/09/wbs/35422/Accessible-authentication-review/results - Accept as amended at AAA
- Contextual information: https://www.w3.org/2002/09/wbs/35422/Contextual_Information_review/results - Accepted as amended at https://www.w3.org/WAI/GL/wiki/1-3-5_Revision
- Animation from Interactions: https://www.w3.org/2002/09/wbs/35422/animation_from_interaction_review/results - Accepted as amended at ##:36 by Alastair
19 December: Accessibility Guidelines Working Group Teleconference
- Interruptions (minimum): https://www.w3.org/2002/09/wbs/35422/interruptions-minimum-review/results - Leave open
- Accessible Authentication: https://www.w3.org/2002/09/wbs/35422/Accessible-authentication-review/results - Leave open
14 December: Accessibility Guidelines Working Group Teleconference
- Contextual information: https://www.w3.org/2002/09/wbs/35422/Contextual_Information_review/results - Leave open
- Resolving issues: https://www.w3.org/2002/09/wbs/35422/resolving_issues_1/ - Accept 602, 608, 616, 617, 618 as proposed
- 601 - Accepted as amended.
- 609 - 609 accepted as amended
- Animation from Interactions: https://www.w3.org/2002/09/wbs/35422/animation_from_interaction_review/results - Leave open, Alastair will propose amended text
7 December: Accessibility Guidelines Working Group Teleconference
- Understanding Document Work - Publish Dec 7 Wide Review Working Draft and Understanding
30 November: SV_MEETING_TITLE
- accidental activation (https://github.com/w3c/wcag21/pull/595) - Accepted for CFC as proposed in pull request 595
- Content on Hover or Focus (https://www.w3.org/2002/09/wbs/35422/ContentHoverFocus_20171109/results) - accept for CFC based on pull request #569
- Common Input Control Purposes - leave open pending comments to list by 1130 tomorrow
- Device Sensors (https://www.w3.org/2002/09/wbs/35422/resolving_device_sensors/results) - accepted as amended above for Device Sensor
29 November: Accessibility Guidelines Working Group Teleconference
- Purpose of Controls https://www.w3.org/2002/09/wbs/35422/resolving_purpose_of_controls/results - WG agrees that list should be NORMATIVE!
- Purpose of Controls https://www.w3.org/2002/09/wbs/35422/resolving_purpose_of_controls/results - to spend 5 minutes tomorrow to finish this SC
28 November: Accessibility Guidelines Working Group Teleconference
- Change of Content https://www.w3.org/WAI/GL/wiki/Comment_Summary_3-2-7 - Leave open for more work
- Target Size (AA) https://www.w3.org/2002/09/wbs/35422/resolving_target_size/results - Accepted as amended at https://www.w3.org/WAI/GL/wiki/index.php?title=WCAG_2.1/targets&oldid=8767#Alternative_Wording
- Target Size (AA) https://www.w3.org/2002/09/wbs/35422/resolving_target_size/results - Open issue for implementation follow up
- accepting comment responses for Target size - Accept responses to comments for Target Size at https://www.w3.org/WAI/GL/wiki/WCAG_2.1/targets#Comment_responses as proposed
- AAA Target size - Accept AAA as amended
- AAA Target size - leave open
27 November: Accessibility Guidelines Working Group Teleconference
- Device Sensors https://www.w3.org/2002/09/wbs/35422/resolving_device_sensors/results - leave open
- adapting text https://www.w3.org/WAI/GL/wiki/Comment_Summary_1-4-13 - Accept SC text as proposed https://www.w3.org/WAI/GL/wiki/Comment_Summary_1-4-13 and comment responses as proposed
- Accidental Activation https://www.w3.org/WAI/GL/wiki/Comment_Summary_2-5-2 - leave open
- Change of Content https://www.w3.org/WAI/GL/wiki/Comment_Summary_3-2-7 - Leave open
21 November: Accessibility Guidelines Working Group Teleconference
- Target Size https://www.w3.org/2002/09/wbs/35422/resolving_target_size/results - leave open
- Purpose of Controls - Accept SC in principle
- Purpose of Controls - Leave Open
20 November: Accessibility Guidelines Working Group Teleconference
- Content on Hover and Focus https://www.w3.org/2002/09/wbs/35422/ContentHoverFocus_20171109/results (40 minutes) - Leave open
- Orientation (20 minutes) - Accept SC language as amended.
- Pointer Gestures https://www.w3.org/2002/09/wbs/35422/resolving_pointer_gestures/results (20 minutes) - SC language accepted as amended.
- Target Size https://www.w3.org/2002/09/wbs/35422/resolving_target_size/results (40 minutes) - Leave open.
17 November: Accessibility Guidelines Working Group Teleconference
- https://www.w3.org/2002/09/wbs/35422/resolving_pointer_gestures/results - SC accepted as amended and put to CFC
- https://www.w3.org/2002/09/wbs/35422/resoling_orientation/results - Accept comment responses to 2.5.1
- Orientation SC - Accept SC text as proposed.
- Orientation SC - Accept responses to issues.
16 November: Accessibility Guidelines Working Group Teleconference
- https://www.w3.org/2002/09/wbs/35422/Resolving_Timeouts/results - No consensus
15 November: Accessibility Guidelines Working Group Teleconference
- Graphics Contrast and UI Component Contrast: https://www.w3.org/2002/09/wbs/35422/Graphics_and_UI_Contrast20171109/results - Add definition for state “a dynamic property expressing characteristics of a user interface component that may change in response to user action or automated processes. States do not affect the nature of the component, but represent data associated with the component or user interaction possibilities. Examples include focus, hover, select, press, check, and expand/collapse”
- Graphics Contrast and UI Component Contrast: https://www.w3.org/2002/09/wbs/35422/Graphics_and_UI_Contrast20171109/results - Add definition for state “a dynamic property expressing characteristics of a user interface component that may change in response to user action or automated processes. States do not affect the nature of the component, but represent data associated with the component or user interaction possibilities. Examples include focus, hover, select, press, check, visited/unvisited, and expand/collapse
14 November: Accessibility Guidelines Working Group Teleconference
- Zoom Content: https://www.w3.org/2002/09/wbs/35422/ZoomContent_20171109/results - SC criteria accepted as is, with 1 objection
- Responses to comments https://www.w3.org/2002/09/wbs/35422/ZoomContent_20171109/results - Accept proposed responses to survey as ammended.
- Graphics contrast - Leave Open, discuss tomorrow. Issue around borders, most can live with 3:1
- Graphics contrast - 3:1 ratio has been accepted.
7 November: Accessibility Guidelines Working Group Teleconference
- Interruptions Minimum - We leave Interruptions Minimum open
- Character Key Shortcuts - accept comments and amend understanding document per issue #451
- concurrent SC - Move Concurrent input to AAA
- concurrent SC - Accepted as amended
- concurrent SC - Accepted for next draft https://www.w3.org/WAI/GL/wiki/WCAG_2.1/targets
6 November: Accessibility Guidelines Working Group Teleconference
- Exit criteria - Accepted by the group
- Label in accessible name - Response to 557 accepted and posted
2 November: Accessibility Guidelines Working Group Teleconference
- Survey: https://www.w3.org/2002/09/wbs/35422/Misc_Oct31/results (only #3 on Candidate exit criteria) - leave open
- TPAC Decisions - Decision can be made at TPAC. We will group items with consideration to schedules, and do CFCs for spec changes
31 October: Accessibility Guidelines Working Group Teleconference
- Problem with Technique G131 - Defer for a later time
- Survey: https://www.w3.org/2002/09/wbs/35422/Oct_31_2017/ (#1 and #5) - accept as amended
- Survey: https://www.w3.org/2002/09/wbs/35422/Misc_Oct31/results - Accept as amended https://lists.w3.org/Archives/Public/w3c-wai-gl/2017OctDec/0283.html (Lisa objection)
- Conforming alternatve versions need labels - Handle through changes in understanding
- Candidate Rec Exit Criteria - Leave open talk about on Thursday.
26 October: Accessibility Guidelines Working Group Teleconference
- The rewrite of label in name needs images of text #484 - Leave open
- Response to Comment on 2.4.12 Accessible Name #477 - Accept items 2 and 4 as proposed
- 3. Suggested Grammar fix on User Interface components SC #513 - Accepted as proposed.
24 October: Accessibility Guidelines Working Group Teleconference
- Response to 327 - Leave open. SteveR and MikeG will review and report back.
- survey item 7, proposed response to changing handles on SC - accept response as ammended
- question 8 from survey, proposed response - leave open, AKW and AC will work
19 October: Accessibility Guidelines Working Group Teleconference
- Response to comment on 2.4.11 Character Key Shortcuts #501 - leave open until Tuesday so JF and James can discuss and find a solution
- UIC Contrast - Leave UIC Contrast discussion for TPAC
- Commit for Need an "AND" rather than "OR" in Purpose of controls #405 - Accept as proposed. Will ssend out CFC on this!
17 October: Accessibility Guidelines Working Group Teleconference
- Changes to Understanding document structure? - Benefits to now be a sibling of Intent
- SC Orientation Text: Locking is not the accessibility problem #509 - Accepted Content is operable in all display orientations supported by the user agent, except where display orientation is essential.
- Response to comment on Mitsue-Links Accessibility Dept. C 3.2.7 Change of Content: Avoid using the term "control" #506 - Accept David’s 2 edits.
10 October: Accessibility Guidelines Working Group Teleconference
- Implementation process (https://www.w3.org/2002/09/wbs/35422/WCAG21_impl/) - this was already surveyed but people wanted more time. - Leave open
- in graphics contrast - Alastair and Jason to wordsmith and send to list
- in graphics contrast - Leave open Alex and Alastair to clarify.
- in graphics contrast - Leave open Alex and Alastair to clarify.
- in graphics contrast - leave open, discuss 'essential' later
5 October: Accessibility Guidelines Working Group Teleconference
- Survey on Essential cases: https://www.w3.org/2002/09/wbs/35422/essential_breakout/ - Accept 2,4,5,7,9
- Survey on Essential cases: https://www.w3.org/2002/09/wbs/35422/essential_breakout/ - resolution to accept "In accessible authentication" as amended
- CONTENT on hover or Focus - leave open
3 October: Accessibility Guidelines Working Group Teleconference
- Requirement for PDF to Interactive - Accepted as proposed in github survey
- 4. And/or in SC2.2.7 Accessible Authentication #325 - Leave open until Lisa S available for discussion
- Success Criterion 3.2.7 Change of Content #365 - Proposed definition for Programatic Notification to go to CFC
- In Graphics Contrast - Leave open and come back on Thursday
- AGWG Work Items progress check in and sign-ups: https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3A%22AGWG+Work+item%22 - John Foliot to update the pull request
- AGWG Work Items progress check in and sign-ups: https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3A%22AGWG+Work+item%22 - Rachael to take on issue 403
- AGWG Work Items progress check in and sign-ups: https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3A%22AGWG+Work+item%22 - Jake Abma to take on issue 307
- AGWG Work Items progress check in and sign-ups: https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3A%22AGWG+Work+item%22 - Assign both 211 and 302 to John Foliot, with Andy Heath assisting on 302 and John Kirkwood assisting with 211
28 September: Accessibility Guidelines Working Group Teleconference
- PR for: Sync Accessible Name SC language with existing WCAG terminology #371 - Accepted as amended
- PR for:Use of "essential" #372 and comment #333 - Accepted #393
- PR for: Correct all uses of Essential - Leave open
- Use of the term 'easily available' https://github.com/w3c/wcag21/issues/373 (with Lisa) - leave open
26 September: Accessibility Guidelines Working Group Teleconference
- SC Numbering - Accept Michael's proposal on WCAG 2.1 numbering and IDs
- Resolving Issues Survey (https://www.w3.org/2002/09/wbs/35422/resolvingissues1/results) - Issues 154, 375, 157, 153 accepted as proposed
- Issue 379 - Accept as proposed, Issue 379
- Issue 373 - One or more concrete proposals needed for issue 373 - A mechanism is easily available
19 September: Accessibility Guidelines Working Group Teleconference
- Survey on SC ordering: https://www.w3.org/2002/09/wbs/35422/WCAG21_sort_order/results - leaving open
- Merging SC - set a goal that we want to avoid merging but not take it off the table entirely. case by case - file issue for specific mergings.
12 September: Accessibility Guidelines Working Group Teleconference
- 1) New SCs - To Merge or not to merge? Survey https://www.w3.org/2002/09/wbs/35422/SC_merge/ - Leave this open. Needs more discussion.
- 2) Implementation testing process - (https://www.w3.org/2002/09/wbs/35422/WCAG21_impl/). - Leave this open. Will discuss after more have answered the survey next week.
29 August: Accessibility Guidelines Working Group Teleconference
- ACT Rules Format draft publication survey - Publish the ACT Rules Format 1.0 second draft and three examples rules
22 August: Accessibility Guidelines Working Group Teleconference
- Printing – Issue 76 https://www.w3.org/2002/09/wbs/35422/extra_sc/results#xmatf1 - SC to be tided up and definition written and CFC to follow
- Animation – Issue 18 https://www.w3.org/2002/09/wbs/35422/extra_sc/results#xanim - Accepted to editors draft at AAA
- Device sensors - Issue 67 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC10 - Device sensors accepted to editors draft
- Undo - Issue 38 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC3 - Undo not accepted into editors draft.
- Issue 41 Plain Language - Undo not accept plain language into editors draft.
17 August: AG WG
- Pointer Gestures Issue 61 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC7 - accepted as amended
- Metadata - Issue 82 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc12 - Accepted as proposed.
- Pointer inputs with additional sensors - Issue 66 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC9 - Defer for later consideration in WCAG 2.2 or later
- Printing Issue 76 https://www.w3.org/2002/09/wbs/35422/extra_sc/results#xmatf1 - leave open for more discussion
15 August: AG WG
- Timeouts - Issue 14 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC1 - Accepted to editors draft with the addition of a note on user consent and editors note
- Personalization - Issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13 - Accepted as amended with MCs mc2 branch.
10 August: Accessibility Guidelines Working Group Teleconference
- Personalization - issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13 - Accepted as proposed for the AA Personalization item, with an objection from Alex.
- Personalization - issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13 - presonalization AAA accepted
- Personalization - issue 6 https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13 - Popup Visibility accepted for CFC
8 August: Accessibility Guidelines Working Group Teleconference
- meeting time (https://www.w3.org/2002/09/wbs/35422/mastiempo/results) - Extend the calls starting Thursday August 10. Split scribing for long call.
- Concurrent Input Mechanisms (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC8) - Accept as amended.
3 August: Accessibility Guidelines Working Group Teleconference
- Plain Language: https://www.w3.org/2002/09/wbs/35422/sc_august2017 (only item 2) - No consensus yet.
1 August: Accessibility Guidelines Working Group Teleconference
- Popup - Leave open. Alex to work with Steve on new wording.
- pointer gestures - leave open resurvey
25 July: Accessibility Guidelines Working Group Teleconference
- Personalization https://www.w3.org/2002/09/wbs/35422/LatestPersonalization/results - Partially clean up definitions and bring back next week.
- Target size https://www.w3.org/2002/09/wbs/35422/target_size/results - Keep the AAA version of target size
- Target size https://www.w3.org/2002/09/wbs/35422/target_size/results - Accept AA version with editors note about exception for groups of links
- Confirm Important Information https://www.w3.org/2002/09/wbs/35422/confirm-impt-info/results - Continue work on transaction definition and scope
18 July: Accessibility Guidelines Working Group Teleconference
- Adapting Text: https://www.w3.org/2002/09/wbs/35422/AdaptingTextJuly6/results - Accept to editor's draft. CFC to follow
- Conformance changes: https://www.w3.org/2002/09/wbs/35422/62-63-71-conformance/results - Accept version posted by AWK at 12:02. Also create an issue for clarifications to be made in understanding document.
13 July: Accessibility Guidelines Working Group Teleconference
- Undo : https://www.w3.org/2002/09/wbs/35422/COGA_undo/results - Leave open for further edits from Lisa, Mike and Alastair
11 July: Accessibility Guidelines Working Group Teleconference
- Resolving Issues 62/63/71: https://www.w3.org/2002/09/wbs/35422/Issues64-67-68/results - pursue approach on modification to conformace section
- Adapting Text (continued): https://www.w3.org/2002/09/wbs/35422/AdaptingTextJuly6/results - leave open
- Personalization - leave open
6 July: Accessibility Guidelines Working Group Teleconference
- Adapting Text: https://www.w3.org/2002/09/wbs/35422/AdaptingTextJuly6/ - leave open UNDO
- Adapting Text: https://www.w3.org/2002/09/wbs/35422/AdaptingTextJuly6/ - Adapting Text accepted into editors draft
29 June: Accessibility Guidelines Working Group Teleconference
- Concurrent Input Mechanisms (cont) https://www.w3.org/2002/09/wbs/35422/MATFSC_june/results#xnew1 - send back to Mobile task force for better examples
- Support personalisation (minimum) https://www.w3.org/2002/09/wbs/35422/COGA_new/results - leave this one open
27 June: Accessibility Guidelines Working Group Teleconference
- Concurrent Input Mechanisms https://www.w3.org/2002/09/wbs/35422/MATFSC_june/results#xnew1 - Leave Open
- Support personalization (minimum) https://www.w3.org/2002/09/wbs/35422/COGA_new/results#xq4 - Leave open
22 June: Accessibility Guidelines Working Group Teleconference
- 1. Speech Input / Accessibility Name #68 - success criteria Accessible Name accepted for editors draft with minor editorial changes (i.e., removing the note)
20 June: Accessibility Guidelines Working Group Teleconference
- Device Sensors/User Interface Component Contrast (Minimum): https://www.w3.org/2002/09/wbs/35422/Top3_18Apr2017/results - Device Sensors - Accept this SC into editors draft and include an Editor note to say that the preference of the group is to alter an existing SC rather than add a new one.
- User Interface Component Contrast - Accepted User Interface Component Contrast (Minimum) #10 into editors draft.
- Accessible Authentication: https://www.w3.org/2002/09/wbs/35422/COGA_Auth/results - Accepted into Working draft accessible authentication #23
15 June: Accessibility Guidelines Working Group Teleconference
- Accessible Authentication: https://www.w3.org/2002/09/wbs/35422/COGA_Auth/results - Leave open
8 June: Accessibility Guidelines Working Group Teleconference
- Orientation: https://www.w3.org/2002/09/wbs/35422/MATF_orientation/ - Put Orientation SC into the next editor's draft
6 June: Accessibility Guidelines Working Group Teleconference
- AGWG summer schedule https://www.w3.org/2002/09/wbs/35422/AWAG_summer_2017/results - We do not have consensus to publish new WCAG 2.0 edited recommendation
- AGWG summer schedule https://www.w3.org/2002/09/wbs/35422/AWAG_summer_2017/results - Accepted as proposed “Approval process for Understanding documents”
- AGWG summer schedule https://www.w3.org/2002/09/wbs/35422/AWAG_summer_2017/results - Accepted as proposed, with need for futher clarifications in understanding doc
- AGWG summer schedule https://www.w3.org/2002/09/wbs/35422/AWAG_summer_2017/results - leave this open
30 May: Accessibility Guidelines Working Group Teleconference
- change of content: https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/results#xq10 - The working group has accepted this SC for inclusion in the Editor's draft
25 May: Accessibility Guidelines Working Group Teleconference
- Resize Content: https://www.w3.org/2002/09/wbs/35422/ResizeContent-issue77/ - Leave open, alastair to work on edits
- Resize Content: https://www.w3.org/2002/09/wbs/35422/ResizeContent-issue77/ - Leave open.
23 May: Accessibility Guidelines Working Group Teleconference
- Supplementary document(s) survey: https://www.w3.org/2002/09/wbs/35422/WCAG21_supp/ - the working group has agreed to publishing supplemental guidance in 1 document that is non-normative
- Target Size: https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/#wbsq4 - Target Size proposal accepted
18 May: Accessibility Guidelines Working Group Teleconference
- 1.3.3/1.4.1 - go for CFC
- Resize Content: https://www.w3.org/2002/09/wbs/35422/ResizeContent-issue77/results - Leave open
- Target Size: https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/#wbsq4 - Leave open
16 May: Accessibility Guidelines Working Group Teleconference
- Resize Content: https://www.w3.org/2002/09/wbs/35422/ResizeContent-issue77/results - Leave open
- Plain Language: https://www.w3.org/2002/09/wbs/35422/plainLanguage-min-Issue30/ - leave open
- Target Size: https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/#wbsq4 - Leave open
9 May: Accessibility Guidelines Working Group Teleconference
- Resize content #77 CFC - Removing Resize Content #77
4 May: Accessibility Guidelines Working Group Teleconference
- Timeouts: https://www.w3.org/2002/09/wbs/35422/Timeouts_Issue14/results - Leave open while final adjustments are made. See issues.
- Minimize user errors: https://www.w3.org/2002/09/wbs/35422/minimize-user-errors-13/results - Leave open
- Single Key Shortcut Alternative: https://www.w3.org/2002/09/wbs/35422/Top3_18Apr2017/#wbssc - Leave Open
2 May: Accessibility Guidelines Working Group Teleconference
- Single Key Shortcut Alternative: https://www.w3.org/2002/09/wbs/35422/Top3_18Apr2017/results#xsc - Leave Open
- Timeouts: https://www.w3.org/2002/09/wbs/35422/minimize-user-errors-13/results - Leave Open
25 April: Accessibility Guidelines Working Group Teleconference
- Suggestion to change SC review schedule to make it easier. - Success criteria will be released every two weeks
- SC managers and comments - overview of process. - Success criteria will be released every two weeks
18 April: Accessibility Guidelines Working Group Teleconference
- Accessible Authentication: https://www.w3.org/2002/09/wbs/35422/SCs_April_11/#wbsq10 - leave open
13 April: Accessibility Guidelines Working Group Teleconference
- Adapting Text options discussion - Group to review options for split SC on the list
11 April: Accessibility Guidelines Working Group Teleconference
- TPAC F2F - AG meeting will be happening at TPAC
- SC Review - accept Accidental Activation
- Support Personalization - go back to COGA for reviewing comments and further work
- Adapting text options - Needs more discussion.
6 April: Accessibility Guidelines Working Group Teleconference
- Target size - Working group will resurvey this item language proposal
- Adapting Text - Options for Adapting Text to be surveyed
4 April: Accessibility Guidelines Working Group Teleconference
- Adapting Text - Needs more work.
28 March: Accessibility Guidelines Working Group Teleconference
- User Interface Component Contrast (Minimum) - Leave open, with final contrast ratio to be determined next week.
21 March: Accessibility Guidelines Working Group Teleconference
- adapting text - No consensus yet
21 February: Accessibility Guidelines Working Group Teleconference
- FPWD Survey: https://www.w3.org/2002/09/wbs/35422/WCAG21FWPD/ - Publish as FPWD
14 February: Accessibility Guidelines Working Group Teleconference
- SC Proposal: Graphics Contrast (Issue 9) - Accept pull request into editor's draft
- SC Proposal: Interruptions (minimum) (Issue 47) - Accept pull request into editor's draft
7 February: Accessibility Guidelines Working Group Teleconference
- Testing Survey: https://www.w3.org/2002/09/wbs/35422/testing20170207/results - User testing is not a required part of a manual testing process for WCAG test criteria.
- Testing Survey: https://www.w3.org/2002/09/wbs/35422/testing20170207/results - WG agrees that SC should have a high degree of confidence of inter-rater reliability, approximated by the expectation that 8 of 10 experts in a area would agree.
31 January: Web Content Accessibility Guidelines Working Group Teleconference
- SC Proposal: accessible authentication #23 - Issue 23 Accessible Authentication is not approved at this time and needs further work. The SC manager will reiterate
- SC Proposal: Manageable blocks #24 - Issue #24 Manageable Blocks was not accepted by the group and may have another iteration
- SC Proposal: Resize Content #77 - Issue 77 Resize Content is accepted with minor changes
- SC Proposal: Resize Content #77 - Issue #9 Informational Graphic content is accepted by working group
24 January: Web Content Accessibility Guidelines Working Group Teleconference
- 'Proposal for modifying existing SC' https://www.w3.org/2002/09/wbs/35422/ModifySCs/ - we will NOT consider modify existing SCs at this point (while draft 2.1 SCs are being worked on). We will set up a time for additional discussion for SC managers.

2016

29 November: Web Content Accessibility Guidelines Working Group Teleconference
- DPUB business - To route Issue-72 for approval
- DPUB business - Katie to work on text for proposed success criteria metadata with others.
- New SC proposal - Issue 10: Interactive Element Contrast (Minimum) - Glenda to work on an updated proposal on Disabled Item Success Criteria proposal
- New SC proposal - Issue 9: Informational Graphic Contrast (Minimum) - Laura and Alistair to work on an updated proposal on Informational Graphic Contrast (Minimum)
22 November: Web Content Accessibility Guidelines Working Group Teleconference
- [DPUB] Request to consider inclusion of accessibility metadata - Katie and Wilco to work on a proposal on "best practices" and DPUB to look at a specific success criteria proposal
- Survey: https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results - DPUB group to review "set of web pages" and "web page" definitions and suggest changes/additions to clarify
- Survey: https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results - DPUB will review definitions of web pages that are backward compatible
15 November: Web Content Accessibility Guidelines Working Group Teleconference
- Making G53 more generic to meet 2.4.4 #242 - Mike Gower to work on updates to Issue 246 in a new issue
- Making G53 more generic to meet 2.4.4 #242 - Not accept changes in Issue 242
- Working group review of ACT Framework Requirements + DPUB request https://www.w3.org/2002/09/wbs/35422/ACT_DPUB_Review_Nov_2016/ - to keep #240 open
8 November: Web Content Accessibility Guidelines Working Group Teleconference
- Charter edit re: DPUB - Add to Charter: "Digital Publishing Interest Group: Coordinate on accessibility guidelines that impact digital publishing."
- Consider language changes in Sufficient Techniques section of 1.3.2 SC for item 1 #243 - Leave open.
- Moving ARIA2 technique from 3.3.3 and putting in 3.3.2; adding ARIA21 to 3.3.3 - Leave open. Take up next time.
1 November: Web Content Accessibility Guidelines Working Group Teleconference
- Issue 245 - Approve 245
- Issue 244 - Accept 244 as advisory technique
- https://www.w3.org/2002/09/wbs/35422/SilverTFWorkStatement/ - Accept Silver Work Statement
25 October: Web Content Accessibility Guidelines Working Group Teleconference
- Issue 199 - Accepted as proposed.
- Issue 200 - Accepted as amended.
- Issue 232 - Accept proposal to decline adding the link.
- 11:35-12:00 - Silver Plan Survey: https://www.w3.org/2002/09/wbs/35422/SilverProcess/ - Accepted process document with revisions.
19 September: Web Content Accessibility Guidelines Working Group Teleconference
- Issue 6 Support Personalization - Needs to be considered at the same time as MATF and LVTF personalization items, possibly a new GL group.
30 August: Web Content Accessibility Guidelines Working Group Teleconference
- Publication of Techniques and Understanding Documents (https://www.w3.org/2002/09/wbs/35422/fall2016pubs/) - WG agrees to publish updated Techniques and Understanding documents.
23 August: Web Content Accessibility Guidelines Working Group Teleconference
- Updated charter discussion (https://www.w3.org/2002/09/wbs/35422/2point1Charterdraft/) - Inclue ATAG 2.0 and UAAG 2.0 maintenace into charter scope as allowed but not required.
- Updated charter discussion (https://www.w3.org/2002/09/wbs/35422/2point1Charterdraft/) - Working group approval to submit Charter for preliminary review.
- Updated charter discussion (https://www.w3.org/2002/09/wbs/35422/2point1Charterdraft/) - New versions of UAAG and ATAG are out of Charter scope.
- Survey on github issues and pull requests (https://www.w3.org/2002/09/wbs/35422/August23Misc/) - Items 1 and 5 accepted.
- Survey on github issues and pull requests (https://www.w3.org/2002/09/wbs/35422/August23Misc/) - Accept item #2.
- Survey on github issues and pull requests (https://www.w3.org/2002/09/wbs/35422/August23Misc/) - Accept Item 3
- Survey on github issues and pull requests (https://www.w3.org/2002/09/wbs/35422/August23Misc/) - Accept item 4
- Survey on github issues and pull requests (https://www.w3.org/2002/09/wbs/35422/August23Misc/) - Accept item 6 as changed.
16 August: Web Content Accessibility Guidelines Working Group Teleconference
- Update to H86 - The phrase standard characters will be used instead
- Update to H83 - Accepted update to H86 as proposed
- Changes to PDF Technology Notes - Agreed to the response, and notes can be updated easily.
- Remove H46 - H46 - response accepted as proposed
9 August: Web Content Accessibility Guidelines Working Group Teleconference
- ACT TF Proposal https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement - Working group approves work statement and TF Proposal for the ACT task force
- ACT TF Proposal https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement - Checklist for proposals for new SC approved
- Success Criteria Requirements - Acepted SC requirements
12 July: Web Content Accessibility Guidelines Working Group Teleconference
- Silver sub group - silver sub group is initiated
14 June: Web Content Accessibility Guidelines Working Group Teleconference
- FPWD of COGA Gap Analysis, Road Map and Issue Papers https://www.w3.org/2002/09/wbs/35422/COGA_FPWD_2016/ - Publish COGA for FPWD is accepted.
7 June: Web Content Accessibility Guidelines Working Group Teleconference
- PDF Proposaal - Accept as proposed
- Adding PX comment to G18 and G145 - Accept this change as amended.
- Remove references of 3.2.1 from f52 - No concensus
- Focus order with TabIndex - is it allowed? #182 - Accept as proposed.
24 May: Web Content Accessibility Guidelines Working Group Teleconference
- Issue 188 (https://github.com/w3c/wcag/pull/188/files?diff=split) - Accept pullrequest
17 May: Web Content Accessibility Guidelines Working Group Teleconference
- TPAC Registration https://www.w3.org/2016/09/TPAC/ - Josh to ping the list to ask the group if it likes the idea of using Date reviewed.
- Proposal Should G83: "Providing text descriptions to identify required fields that were not completed" reference 3.3.2 - Do not accept for being unclear.
- <Joshue108> TOPIC: F38 and 4.1.1 conflict ? #186 - Proposed response is accepted.
- "Large text" - using px rather than pt as unit #181 - Work on this will continue in the understanding document and be flagged for 2.1.
- Does WCAG 2.0 SC 1.3.1 mean that headings areas, footer areas are required to be identified programatically or in text - Will be addressed next week.
3 May: Web Content Accessibility Guidelines Working Group Teleconference
- Publishing new WCAG edited recommendation, with Makotos edit to 1.4.6 - no objection to publishing new WCAG edited recommendation with Makotos edit
- 173 - Leave open
26 April: Web Content Accessibility Guidelines Working Group Teleconference
- Issue 167 - accepted pull request 179 as proposed
- Issue 165 - Accept proposed response
- Issue 158 - Accept pull request 174
19 April: Web Content Accessibility Guidelines Working Group Teleconference
- Publishing new WCAG edited recommendation - CFC to go to working group list regarding Mikota’s edit and working group approval
- Some questions left from previous meeting - Laura to rework techniques based on working group review
- Some questions left from previous meeting - accepted editorial changes
- Some questions left from previous meeting - leave open need more info
- Remaining survey items from last week - defer response
- Remaining survey items from last week - link page 91 ith related aria techniques
12 April: Web Content Accessibility Guidelines Working Group Teleconference
- Issue 168 - The Working Group has concluded that WCAG 2.4.4 (Issue 168) that <buttons> are out of scope per a strict read of WCAG 2.0. The Working Group recognizes this gap, and resolves to address that gap.
- Issue 168 - The Working Group has concluded that WCAG 2.0 SC 2.4.4 does not cover button elements per a strict read of WCAG 2.0. The Working Group resolves to add this as an issue for consideration in a post-WCAG 2.0 version
- Issue 157 - accept response as amended.
5 April: Web Content Accessibility Guidelines Working Group Teleconference
- Issues 171 - WG agrees that Landmarks are not required to meet SC 1.3.1 for any page with head/foot/navigation areas as there are other ways to indicate a page's structure.
- Issue 170 - The WG generally agrees that F52 doesn't apply to 3.2.1 and needs someone to write up the official proposal of changes in GitHub
15 March: Web Content Accessibility Guidelines Working Group Teleconference
- QuickRef Survey (https://www.w3.org/2002/09/wbs/1/2016quickrefapproval/results) - Approve publication of WCAG quickref
1 March: Web Content Accessibility Guidelines Working Group Teleconference
- Clarification over link/button states - James N and Alistair to work on description of transcient meta states
23 February: Web Content Accessibility Guidelines Working Group Teleconference
- Techniques and Understanding Review: https://www.w3.org/2002/09/wbs/35422/Feb2016TandU/results, closed - Working group approves Techniques and Understanding document.
- Extension document issues (https://www.w3.org/2002/09/wbs/35422/Misc20160223/results, list discussion on 2.2) - Accepted as proposed.
16 February: Web Content Accessibility Guidelines Working Group Teleconference
- LVTF Accessibility Requirements for people with Low Vision doc - ready for FPWD approval. - LVTF approved for FPWD
- COGA Task Force draft of Roadmap and Gap Analysis doc - ready for FPWD approval. - COGA will be left open for editorial updates
- Extension framework requirements - discussion/changes to paragraph 2.2. - Leave Extensions framework document open for discussion by editors to discuss going out for public review
9 February: Web Content Accessibility Guidelines Working Group Teleconference
- item 156 - leave open
- Proposed change to 2.2 in Extension Requirements - leave open - take it up on list
26 January: Web Content Accessibility Guidelines Working Group Teleconference
- • Extension document comment survey [continued / to be short!] (https://www.w3.org/2002/09/wbs/35422/Ext_req_comments/ - We sent this wording to the list.
- [Github ISSUE: #151] ARIA5: About jQuery code - We send the wording above to the list for consensus.
- Github ISSUE: #150] ARIA4/5: Clarification of a user interface component - Pass the wording of the response to the list for consensus.
- [Github ISSUE: #148] WAI-ARIA Technology Notes: Old UA descriptions - Leave this one open.
19 January: Web Content Accessibility Guidelines Working Group Teleconference
- Extension document comment survey (https://www.w3.org/2002/09/wbs/35422/Ext_req_comments/) - Leave open.
- Issue 108 - Leave open.
12 January: Web Content Accessibility Guidelines Working Group Teleconference
- Issue 80 - leave Issue 80 open
- Issue 133 - accepted as recommended
- Issue 96 - Leave open

2015

24 November: Web Content Accessibility Guidelines Working Group Teleconference
- Public review of 'Requirements for WCAG 2.0 Extensions' (FPWD) https://www.w3.org/2002/09/wbs/35422/ExtensionsFPWD/ - Accepted for public review WCAG 2 Extensions.

Back to Top

This is an unpublished draft preview that might include content that is not yet approved. The published website is at w3.org/WAI/.