-
Notifications
You must be signed in to change notification settings - Fork 4
Agendas
These are the agendas for the WCAG2ICT weekly meeting. For links to surveys and other materials we'll be reviewing or discussing, go to the Work for the week page of this Wiki.
- Announcements
- Phase 2 of WCAG2ICT update
- Work statement
- Explainer outline
- Announcements
- Retrospective
- Phase 2 of WCAG2ICT update
- Updating the WCAG2ICT work statement - PR 942
- Explainer for WCAG2ICT - Google doc
- Level AAA Success Criteria
- Project plan
Per W3C WCAG2ICT Group Note Published email to listserv, the Task Force is taking a little hiatus and will not meeting again until 7 November. The next tasks are:
- Create a brief explainer emphasizing the purpose and proper use of WCAG2ICT
- Add WCAG Level AAA SC guidance to the document
- Announcements
- Next steps/work for the WCAG2ICT TF
No meeting
Please plan for an extra-long meeting (one hour longer)
- Announcements
- Survey results (Group 3) Review changes due to comments on second public draft
- Remaining issue answers (464 and 466)
- Slight change to definition of 'large scale'
- 4.1.1 Parsing - inclusion of WCAG 2.1 and 2.2 versions of the text
- TF Resolution: Send editor's draft to AG WG for review and approval for publication as a final Group Note
- Announcements
- Survey results (Group 3) Review changes due to comments on second public draft
Working session to address open issues. We'll be developing proposals for changes to the WCAG2ICT draft (if needed) and issue answers to go into the issue comments. Once this sub-group is happy with proposals, they will go to the full TF in a survey.
- Open issues
- Open pull requests - specifically to provide Daniel with feedback on his proposed changes
- Announcements
- Survey results: (Group 2) Review changes due to comments on second public draft
Working session to address open issues. We'll be developing proposals for changes to the WCAG2ICT draft (if needed) and issue answers to go into the issue comments. Once this sub-group is happy with proposals, they will go to the full TF in a survey.
- Announcements
- Survey results: (Group 1) Review changes due to comments on second public draft
- Announcements
- Mobile TF discussion on interpretation of success criteria applicable to "sets of software"
- Survey results: (Group 1) Review changes due to comments on second public draft
- Announcements
- Work on open issues
- Announcements
- Issues Mitch opened (Issue 424, Issue 427, Issue 432, Issue 436, Issue 437)
- Issues AG WG Opened (Issue 383, Issue 394)
- Public comments (Issue 437)
- Announcements
- Public comments
- Other open issues
- Announcements
- Reminder of process for public comments
- Public comments
- Other open issues
- Announcements
- Publication timeline
- Wide review communication
NOTE: If we have a quorum, we will be making TF decisions during this meeting
- Issue 77: including WCAG supplements and Making Content Usable for People with Cognitive and Learning Disabilities
- Issue 374: Focus Not Obscured needs a note for non-web software
- Announcements
- Survey results 3rd round of reviewing proposed updates
- No extra Friday meeting
- Announcements
- Survey results Review updated proposals developed on 30-31 May
- Announcements
- Survey results: Review of Updated Proposed Changes since 16 May
- Issue 377: Feedback from Microsoft on WCAG2ICT Reflow notes 5 and 7
- Survey results for proposed WCAG2ICT changes and clarifications
- Proposed verbiage changes regarding 3.3.8 Accessible Authentication in the Google doc
- Announcements
- Revisit discussion on 3.3.8 Accessible Authentication
- AG WG comments received thus far in the review issues
- Survey Results: Additional proposals for changes
- Announcements
- Work left before publication
- Survey results: Remaining answers to open issues
- Survey results: Remaining proposals for changes to the editor's draft
- Survey results: Proposed editor's notes
- Survey results for (Part 3 of 4 for Issue 4): Are built-in platform accessibility features considered AT?
- Survey results for (Part 4 of 4 for Issue 4): Does 1.4.4 Resize Text guidance in WCAG2ICT need changes?
- Questions we didn't get to in the 9 May meeting: follow-up survey (starting at question 2) through question 4.
- Announcements
- Survey results: Follow-up survey addressing public comments, SOTD
- Survey results: Issue 4
- Develop any alternate proposals based on the Survey results: Issue 145, answers to public comments, and SOTD starting at question 4.
- Lood at the survey results: Issue 4 and work on alternate proposals, if needed.
- Announcements
- Work left before publication
- Survey results: Issue 145, answers to public comments, and SOTD
- Survey results: Issue 4
- Issue 4 - finish work on this last issue, proposing answer and IF new draft content is needed draft it!
- New/modified drafted content due to survey feedback for 25 April, if needed
- Discussion and work on editors' notes drafts
- Announcements
- Work left before publication
- Survey results: Issue 145, answers to public comments, and SOTD
Call cancelled due to lack of participants.
- Draft answers in the google doc for Issues 221, 226, and 257 which are all related to 1.4.10 Reflow.
- Issue 4 – Looking for guidance regarding SC 1.4.4, Resize Text, on mobile native apps
- Announcements
- Status of remaining work before next publication
- Glossary term "conforming alternate version"
- Results of survey on proposed changes to address Issue 196
- (if time allows) Discussion on editor's notes needed in draft for the public review.
- Taking a break, no meeting.
- Announcements
- Status of remaining work before next publication
- Survey results: Proposals for remaining work
- Cancelled due to lack of participants
- Announcements
- Status of remaining work before next publication
- Survey results: Proposals for remaining work
- Issue 145 - Add info/content on the WCAG exemptions in regulatory work
- Issue 4 – Looking for guidance regarding SC 1.4.4, Resize Text, on mobile native apps
- Issues 221, 226, and 257 which are all related to 1.4.10 Reflow. We'll initially draft answers in the google doc.
- Announcements
- Status of remaining work before next publication
- Survey results: Proposals for remaining work
- Open issue discussions
- Develop any remaining public comment responses and/or proposed document changes.
- Talk about and develop the editors' notes needed for the next public release of the draft.
Our regular Task Force meeting will be a working session due to CSUN, as several participants will be at that conference.
- Work on proposed changes for 1.4.10 Reflow
- Develop proposed content changes for Issue 196
- Work on answers and potential changes for Issues 4, 200, and 266
- Work on remaining Survey results from 14 March proposing changes
- Announcements
- Approve public comment responses - Issue 216
- Survey results for remaining SC problematic for Closed Functionality content
- 2.1.1 Keyboard - Work on changes due to survey results
- 1.4.10 Reflow - Work on changes due to survey results
- SC Problematic for Closed Functionality - SCs that require programmatic information (4.1.2, 1.3.1, 1.1.1, 1.3.2, 3.1.1, 3.1.2, others?)
- Announcements
- Survey results: SC Problematic for Closed Functionality - 1.4.5 Images of Text
- Survey results: SC Problematic for Closed Functionality - Keyboard SCs
- Survey results: Review answers to public comments - Group 3
- 1.4.10 Reflow
- Keyboard SCs: 2.1.4 Character Key Shortcuts, 2.4.7 Focus Visible, 2.1.2 No Keyboard Trap
- Announcements
- Survey results - Review of proposed responses to public comments - Group 2, starting with question 2
- Survey results - Review of 1.4.12 Text Spacing and Images of Text proposals
- Discussion on Issue 196 - Can a non-web software act as, or have, a conforming alternate version?
- Status messages - new note?
- Adjustments to 1.4.12 Text Spacing guidance
- 1.4.5 Images of Text
- 1.4.10 Reflow (if there's time)
- Announcements
- Survey results - Review of 4.1.3 Status Messages proposal
- Survey results - Question 5 of the Review of proposed responses to public comments - group 1
- Survey results - Review of proposed responses to public comments survey results
- Handling of SC 4.1.3 Status Messages and 1.4.12 Text Spacing (Differing guidance, expansion of scope, etc.)
- Announcements
- Survey results regarding responses to public comments - Group 1, starting at question 4 - Issue 216
- Survey results for public and TF comments
- Survey results for the Review of 3.3.8 Accessible Authentication notes and SC problematic for closed guidance
- 3.3.8 Accessible Authentication Notes 3 & 4
- 3.3.8 Accessible Authentication content in SC Problematic for Closed Functionality
- Announcements
- Comments on Closed Functionality - CfC on which option to incorporate (results of 1 Feb. email poll)
- Survey results for 3.3.8 Accessible Authentication - Starting with Question 4
- Survey results for public comment responses - group 1
- Work on 1.4.10 Reflow notes due to Issue 226
- Work on 3.3.8 Accessible Authentication notes (incorporating survey results)
- Announcements
- Comments on Closed Functionality and definition of "closed functionality" per the survey results.
- Discussion on 4.1.3 Status messages in the Google doc.
- Due 31 Jan.: Survey results for 2.4.8 Target Size (Minimum) and new draft for 3.3.8 Accessible Authentication
- Due 31 Jan.: Survey results for public comment responses - group 1
- Announcements
- Discussion on 4.1.2 Name, Role, Value bullet for SC problematic for closed functionality section.
- Latest proposal for Comments on Closed Functionality section based on survey results on Closed intro
- Latest proposal for key term "closed functionality" based on survey results - review of "closed functionality"
- Announcements
- Closed functionality bullets and introductory section (See survey results - Closed Functionality: Intro and bullets for 1.4.5, 2.4.3, and 4.1.3.)
- Work on unassigned list of public comment issues.
- Announcements
- Survey results: Review of updated draft for 3.2.6 Consistent Help
- Survey results: Review of Closed functionality bullets for SCS 3.2.3 & 3.2.4, 4.1.2, 2.1.2, 2.1.4, and 2.4.7
- Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 3.2.3 and 4.1.2
- Survey results: Review of TF responses to public comments
- Continue work on Closed functionality bullets starting where we left off on 4 Jan. Survey results: Closed functionality bullets starting at question 4 for 3.2.3 Consistent Navigation and 3.2.4 Consistent Identification
- Work on unassigned list of public comment issues.
- Announcements
- Project status and standup
- Status of AG WG comments on our content review
- Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2
- Work on unassigned list of public comment issues.
- Announcements
- AG WG comments on our content review
- Public comments (and upcoming survey to review proposed responses)
- Review of remaining new term definitions
- Reopened the Closed Functionality Bullets: SCS 2.5.2, 3.1.1, 3.1.2, 3.2.3, and 4.1.2.
- Announcements
- WCAG2ICT project status and standup
- Survey results - Closed Functionality Bullets: SCS 2.5.2, 3.1.1, 3.1.2, 3.2.3, and 4.1.2
- Survey results - Review of SC 2.5.8 Target Size (Minimum) proposed updates
- Survey results - Review SC 3.2.6 Consistent Help draft
- Announcements
- WCAG2ICT project status and standup
- Survey results - 3.3.8 Accessible Authentication (Minimum) (continue working on last 2 questions)
- Public comments (continue from last week, starting with question 2)
- TOPIC: Issue 217 Survey results - updated proposal for Closed functionality section
- Announcements
- WCAG2ICT project status and standup
- Public comments (continue from last week, starting with question 2)
- TOPIC: Issue 217 Survey results - updated proposal for Closed functionality section
- Survey results - 4.1.1 Parsing interpretation for WCAG 2.0 and 2.1
- Survey results - 3.3.8 Accessible Authentication (Minimum)
- Announcements
- WCAG2ICT project status and standup
- Public comments
- TOPIC: Issue 217 Survey results - updated proposal for Closed functionality section
- Survey results - 2.4.11 Focus Not Obscured (Minimum)
- Survey results - updated proposal for 2.5.7 Dragging Movements
- Announcements
- WCAG2ICT Project status and standup
- Public comments
- Survey results: Proposal for 2.5.7 Dragging Movements
- Survey results: Updated proposal for 4.1.1 Parsing
- Announcements
- Public comments
- Survey results: Review of Proposed Changes to Definitions
- Survey results: Review proposed changes for 4.1.1 Parsing
- Announcements
- Public comments
- Discussion on 1.4.4 Resize Text
- Survey results for Review of Proposed Changes to Definitions
- Survey results for Review proposed changes for 4.1.1 Parsing
- Announcements
- Public comments on the FPWD
- Proposed response to Issue 228 on 2.1 Accessibility Services of Platform Software
- Triage unassigned issues
- Proposed change to Guidance heading text in Issue 238
- Survey results on Closed functionality: SCs 2.1.1, 2.4.2, and 2.4.5
- Announcements
- Public comments on the FPWD
- Topic: New issues opened last week
- Topic: Issue #232 2.2.2 Pause, Stop Hide
- Topic: Issue #231 1.4.12 Text Spacing
- Results for Survey on 3.3.7 Redundant Entry
- Announcements
- Public comments on the FPWD
- Survey results, Review draft updates to SC Problematic for Closed Functionality - starting with SC 2.4.2 Page Titled
- Announcements
- Public comments on the FPWD
- Survey results, Review draft updates to SC Problematic for Closed Functionality - starting at SC 2.4.1 Bypass Blocks
- Announcements
- Public comments on the FPWD, including resolution to send updated response to Craig Keefner
- Survey results: Review draft updates to SC Problematic for Closed Functionality - starting at SC 1.4.13 Content on Hover or Focus
- Announcements
- Public comments on the FPWD
- Survey results: Review updated proposals for SC Problematic for Closed Functionality (For 1.3.2 Meaningful Sequence and 1.4.12 Text Spacing)
- Survey results: Review draft updates to SC Problematic for Closed Functionality - starting at SC 1.4.12 Text Spacing
- Announcements
- Public comments on the FPWD
- Survey results: Review draft updates to SC Problematic for Closed Functionality - starting at SC 1.4.12 Text Spacing
- Announcements
- Survey results: Review draft updates to SC Problematic for Closed Functionality - starting at SC 1.4.10 Reflow
- Announcements
- Survey results: Review draft updates to SC Problematic for Closed Functionality - starting at SC 1.3.5 Identify Input Purpose
- Announcements
- Survey results: Review proposed key term 'closed functionality'
- Survey results: Review draft updates to SC Problematic for Closed Functionality
- Announcements
- CfC supporting publication of WCAG2ICT FPWD
- Survey results: Review draft updates to SC Problematic for Closed Functionality
- Announcements
- Survey results: Review draft updates to Text / Command line / Terminal Emulator sections
- Survey results: Review draft updates to SC Problematic for Closed Functionality
- Survey results for Notes 3 & 4: Review of Proposals for SC 1.4.10 Reflow
- Survey results: Review of "style property" definition
- Survey results: Review of "set of web pages" definition
- Get started on survey results: Review of proposed updates to SC Problematic for Closed Functionality
- Survey results: Review of Proposals for SC 1.4.10 Reflow
- Survey results: Review of "style property" definition
- Get started on survey results: Review of proposed updates to SC Problematic for Closed Functionality
- Announcements
- Project standup and planning
- Survey results: Continue CSS pixel definition draft review
- Survey results: Update to non-web document note on 2.5.8 Target Size (minimum)
- Survey results: Review of Proposals for SC 1.4.10 Reflow
- Announcements
- Project standup and planning
- Survey results: CSS pixel definition draft review
- Survey results: Update to non-web document note on 2.5.8 Target Size (Minimum)
- Survey results: Review of Proposals for SC 1.4.10 Reflow
- Announcements
- Project standup and planning
- Survey results: CSS pixel definition draft review
- Announcements
- Project standup and planning
- Survey results: 2.5.8 Target Size (Minimum)
- CSS pixel definition
- Announcements
- Project standup and planning
- Survey results: 2.5.8 Target Size (Minimum)
- Announcements
- Project standup and planning
- Discussion on definition of Device-independent pixels
- Announcements
- Project standup and planning
- Discussion on definition of Device-independent pixels
- Announcements
- Project standup and planning
- Discussion on definition of Device-independent pixels
- Continue the discussion on 1.4.10 Reflow
- Announcements
- Project standup and planning
- Continue the 20 April discussion on 1.4.10 Reflow
- Approve adjustments to 2.5.2 Pointer Cancellation language to be consistent with 2.5.1 Pointer Gestures
- Approve Pull request 152 to remove word substitution suggestions for the WCAG Intent sections
- Announcements
- Project standup and planning
- Survey results and discussion on SC 2.5.1 Pointer Gestures
- Do we need the Understanding Intent included in the document?
- Continue last week's discussion on 1.4.10 Reflow
- Announcements
- Project standup and planning
- Survey results and discussion on SC 1.4.10 Reflow
- Announcements
- WCAG 2.2 Status
- Project standup and planning for WCAG 2.2 SC
- Discussion on SC Problematic for Closed Functionality
- Announcements
- Project standup (status of your assigned issues)
- Survey - SC 1.4.11 Non-text Contrast - closed functionality software guidance
- Survey - SC 1.4.10 Reflow - readiness to incorporate into editor's draft
- Announcements
- Review of SC 1.4.12 Text Spacing
- Review of SC 4.1.3 Status Messages readiness to incorporate into editor's draft
- Review of 2.5.2 Pointer Cancellation readiness to incorporate into editor's draft
- Options for closed functionality bullets for SC 1.4.11 Non-text Contrast
- Announcements
- Project standup (status of your assigned issues)
- SC 1.4.11 Non-text Contrast readiness to incorporate into editors draft
- SC 1.4.12 Text Spacing readiness to incorporate into editors draft
- SC 4.1.3 Status Messages readiness to incorporate into editors draft
Guidance development working session today on the following:
- 4.1.3 Status Messages - discuss and develop guidance
- 2.5.2 Pointer Cancellation - discuss and develop guidance
- Announcements
- Project standup (status of your assigned issues)
- SC 1.4.12 Text Spacing readiness to incorporate into editors draft
- SC 1.4.11 Non-text Contrast readiness to incorporate into editors draft
- Announcements
- Project standup (status of your assigned issues)
- Review Survey results for SC 1.4.13 readiness to incorporate into editors draft
- Review Survey results for Key Terms and Glossary Items Used Only in AAA Success Criteria sections
- Continue previous discussion on applying 1.4.10 Reflow to non-web documents and software
- Announcements
- Project standup (status of your assigned issues)
- Survey: Review of SC 2.5.3 Label in Name readiness to incorporate into editor's draft
- Discussion thread on applying 1.4.10 Reflow to non-web documents and software
- Announcements
- Project standup (status of your assigned issues)
- Survey: Review of SC 1.4.11 readiness to incorporate into editor’s draft
- Survey WCAG2ICT-Abstract and Comparison sections readiness to incorporate into editor's draft
- Survey WCAG2ICT-Introductory sections' readiness to incorporate into editor's draft
- Announcements
- Project standup (status of your assigned issues)
- Discussion: Loïc's proposal for 1.4.12 Text Spacing
- Survey: Review of SC 2.5.4 readiness to incorporate into editor’s draft
- Survey: Review of SC 1.4.11 readiness to incorporate into editor’s draft
- Announcements
- Project standup (status of your assigned issues)
- Discussion: Readiness of SC 2.1.4 proposal to incorporate into editor's draft (Continue from last week)
- Discussion: Loïc's proposal for 1.4.12 Text Spacing
- Announcements
- Project standup (status of your assigned issues)
- Survey: Readiness of SC 2.1.4 proposal to incorporate into editor's draft
- Survey: Readiness of Background section proposal to incorporate into editor's draft
- Announcements
- Project standup (status of your assigned issues)
- Survey: Readiness of SC 1.4.12 proposal to incorporate into editor's draft
- Survey: Readiness of SC 2.1.4 proposal to incorporate into editor's draft
- Announcements
- Project standup (status of your assigned issues)
- Survey: Readiness of SC 1.3.5 proposal to incorporate into editor's draft
- Survey: Readiness of SC 1.4.12 proposal to incorporate into editor's draft
- Survey: Initial look at draft for 1.3.5 Identify Input Purpose
- If you have assigned yourself an issue, be prepared to give a brief status during the meeting and when you expect to complete the work, if you’ve got any blockers, or need any help. This will help me plan for upcoming meetings where content might be ready to send to the task force for review.
- Announcements
- AG WG guidance to TF on scope of changes the TF can make
- Survey: Draft background section
- Survey: Review proposed changes to guidelines
- Survey: Initial look at draft for 1.3.5 Identify Input Purpose
- Announcements
- Status of Markdown version of document
- Survey: Draft of SC 1.4.12 Text Spacing
- Survey: Draft of SC 1.3.4 Orientation
- Survey: Draft Background section
- Announcements
- Success Criterion templates
- Markdown version of files (Michael)
- Final Poll results & discussion
- Project timeline and Issue sign-up
Note: Daylight savings has not ended for USA, but has in some countries. Check against 10 AM Eastern to your location.
- Announcements
- Success Criterion Templates
- Walkthrough using the template
- Announcements
- Questions about using GitHub to propose changes
- The WCAG2ICT project plan
- Announcements
- GitHub training
- Announcements
- Next steps for the WCAG2ICT Work Statement
- Begin learning GitHub
- Announcements
- Review survey results from the work statement review
- Review/approve Pull Request 2682
- Next steps for the WCAG2ICT Work Statement
- As time allows, begin learning GitHub
- Announcements & unfilled roles
- Continue discussion on survey results from the work statement review
- Tools for drafting content
- Wiki updates
- Questions regarding this meeting's preparation work
- Review survey results from the work statement review
- Ways we might work - making sure all have access, can work effectively
- Welcome
- Short-term meeting dates
- Introductions
- Identify unfilled roles and potential interest
- Getting started with W3C and the WCAG2ICT wiki
- Ways we might work - making sure all have access, can work effectively
- Initial priorities for the group
- Homework / Preparation for the second meeting
This Wiki page is edited by participants of the Accessibility Guidelines Working Group's WCAG2ICT Task Force. Content in the Wiki shows work in progress by the task force, and does not necessarily represent consensus.