Jump to content 
Important notes:

This page is archived information that is not up-to-date.

Information about EOWG closing is in the 19 September 2024 blog post: Accessibility education and outreach: Another milestone in W3C's 30-year history and evolution.

This Wiki page was edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Improve Discoverability and Integration Requirements Analysis

From Education & Outreach

Purpose, goal

Improve the discoverability of WCAG 2.0-related resources on the W3C WAI Website, and support integration of new and existing WCAG 2.0 resources into the search interface.

Audiences, use cases

  • Managers, evaluators, and procurement specialists can find a role-based introduction to web accessibility, with links to supporting resources
  • Web and app developers can find what types of technical and educational resources are available to support understanding and implementation of WCAG 2.0.
  • Web and app developers can search for technical and educational resources by keyword, or by type of technical or educational resource.

Objectives, tasks

Develop role-based introductions for managers, evaluators, and procurement specialists

  • Update managers' and evaluators' draft introductions
  • Draft new content for procurement specialists
  • Identify key resources to link to while avoiding redundancies

Figure out how & where to fit with the new information architecture from the website TF

  • Update icons to match (coming) graphic redesign?
  • Home page, header, footer entry points? (Discussion: are home-page entry points possible or not?)

Improve search options; pros and cons; possible approaches...)

Next steps

  1. EOWG review requirements
  2. Draft role-based introductions, and add resource linkages
  3. Develop search approach and plan integration with new information architecture

Notes, issues

  • Must be able to clearly demarcate previous work from new USAB-sponsored work. For the three roles of managers, evaluators, procurement specialists, WAI-DEV work did not proceed past a draft, and did not include introduction to resources. Clarify attributions going forward.
  • Discussed and agreed, but see note below: "procurement" quick tips replacing "management" quick tips.

Links

Detailed Next Steps

Complete "Tips for Advocating for Web Accessibility"

  • Review existing draft & note remaining issues to address
  • Discuss key questions
    • Is the scope of the existing content more "Advocating" or "Promoting"? Seems more like the latter?
    • What are our priority audiences for this resource?
    • Which resources do we have the best opportunity to highlight through this "Tips" page?
    • Does EOWG have sensitivities about potential negativity? For instance, any problem with adding a first (or early) action tip called "identify barriers"? (Current "assess key issues" seems like a meta-step after identifying barriers.)
  • Outline remaining work
    • Confirm a useful range and focus of individual "tips" for this topic (individual websites? individual organizations and companies? market sectors? local, regional, national governments? etc.)
    • Populate "examples"
    • Highlight "for more information" resources

Complete "Tips for Evaluating Web Accessibility

  • Review existing draft & note remaining issues to address
  • Discuss key questions
    • Are we confident that a completed "Tips for Evaluating Web Accessibility" would not be redundant with existing WAI resources regarding evaluation of Web accessibility?
    • What would be the most important differentiators between this and other resources?
    • The completed tutorials have engaging graphical examples under most of the individual tips, as well as "for more info". Are there particular examples that EOWG advises highlighting?
  • Outline remaining work
    • Process Open Github issues
      • Add a tip on prioritization of repairs
      • Add description of work underway on an accessibility conformance evaluation framework(?)
      • Add examples for each tip
      • Add "for more info" for each tip

Create "Tips for Procuring Web Accessibility Applications and Services"

  • Propose audience and scope
    • procurement officers within government; purchasing/commissioning within organizations & companies
    • practical considerations; potential legal/policy obligations
    • where is: old draft on commissioning website accessibility & does EOWG have plan for that, or convert some of old content to "tips" format?
  • Discuss key questions
    • Right audience & scope?
    • Right range?
    • Initial thoughts on Tips topics?
    • Careful of overlaps with "managing" resources(?/!)
  • Draft outline (Very Drafty)
    • Intro to focus & scope
    • Tips (again, very drafty)
      • Assess/Address organization's accessibility goals and/or obligations
      • Assess/Address organizational needs in terms of complexity of website(s) and content development
      • Assess/Address contracting external needs vs developing internal expertise vs hybrid
      • Assess/Address software/application needs
      • Develop internal accessibility-central resource area to coordinate approach

Support

U.S. Access Board, WCAG TA Project, Task 1

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