Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SCOPE] Scope document - Navigating the WAI website - expand Audience and User Stories/Use Cases #33

Open
Different2day opened this issue Nov 6, 2024 · 0 comments

Comments

@Different2day
Copy link

Different2day commented Nov 6, 2024

Title of Resource

Scope - Navigating the WAI website

Current scope text

Audience

Anyone interested in learning about (or more about) web accessibility at any stage of their career.

Primary

  • Developers
  • UX Designers
  • Educators

Secondary (if appropriate)

  • Procurement specialists
  • Project managers
  • Executives

User Stories/Use Cases
Guiding someone through WAI resources based on their familiarity with web accessibility.

  • Beginner
  • Intermediate

Someone looking for vetted resources to teach others about web accessibility.

  • Teacher
  • Trainer

Suggested scope text

Audience

Anyone who visits the w3.org website to learn (more) about web accessibility.

We assume users with varying knowledge, interests, and roles. These factors shape their experience as they navigate the site and engage with its content.

Domains/subtopics

Accessibility/Usability

  • W3C accessibility standards and conformance (WCAG and other standards)
  • Accessibility beyond standards and conformance
  • Disability and impairments (sensory, cognitive, motor)
  • Ethics

Design

  • User-centered design
  • User experience design
  • Visual design
  • Content design (language, content writing)
  • Digital product design
  • Timed media design

Technology

  • Development (specific systems)
  • Systems architecture and integration
  • Assistive technology
  • Technical testing and testing technology

Educating in any of these domains/subtopics

Role/Perspectives examples

Primary user groups

  • Developer
  • UX Designer
  • Product Owner
  • Tester
  • Accessibility Professional
  • Educator
  • Affected individual (individual with impairments)
  • Advocate for affected individuals
  • Students who wish to learn about accessibility (secondary, tertiary education)
  • Anyone who wishes to create accessible pieces of media or raise awareness on the topics, such as: content creator, media outlet representative, presenter, speaker

Secondary user groups

  • Procurement specialist
  • Project manager
  • Executive
  • Anyone involved in any of the W3C groups

Level of current understanding

  • Beginner
  • Intermediate

Potential milestones

  • Refine perspectives
  • Create personas if useful
  • Identify information-seeking goals

User Stories/Use Cases

Usability goals:

Users succeed if they can:

  • Navigate the website with relative ease and maintain their orientation.
  • Find resources that align with their interests, goals, abilities, and familiarity with accessibility.
  • Understand the content and gain knowledge without undue confusion.

Potential milestones

Identify user stories/use cases

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.

  • Expand user groups to include affected individuals, members of the public
  • Gain clarity on what contributes to challenges in understanding accessibility-related content. Spelling out the sub-domains may potentially be helpful, as accessibility lies at the intersection of these subdomains.
  • Simplify by gaining clarity on the different user's perspectives.
  • Use the insights gained to create helpful guidance materials and propose website and website content updates.

Issue raised by

Anya Sims

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant