Chairs

From Education & Outreach

This page is for EOWG Chairs to keep notes, reminders, and planning discussions.

Chairs/Contact Weekly Review

For discussion

  • ...

Action Items

Current Issues

High priority:

  • action items above

Medium priority:

  • Documenting W3C Member support for EOWG @@link

Low priority:

  • Maintaining existing resources, open issues on many EOWG resources : List of issues in EO resources - note 1: it takes a few seconds to load ; note 2: some EOWG resources not in the list, and some in the list might not be EO resources
    1. First, ensure staff and chair support available
    2. Talk with EOWG about supporting the maintenance by reviewing issues, resolving or bringing to Planning/EOWG.
    3. Ask for volunteers to select a resource repository to watch and act upon
  • Developer needed for ARRM
    • Still a need? Check in with small group to update on progress and needs.

EOWG Work List

EOWG current projects

Weekly Updates

Wednesday after EO-Plan meeting:

Friday after EOWG meeting:

Project Management Liaison

  • open
    • How People with Disabilities Use the Web - update (Editor: Shadi)
    • W3C Accessibility Education and Outreach - documenting Member support (Project Lead: Kris Anne, at least for now)
    • Accessibility Roles and Responsibilities Mapping (ARRM) (Editor: Denis Boudreau)
  • Kris Anne
  • Brian
    • Tutorials - manage issues
  • Shawn
    • Make presentations & meeting accessible - update and expand
    • WCAG Support Docs Redesign - ARIA APG updates
    • Media resource - manage issues
  • Kevin
    • Web Accessibility Laws & Policies - update
    • Web Accessibility Evaluation Tools List - update (WAI-CooP project lead: Eric Velleman)
    • Easy Checks Next Gen (WAI-CooP project lead: Eric Velleman)
    • WCAG-EM Report Tool - manage update for 2.2 (WAI-CooP project lead: Eric Velleman)


Survey Notes

  • reminders
    • EOWG likes calendar invites to make it easier to schedule time to do the review.
    • EOWG appreciates an estimate of how long it will take to do the review (and survey).
    • EOWG has asked for frequent reminders. For longer surveys, you can set an automatic reminder. Good to also send e-mails. Easiest is to the list. Better is to individuals. From the bottom of survey results, you can "Send an email to all the non-responders" and then delete the in-active addresses.
  • How long open?
    • Often we want the surveys to close on Tuesdays so the editors can review results and present potential topics for EOWG discussion in the Wednesday EO-Plan meeting.
    • For approval to publish we often like to go over three weeks in case someone is out for a week, e.g., from at least a Thur to a Tuesday. However, sometimes that's not necessary.
    • Lots of people put it off to the last minute no matter what, so one approach is to set a close date and offer for people to ask for more time, e.g., put an option for "I will complete it by the date in the comments." However, that doesn't work well when editors schedule time to work on it the day after the survey closes.

Wording:

  • review vs survey — for Work for this week and e-mails, usually we want to focus the wording on doing the review rather than just completing a survey.
  • approve wording — Resources that are not official EOWG publications should not imply that EOWG approves (e.g., avoid "abstain", "not vote", "accept the decisions of the Working Group", etc.).
    • EOWG publications say in the footer: Developed by EOWG
    • others say: Developed with input from EOWG

Survey set up:

  • Who is allowed to see the results?
    • Generally EOWG survey results should be available to anyone.
  • Who can answer:
    • For Approval to Publish surveys: EOWG participants only
    • For most other surveys: Anyone (since we are encouraging input from beyond EOWG)

Resources

2023 Re-Chartering

EOWG 2023

Archived old notes

2017 Chartering

EO 2017 Chartering

Charter Info

Timeline

  ideal planned latest notes
EOWG approved charter,
AC review announcement
15 Feb   15 March  
AC review deadline 15 March   15 April 4 week review period
Comment processing 15 March-15 April   15 April-15 May  
Comments addressed 15 April   15 May  
Charter approved 1 May   31 May  

Possible work in scope:

  • expand translations of WAI resources - specifically, encourage and manage volunteer translations
  • Easy Checks - next generation (GitHub 9, and later version)
  • Components List
  • accessibility use cases for new & developing specs (e.g., @@Speak)
  • help with WCAG Understanding docs
  • improving coverage of cognitive throughout EOWG docs, e.g., How People with Disabilities Use the Web


charter announcement wording

first rough draft:

EOWG is designed for W3C Members to participate in the particular deliverables they are interested in, and not need to spend time on the others. EOWG conducts work via surveys, GitHub, and wiki, in additional to teleconferences, thus enabling asynchronous work outside of phone calls.

EOWG is working on several things you might want to participate in over the next several months, including:

EOWG is adding another teleconference time for more convenience in the Asia-Pacific and North American west coast time zones. Depending on interest, it might be monthly, bi-monthly, or weekly. Given end-of-year holidays, we expect to start the teleconference in January. If you are interested in participating in that teleconference regularly, please help us find a time that works best for the most people, by completing this poll: [link]

If you have any question about EOWG participation, please do contact the Chairs and Staff Contact via [<team-eowg-chairs@w3.org>].

revision suggestions / next draft: