[SCOPE] Scope document - Navigating the WAI website - expand purpose and scope

[Different2day]

Title of Resource: Scope - Navigating the WAI website

Current scope text

Purpose
Creating a resource that helps people navigate the WAI website.

Scope
Create a new resource with links to specific resources or sections of the WAI website based on need and usability level.
Create new tags for existing WAI pages for users to search for or filter on.

Suggested scope text

Purpose
Improve user experience for users visiting the W3C website to seek information about accessibility

Scope

• Identify key usability challenges (heuristic evaluation)
• Assess challenges
• Compile targeted improvements
• Select the best method
• Implement the method

Rationale

These are just my thoughts, raised in case they are helpful. I appreciate that I may not have the full picture on what’s intended.

1. Expand Scope Beyond WAI

Many visitors navigate W3C content as a whole, not distinguishing WAI from other sections. Extending the scope to include relevant W3C pages aligns with this natural user flow.

2. Include Key W3C Sections Relevant to Accessibility

• Technical Reports (TR): accessibility-tagged documents provide essential information on accessibility standards and guidance
• Standards and Review Processes: clarifies the framework and provides essential context around accessibility standards at W3C
• Liaisons, Groups, and Ecosystems: broaden understanding of the eople, organisations and lawmakers involved in accessibility, for those interested in this context
• Developers: shows the specific context presented to developers when accessing W3.org and offers a link to WAI tutorials
• Translations: demonstrates how accessibility is supported and expanded globally through translated resources

(for site section URLs see below)

3. Shift Purpose to a User-Centered Goal

Reframe the purpose to prioritize user experience, focusing on:

• How easily users find and understand accessibility content.
• What usability challenges they encounter (using heuristic evaluation and, if possible, light user research).

4. Keep Methods Flexible to Address Challenges Effectively

Flexibility in methods allows us to identify issues first and adapt solutions as needed. Potential milestones listed above, under "Scope"

Some early ideas on areas to address/develop:

• Complex navigation and inconsistent templates across sections.
• Terminology variations that may lead to confusion.
• Inconsistent or missing references to standards, such as WCAG and related documentation.
• Improved orientation aids and restructured overview sections to better support mental mapping.

Detail to point 2: Examples for relevant non-WAI site sections

• W3C TR (especially accessibility-tagged TRs)
• Standards Types
• Review Processes
• Liaisons
• Groups
• Ecosystems
• Developers (links to WAI tutorials; why only a page for developers?)
• Policies
• Resources (lacking a clear WAI link)
• Translations (especially WCAG translations)

Issue raised by:

Anya Sims