Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

2020 Update Project Page

Jump to bottom
Shawn Lawton Henry edited this page Apr 5, 2024 · 11 revisions

Existing resource: How People with Disabilities Use the Web

Requirements Analysis

Purpose/Goals/Objectives

@@

Audience

Previous audience focused on designers and developers, and it has shifted to a broader audience. [slh not sure about that previous audience?]

Primary audience for this resource:

  • People new to accessibility and interested in the human element
  • Designers looking to understand digital barriers

Secondary audiences for this resource:

  • Accessibility specialists looking for materials to support advocacy work
  • Developers and testers looking to understand how assistive technology is used
  • Developers looking to understand how success criteria related to lived experience

2020-2021 Update Project

Background

There is an opportunity to review and update the resource to better reflect mobile web usage which is much more prevalent than when this resource was developed. There is also a need to explore how cognitive impairments are covered within the resource, and work with the COGA Task Force to better integrate with Making Content Usable for People with Cognitive and Learning Disabilities. The impact of broader WAI design and tone changes also need to be explored to determine how to better reflect the new style in this resource.

Approach

Scope

The review will consider the existing resources:

Additionally, edits for alignment may be needed to the follow page that was previously part of the resource suite before being moved:

Any recommendations for change will be confined to the content within the existing visual styling of the WAI site. Recommendations will be confined to the objectives as outlined above and any feedback already received on the existing resource via GitHub.

Project Plan

Target publication date: by mid-November 2020 in 2021 along with videos.

This is an early draft for planning purposes. This will be refined within the next week.

  1. Conduct gap analysis between existing stories and other disability personas including COGA materials. Goals:
    • Identify opportunities for additional stories – there are two cognitive or learning impaired related stories. We need to review how these align with the COGA document to determine if they are sufficient or if there is a need to include additional stories.
    • Identify opportunities for improvements in presentation, for example, including quotes or changing tone – concern that any quotes are ‘made up’. These are much more personal and it would be important to ensure that they are as real as possible. This could benefit from sharing proposed rewrites with representative groups and asking for input?
  2. Review existing information architecture. Goals:
    • Prototype of options with rationale for change. For example, structure of individual stories, changing high level section titles or presenting in a much more integrated way (i.e. everything in one story)
  3. Review existing feedback and present options. Goals:
    • Identify opportunities to weave mobile considerations into selected relevant stories. For example, is mobile harder for Lee in harsh lighting conditions, does Alex use a mobile or tablet to respond to emails as it puts less strain on her wrists, does a mobile or tablet provide Preety with more flexibility in how books are presented, has Yun adapted to using a tablet or a voice activated interface (sorry, don’t know collective term for Alexa, Siri, Cortana), are there other phone apps that help Luis, how does Kaseem’s technology integrate with her mobile?
  4. Develop initial draft of story format. Goals:
    • Explore options for structural presentation. For example, simplify each story to include the story, what helps, what hinders, tools used.
    • Review Diverse Abilities and Barriers and Tools and Techniques, in particular how they relate and integrate into the stories. Do they need to be so interconnected or is there scope to decouple them a little bit and reduce all the interlinking? This would be with a view to making each part of the resource more coherent in and of itself.
    • Review tone of each story to make it more personable and consistent across the whole resource.
  5. Develop draft pages. Goals:
    • Rewrite stories
    • Rewrite abilities and barriers
    • Rewrite tools and techniques

Points for review (dates TBC):

  • Squirrel review on overall requirements and outcomes
  • Eagle review of suggestions for additional stories, options to change information architecture and early ideas
  • Eagle review of early prototype
  • Starfish review of late stage prototype
  • Monkey review of final product
  • Butterfly approval

Project Pages

  • [https://w3c.github.io/wai-people-use-web/people-use-web/mockup/ mockup of draft user stories re-designed]
  • [https://github.com/w3c/wai-people-use-web/wiki/Persona-gap-analysis persona gap analysis] ** [https://github.com/w3c/wai-people-use-web/wiki/Questions-from-gap-analysis questions from gap analysis]

Other:

Clone this wiki locally