EOWG 2023

From Education & Outreach
This page is for visioning accessibility education and outreach work for a potential new EOWG Charter in 2023

EOWG charter info

Note: Current charter is extended though 31 December 2023.

2023 info:

Previous info:

W3C process requirements and guidance:

Considerations

  1. What the world wants EOWG to do.
  2. What is appropriate for EOWG to do. (example of what is not: paid consulting on legal policy development)
  3. What W3C Members want EOWG to do. and:
    • What EOWG participants want to do.
    • What other W3C Members won't object to in a charter.
  4. What we can get resources for, e.g., Members provide editors.

notes:

  • Perhaps focus less on creating new resources, and now focus on improving resources and site through usability research. [Jade] +1[Shawn]
  • What analytics data would be useful?
  • Scope: Support W3C Working Groups (not just WAI, also things like Publishing).
  • What are the challenges to getting accessibility actually addressed. [We know a lot...]

Updating Resources

EOWG Resources Appendix below.

Input on what are priorities or not to update:

  • Update WCAG-EM Report Tool for EN 301 549

Potential New Resources

In addition updating many existing resources and the new resources already listed in the Deliverables, draft charter, EOWG is exploring these potential new resources:
  1. Accessibility around the world - potential EOWG resources - EOWG add your thoughts
  2. Evaluation Resources Analysis - EOWG add your thoughts
  3. EPUB education and outreach planning - EOWG add your thoughts
  4. Procurement Guidance Analysis - EOWG add your thoughts
  5. Children and Web Accessibility Requirements Analysis - drafting in progress

We welcome all input! If you are not an EOWG participant who can edit these wiki pages, please send your input to the publicly-archived mailing list: wai-eo-editors@w3.org

Background: Deliverables Brainstorming

See also EOWG Current Work, Upcoming, Pending, and Potential Work and new charter deliverables

Ideas for potential new work:

For discussion

  • Consider developers who don't know HTML and how that impacts potential edits to existing resources or new resources
    • If we "speak" in HTML, do developers know it or are they just using set libraries of components or frameworks?
    • We can't assume a certain skill level. Can we adjust that? Add guidance on how to evaluate libraries and frameworks for accessibility. Based on skill level?
  • Are there resources that EO no longer wants to maintain?
  • Evaluating designs for accessibility seems to be missing from the tutorials list. It would be great to describe an expert review and an inclusive review and to include techniques like screen reader read-downs. [Len] — comments move to Evaluation Resources Analysis

New content

  • [ACTION: needs more clarification to become potential deliverable] Path through resources, noting level of resources (e.g., beginner versus more advanced), moving beyond basic knowledge to implementation [Jade]
    • People may be looking for differentiated learning as knowledge is increasing.
    • But also if you're new - is there a path through? A getting started "Path" through learning? Visual design to help people know where to go?
    • Different paths for basic vs. advanced learning.
  • Very short (1-3 minutes) screen captures with voice-over of quick ways to address accessibility [Brent]
    • Subject-specific, quick learning.
  • More resources around supplemental guidance for Low Vision [Brent]
    • Working with other groups can be part of the charter.
  • More resources around cognitive disability support [Brent]
  • More resources about how to embed accessible procurement processes/the realities of procurement (Jade) — input moved to Procurement_Guidance_Analysis
  • Alternatives to PDFs, ways to help organisations reduce PDFs, options for creating accessible PDFs (Jade) — related potential deliverable: EPUB education and outreach planning
    • Also just cutting down on them in archives.
    • EU is advocating an HTML first.
    • Guidance around PDF's or pitfalls around PDF's.
    • Do we need to produce all of this documentation anyway? With the increase in mobile device use, it doesn't work well. Options for people PDF or EPUB. [Jedi is a good resource for real-world experience on this]
  • Increase knowledge around EPUB and what opportunities to help, maybe we need to say more about it in our resources. — potential deliverable: EPUB education and outreach planning
  • [ACTION LEN - please read https://deploy-preview-113--wai-people-use-web.netlify.app/people-use-web/abilities-barriers-cognitive/ and submit specific suggestions in GitHub] Would love to see photophobia, vestibular disorder, dyscalculia and other disabilities on Stories of Web Users. These would show how content thinking lead to better design for more people. [Len]
    • Github stories written for Cognitive section. [Len Sept 8]
    • [Len is a good resource for this - has worked on some of these topics in his work]
    • Where and how we might want to put this information in Abilities and Barriers
      • I think the following current patterns in Diverse Abilities and Barriers section page will be fine. New disabilities listed above would fit nicely into Cognitive & Learning and the Visual pages. [Len]
  • Resource (or resources) around WCAG localization... [Jedi] — notes moved to Accessibility around the world - potential EOWG resources

New resources

  • [added to charter] Downloadable attributes/logos to demonstrate that we're using WAI resources (Jade)

Updates to existing content

  • Update current EOWG resources — This is a significant amount of work, e.g.,
    • some things need updating for WCAG 2.1 and WCAG 2.2
    • there are a lot of open issues on EOWG resources
    • Perhaps user research to help prioritize work
  • bite-size info, modularized, filterable, customize view
  • [ACTION: needs more clarification] Extending the developer training curricula to incorporate other types of developers (Jade)
  • [ACTION LEN: please add this as a GitHub issue on the tutorials] Can we add more user notification examples to tutorials? We have one in forms, but this doesn't cover other scenarios mentioned un Understanding 4.1.3. [Len]
  • [ACTION LEN: please add this as a GitHub issue on the tutorials] It would be great to have a tutorial for designing and developing data visualizations / charts. [Len]
  • [ACTION LEN: please add this as a GitHub issue on the tutorials] Can we add some 'phrases to avoid' in the Form Instructions (Forms Tutorial)? For example, "simply fill out this quick form" is ableist and can set the wrong tone for the user's ability to complete the task. [Len]

Updates to existing copy

  • Can we work on bringing readability scores up above 50% and possibly reduce the grade reading level base? I work with several people who need this content translated for them. Their cognitive disabilities find it hard to read and comprehend some of our content. [Len]
    • [shawn question for @@Len]: is this mostly the WCAG Understanding docs? or EOWG resources? IF EOWG resourceds, which ones?

Support/community

  • outreach (people not aware of all of our resources)
  • Many WAI Working Group deliverables need technical editing for readability (and thus meeting WCAG). How can EOWG support that? (We previously tried EOWG group copyediting, and that didn't work.) Perhaps supporting embedded editors? [Shawn]
  • Contributing to WCAG 3 design, ARIA APG, and how all of this will fit into the whole WAI website.
  • liaison with community group (existing WAI-Engage or new on E&O)
  • Accessibility for Children's White paper - possibly to turn it into a resource, similar to the Older Users resource for specific info and research about accessibility for children

Surveys

Survey 1 : EOWG Participation

misc notes:

  • Is the meeting time limiting participation? Would chaning the meeting time increase participation?
  • What else would increase participation? More comfortable orientation and "onboarding"? Actively providing content to specific deliverables? other???

Survey was conducted in @@ 2023 and to encourage frank input, the results were only provided to EOWG Chairs and W3C Team.

Survey 2: EOWG deliverables

Goal: What do W3C Members want EOWG to do under the next charter? And, what not?

Target audience for survey: W3C Members, particularly: 1. Those interested in accessibility, 2. AC Reps who will vote on the EOWG Charter.

Plan: 1. Develop survey, 2. Ask all EOWG participants to complete survey (including non-active participants). 3. Refine the survey, 4. Encourage wider survey input.

@@ survey tool ; results visibility ; anonomous

misc ideas

  • Survey now to provide input into charter. Then possibly later surevey on more specifics.
  • Where the resources aren't supporting users needs? Which resources? Why not? ("What didn't meet your expectations." except we don't know their expectations)
  • Instead of just check which resources do you like, ask the link between guidance and practices. Please give examples of how you use EOWG resources in your organization. [Jade]
  • Where do you do to get accessibility information?
  • Important wording note: Be careful of "your organization" since that will limit what people can say.

Re-Charter Timeline

  inital plan done notes
Survey W3C Members July 2023 didn't (lots of Europeans and some other take off lots of August)
Discuss with EOWG, WAI CC, WAI staff, AC reps and others to draft deliverables July-August 2023 done  
Draft and refine though EOWG August 2023 in-progress  
Send draft to AC & others - Advanced Notice - Request feedback and input 1 Sept 7/8 Sept
W3T Strategy - Horizontal review 1-15 Sept requested 7 Sept ? is 2 week review period sufficient, especially given TPAC is 11-15 Sept
Promote & get support for charter at TPAC! 11-15 Sept   (11-15 Sept is TPAC)
EOWG approve draft charter 15 Sept   (11-15 Sept is TPAC)
W3C TiLT approve proposed charter 20 Sept-4 Oct in pipeline 7 Sept is 2 week review period sufficient?
AC review announcement 4 Oct   (for example: 30 April e-mail)
AC review deadline 5 Oct - 2 Nov   28-day review period required
Comment processing 2 Nov -
7 Dec		   (plan has 5 weeks for this — although it shouldn't take that long!)
(note US Thanksgiving holidays 23-24 Nov)
Comments addressed 7 Dec    
Charter approved and announced 12 Dec   Many people take off the last couple weeks of December.
(current charter ends 31 December 2023)

Appendix: EOWG Resources

Retrieved from "https://www.w3.org/WAI/EO/wiki/index.php?title=EOWG_2023&oldid=39345"