Skip to content

Work for the week

Jump to bottom
Bruce Bailey edited this page Dec 12, 2024 · 406 revisions

This page lists work items for members of the WCAG2ICT TF to do in preparation for the weekly meeting.

12 December

Explainer

  • Review Explainer and the meeting discussion on 14 Nov. where we made a resolution on the explainer. Read some other examples of explainers that may cause adjustments to the outline and be ready to make suggestions:

Priority of Level AAA

  • Review the meeting discussion on 21 Nov. regarding Level AAA where we made a resolution to make Level AAA a lower priority.
    • Gregg previously did some an analysis of AAA criteria. Does this change your view on the previous decision to have Level AAA criteria at a lower priority?

WCAG2ICT Work Statement Update

  • Understand where we currently are with the WCAG2ICT work statement PR 942 (or to read the built version of the work statement or a more friendly diff version between the two work statements.)
    • The resolutions made in the 21 November meeting have been incorporated.
    • Consider what further changes might be needed by noting them as comments to the PR.

5 December

21 November

  • Be familiar with the proposed updates to the WCAG2ICT Work Statement and existing PR 942. We'll be discussing and adjusting the PR live in the meeting based on what was learned in the joint AG WG and WCAG2ICT leadership meeting.

14 November

  • If you haven't already, review proposed updates to the WCAG2ICT Work Statement with the detailed changes in PR 942.
  • Review the Google doc outline for the Explainer for WCAG2ICT. Be ready to discuss whether this is sufficient, or needs additional information added.
  • Read Issue 578 and Issue 567. Feel free to add comments in the issues with your thoughts. Be ready to discuss and potentially make decisions on how Level AAA SC and definitions only used in Level AAA SC might be added and/or specially notated in the WCAG2ICT Note.

7 November

Month of October

Per W3C WCAG2ICT Group Note Published email to listserv, the Task Force is taking a little hiatus. 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

19 September

No prep work needed.

12 September

No meeting 12 September. However, please respond to the two CfCs noted in the 10 September email to the WCAG2ICT list:

As we charge toward getting WCAG2ICT published as a final note, there are two important things to do this week (even though we aren't meeting) -- by Friday, 13 September...

5 September meeting

NOTE: We reordered the questions to put the ones we reached resolution on in the 29 August meeting to the bottom of the survey.

29 August meeting

23 August (Extra Friday) meeting

  • We'll be working on proposals to resolve open issues from the public review.

22 August meeting

16 August (Extra Friday) meeting

  • We'll be working on proposals to resolve open issues from the public review. If you assigned yourself an issue to work on and want a group discussion, let me know and I can prioritize that in the discussion.

15 August meeting

8 August meeting

  • Due Tuesday 6 August: Complete the survey - (Group 1) Review changes due to comments on second public draft
  • Be familiar with the WCAG2ICT guidance for the five criteria regarding "sets of documents" and "sets of software" (2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, 3.2.4 Consistent Identification, and 3.2.6 Consistent Help). Jan Jap de Groot will be joining us for a discussion regarding mobile applications and these success criteria.

1 August meeting

25 July meeting

  • Review the list of issues and make sure you have an understanding of them so we can work developing possible content changes and/or responses.

18 July meeting

Task force participants are expected to take ownership of issues and usher them to resolution as follows:

  1. Look at the list of unassigned open issues and choose at least one issue to work on.
  2. Assign yourself to the issue by opening the issue and under "Assignees" choose the link to "Assign yourself". This will prevent multiple people from working on the same issue.
  3. Create proposals for changes to WCAG2ICT (if needed) either in the Issues Google doc or in a PR.
  4. Create a draft answer for the issue in the Issues Google doc.
  5. Add the label "Ready for TF Review" to the issue by opening the issue, clicking on "Labels" and then type "Ready" in the entry field until you see the appropriate tag and then select it. NOTE: Once you select the tag, click somewhere else in the issue first before going back to the issue list so the label is applied.

11 July meeting

Be prepared to self-assign issues and begin work to suggest edits or more substantive changes and to make PRs, as needed:

I've started a Google doc to develop issue answers. If you have anything else you want added to the agenda, send an email to the group or directly to Mary Jo.

NO MEETING: 4 July (U.S. holiday)

NO MEETING: 27 June meeting (draft in CfC for publication)

20 June meeting

  • Update the wide review communication wiki page with any persons or organizations you think it is important to contact so they are aware of the public comment period for this draft of WCAG2ICT.

14 June meeting

13 June meeting

6 June meeting

31 May (Extra Friday) meeting

30 May meeting

24 May (Extra Friday) meeting

23 May meeting

16 May meeting

10 May (Extra Friday) meeting

9 May meeting

3 May (Extra Friday) meeting

2 May meeting

26 April (Extra Friday) meeting

25 April meeting

19 April (Extra Friday) meeting

18 April meeting

No 12 April (Extra Friday) meeting

  • No prep, as there is no meeting on 12 April.

Preparation for the 11 April meeting

  • Be familiar with the survey results: Proposals for remaining work for questions 1 through 4. If you have content changes to propose or disagree with the majority of the responses, please add any comments or proposals for changes in the issues associated with the review.

Preparation for the 5 April (Extra Friday) meeting

Preparation for the 4 April meeting

Preparation for the 29 March (Extra Friday) meeting

  • Be ready to discuss what document content changes are needed to address Issue 145
  • Continue discussion on Issue 4
  • Assuming that 1.4.10 Reflow changes will be approved, work on drafting issue answers for Issues 221, 226, and 257. We'll initially draft in the google doc

Preparation for the 28 March meeting

Preparation for the 22 March (Extra Friday) meeting

  • Be familiar with the following issues: 196, 200, and 266. Think about whether the document needs changes to address the concerns in each issue and how we might answer them.

Preparation for the 21 March meeting (Working session due to CSUN)

  • Working session this week:
    • Be familiar with the current Proposals 3A and 3B in the Google doc for 1.4.10 Reflow
    • Be familiar with the following issues: 196, 4, 200, and 266. We'll work on any proposals for document changes needed as well as answers to these issues.

Preparation for the 15 March (Extra Friday meeting)

Preparation for the 14 March meeting

Preparation for the 8 March (extra Friday) meeting

  • Read 2.1.1 Keyboard survey results and think about what changes are needed.
  • Read 1.4.10 Reflow survey results and think about what changes are needed.
  • Prepare for conversation on SC Problematic for Closed Functionality regarding SCs that require programmatic information:
    • 4.1.2 Name, Role, Value - Google doc for 4.1.2. The Background section of the doc has links to previous surveys and discussions if you want to familiarize yourself with its evolution.
    • 1.3.1 Info and Relationships (nothing drafted yet), but is in Issue 275
    • Read through the SC Problematic for Closed Functionality for the other "programmatic info" SCs to ensure these are consistently worded (1.1.1 Non-text Content, 1.3.2 Meaningful Sequence, 3.1.1 Language of page, 3.1.2 Language of parts).

Preparation for the 7 March meeting

Preparation for the 1 March (extra Friday) meeting

Preparation for the 29 Feb. meeting

Preparation for the 24 Feb. (extra Friday) meeting

Preparation for the 23 Feb. meeting

Preparation for the 16 Feb. (extra Friday) meeting

Be familiar with the survey and discussions on 1.4.12 Text Spacing and 4.1.3 Status Messages:

Preparation for the 15 Feb. meeting

Preparation for the 9 Feb. (extra Friday) meeting

Weigh in on the various proposals for the notes for SC 3.3.8 in the Google document for 3.3.8 Accessible Authentication. Indicate in a comment which option is your preference and why (or draft your own proposal with a new option number). I also created heading sections for each proposed note to quickly link there.

Preparation for the 8 Feb. meeting

  • Respond to email regarding Comments on Closed Functionality section (sent on 1 Feb.)
  • Due 7 Feb.: Complete the Survey on public comment responses - group 1. Even if you previously completed the survey, take a look at others' survey answers as well as re-examine question 2 (for Issue 227) and question 5 (for Issue 302) which were changed per Mitch's and Sam's comments.
  • Due 7 Feb.: Weigh in on the various proposals for the notes for SC 3.3.8 in the Google document for 3.3.8 Accessible Authentication. Indicate in a comment which option is your preference and why (or draft your own proposal with a new option number). I also created heading sections for each proposed note to quickly link there.

Preparation for the 2 February (extra Friday) meeting

Preparation for the 1 February meeting

Preparation for the 26 January (extra Friday) meeting

  • Look at the various open public comment issues starting with the newest and be prepared to provide the pertinent points for the response. If you have the time and inclination assign yourself one and develop a response we can discuss in the meeting.

**NOTE: Even the two issues with the label "TF answer completed" have some ongoing discussion that may require further changes to the document.

Preparation for the 25 January meeting

Preparation for the 19 January (extra Friday) meeting

  • We'll be going through the list of public comments that have no response yet to discuss and develop what the response should include.

Preparation for the 18 January meeting

  • Develop your preferred language for the bullet for the SC Problematic for Closed Functionality for SC 4.1.2 Name, Role Value. You can look to various proposals from last week's meeting minutes (3 options were discussed).

Preparation for the 12 January (extra Friday) meeting

Preparation for the 11 January meeting

Preparation for the 5 January (extra Friday) meeting

Preparation for the 4 January meeting

  • Be prepared to provide status of any open issues assigned to you.
  • Take a look at the unassigned list of public comment issues. We will be working in-meeting on drafting responses starting at the top of the list.

Preparation for the 14 December meeting

Preparation for the 7 December meeting

Preparation for the 30 November meeting

  • If you have self-assigned an FPWD comment, please be sure to complete a draft response ASAP. These must be closed out prior to the next working draft.

NO MEETING: 23 November

Preparation for the 16 November meeting

Preparation for the 9 November meeting

Preparation for the 2 November meeting

Preparation for the 26 October meeting

Preparation for the 19 October meeting

Preparation for the 12 October meeting

Preparation for the 5 October meeting

Other work:

Preparation for the 28 September meeting

Preparation for the 21 September meeting

  • Read the three additional follow-up responses from Craig Keefner which is on my response thread. I'll be asking for agreement that these do not require further response other than to note their existence in the issue.
  • Be familiar with suggested changes per the closed functionality survey results, starting with SC 2.4.1 Bypass Blocks

NO MEETING 14 SEPTEMBER

Preparation for the 7 September meeting

Preparation for the 31 August meeting

  • Read the two follow-up email from Craig Keefner and the proposed response which was added to the existing issue comment. Suggest edits or make comments by 30 Aug at midnight Eastern.
  • Due 30 August: Complete the 2 question Closed functionality survey - updated proposals that has newer proposed language for 1.3.2 Meaningful Sequence and 1.4.12 Text Spacing.

Preparation for the 24 August meeting

Preparation for the 17 August meeting

  • Be familiar with suggested changes per the closed functionality survey results, starting with SC 1.4.10 Reflow, to help us move more quickly through the discussion and options for changes.

Preparation for the 10 August meeting

  • Be familiar with suggested changes per the closed functionality survey results, starting with SC 1.3.5 Identify Input Purpose, to help us move more quickly through the discussion and options for changes.

Preparation for the 3 August meeting

Preparation for the 27 July meeting

Preparation for the 20 July meeting

Preparation for the 13 July meeting

Preparation for the 6 July meeting

Preparation for the 29 June meeting

Preparation for the 22 June meeting

Preparation for the 15 June meeting

Preparation for the 8 June meeting

For those who are assigned to the Closed Functionality issue, continue filling in thoughts into the analysis spreadsheet. We will start from 2.5.1 Pointer Gestures and go to the last of the Level A and AA SC table.

Preparation for the 1 June meeting

For those who are assigned to the Closed Functionality issue, continue filling in thoughts into the analysis spreadsheet. We will start from 1.4.2 Audio Control and go to at least 1.4.13 Content on Hover or Focus, probably a few SC further than that.

Preparation for the 25 May meeting

For those who are assigned to the Closed Functionality issue, make sure you fill in thoughts into the analysis spreadsheet at least up to 1.3.4 Orientation.

Preparation for the 18 May meeting

  • For those who can help with the draft content, please self assign one or more of the Reflow issues (#159-162) and complete the Doodle poll to find an appropriate meeting time outside of our weekly meeting. The first we have to complete is #162 definition for CSS pixels/device-independent pixels
  • Form an opinion and/or draft content for the interpretation or replacement of the definition "CSS pixels" or alternate "device-independent pixels" term to use for this and other SCs and definitions that use this term. If you have draft ideas, add in a comment on Issue 162.

For those who are assigned to the Closed Functionality issue, begin filling in thoughts into the analysis spreadsheet

Preparation for the 11 May meeting

Preparation for the 4 May meeting

  • 1.4.10 Reflow: Read Mitch's comments and suggestions for alternative notes to the draft. Be ready for a discussion or have some alternatives ready to discuss. Feel free to add your thoughts to the issue.
  • 2.5.2 Pointer Cancellation adjustments to notes for consistency with 2.5.1 Pointer Gestures - see Issue 151 with the proposed changes to the 2.5.2 notes in the comment
  • Per Issue 104 - Review Pull request 152 to remove word substitution suggestions for the WCAG Intent sections

Preparation for the 27 April meeting

Preparation for the 20 April meeting

Preparation for the 13 April meeting

Surveys due by Midnight Eastern on 12 April:

Preparation for the 6 April meeting

Surveys due by Midnight Eastern on 5 April:

AG WG is also reviewing WCAG2ICT criteria in a survey that our TF can also answer:

Preparation for the 30 March meeting

Preparation for the 23 March meeting

Preparation for the 16 March meeting (and a bit beyond)

Upcoming deadlines for surveys:

Preparation for the 9 March meeting

Preparation for the 2 March meeting

Preparation for the 23 February meeting

Preparation for the 16 February meeting

Preparation for the 9 February meeting

Preparation for the 2 February meeting

Would love to bring the discussions on 2.1.4 Character Key Shortcuts and 1.4.12 Text Spacing to a conclusion this week with an agreement to incorporate with any agreed upon notes. If you have suggestions for modifying the proposals in the comments, please add a comment to the issue (links below) or have it ready for the discussion on Thursday.

Preparation for the 26 January 2023 meeting

Preparation for the 19 January 2023 meeting

Preparation for the 12 January 2023 meeting

5 January 2023 meeting preparation - no longer needed

NOTE: 5 January meeting was cancelled.

Preparation for the 8 December meeting

  • If you haven't already, complete the 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.

Preparation for the 1 December meeting

Preparation for the 17 November meeting

  • Complete the survey Initial look at proposals to gather your initial thoughts on proposed content. Simply read the content and document your thoughts in the survey. This is not final material, but we want to do an initial gut-check on the content before we write notes and have a detailed review.
  • Due on Dec 1: survey Review proposed changes to guidelines (try to complete earlier, if possible)

Preparation for the 10 November meeting

  • Look at the WCAG 2.1 items list in the WCAG2ICT project. This contains issues for ushering new success criteria from WCAG 2.1 into the document. Help me spread the work by choosing a success criteria to use the template on and start working to create the proposed content using the template. For the one you choose, add yourself as the assignee.

Preparation for the 3 November meeting

  • Complete the Discussions poll: Weigh in on possible new sections to add
  • Familiarize yourself with the Wiki Template for adding new success criteria to the WCAG2ICT document. This template can either be copied to a new Wiki Page, by editing the template and copying the GitHub markup content of the page. Then either paste the markup into a new WIKI page you created or into a comment in the issue you plan to work on. If we all want to have the template in the issue, I can boilerplate this into each issue to help things move more quickly.

Preparation for 27 October meeting

  • Make sure you have the ability to create a branch/make edits in GitHub.

Preparation for 20 October meeting

Get set up to practice using GitHub.

  • Either get set up so you have the editing environment on your desktop
    • Windows, MacOS, or Apple silicon Mac: Download & install the corresponding version of GitHub Desktop
      • Go to the GitHub WCAG2ICT repository
      • Use the Code dropdown to and then activate Open with GitHub Desktop to open the WCAG2ICT main branch
      • If you don't have the code cloned on your machine yet, you'll get a prompt to do that. So make sure you do clone (make a copy of) the code onto your computer.
    • Download & install a source code editor. This is up to your preference, but your co-facilitators use the following:
  • Or use the web interface for editing in GitHub. There won't be prep for you.

Preparation for 13 October meeting

Intro to GitHub:

  • Be prepared with your GitHub ID and password. We're going to log in and try some features out.
  • Read the GitHub instructions. During the meeting I'll demo these features live.
  • Think of any questions you have. I'll go further into GitHub features if things are clear.

Preparation for 6 October meeting

Goal: Reach consensus on all sections of the work statement during the meeting. NOTE: Any Scope of Work section changes agreed upon during this meeting will be added to the PR and incorporated into the document.

  • Contribute to 3 email threads regarding Work Statement Survey Question 2: Scope of Work. My original note contained all three topics which Gregg split into three discussion threads at: public-wcag2ict-tf archives
    • Whether or not to include Level AAA criteria in WCAG2ICT
    • Definition of non-web ICT covered by the WCAG2ICT Note
    • Publish WCAG2ICT as a W3C Statement instead of a WG Note?
  • Review updates to Pull Request 2682 to address comments received on all survey questions except Question 2: Scope of Work.
  • Review comments from the Work Statement survey to prepare for discussion
  • Gather thoughts on preferred collaboration tools (e.g. W3C's typical document development in GitHub, Google Docs, Microsoft Word, GitHub wiki). Be ready to express what you are comfortable with or if you are willing to attend training on GitHub and work there using basic HTML markup. If we can converge on a tool, we will; if that's not possible, it helps the chairs understand the level of coordination that might be needed to ensure everyone has the best Task Force work environment.

Preparation for 22 September meeting

Preparation for 8 September 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.

Clone this wiki locally