Introduction

This option for the design of Silver is most oriented toward using user research and data to design Silver and write the requirements. All the intensive research methods will be in this option.

This process specifically addresses the goals:

Perspectives
Evidence & data
Scope

The emphasis for this process option is on:

Gathering a broad range of insights and perspectives.
Representing a broad range of roles and usage, so the outcome of the process better serves the full range of users and user needs.
Using investigative and integrative research and sense-making to explore diverse options.
Using evidence, data, and user perspectives to drive decision-making throughout the project.

Phase 1: Discovery

Understand needs, identify opportunities

User research

For the design-driven process, user research aims to understand and learn from people who use WCAG and people who are affected by WCAG.

These include people who use WCAG:

As a design specification, to guide decision-making in the design of digital products
As a technical standard, to build accessibility into digital products
To measure compliance, evaluating whether digital products adhere to standards
To document compliance, documenting accessibility in digital products
To support laws and regulations, as a baseline standard for policies, laws, requirements
To teach accessibility, providing design and technical guidance for teaching how to design and build accessible digital products

The roles include, but are not limited to:

Web visitors
Web/mobile application users
Web/mobile content creators
Web/mobile application creators
IT Implementors/Support
People who create adaptations of WCAG

Stakeholder map

What: Consolidate and communicate constituents and relationships
Why: Learn about stakeholders for Silver user research
How: Brainstorming session (phone or in person)

For the design-driven process, with its focus on user research and data, the stakeholder map is the foundation for the entire process. For this option we must take the time to fully understand the different roles and responsibilities that are affected by WCAG. An clear and comprehensible map will be a critical asset to the project throughout. The stakeholder map will need to be flexible, adapting we gather additional insights.

For the design-driven process, the stakeholder map will be:

Exhaustive: includes all roles with vested interest
Descriptive: shows roles and relationships
Iterative: evolves over process

Survey

What: Administer a survey
Why: Learn about experiences, perceptions of using WCAG
How: Online survey

Surveys can provide helpful general insights and perspectives. The design-driven process will use surveys, but will focus more on direct research (e.g, phone interviews and in-person inquiry). The surveys will be role-based, targeting key stakeholders to gain specific and defensible insights.

For the design-driven process, the surveys will be:

Targeted: customized for different roles
Credible: valid from a research perspective

Stakeholder interviews

What: Interview thought leaders, others on their use of WCAG
Why: Learn about experiences, perceptions of using WCAG
How: Could be done via phone

Interviews form the backbone of the design-driven process. The interviews will have structure, but will also allow for open discussion to learn how WCAG influences different roles. The primary purpose of the interviews is to understand all the different ways WCAG is used, its strengths and shortcomings, and the constraints we must consider when designing the next major version.

For the design-driven process, the stakeholder interviews will be:

Comprehensive: engages many perspectives
Structured: designed to answer key questions
Personal: phone and in-person interviews

Contextual inquiry

What: Combination of interviews and observation of use of WCAG
Why: Learn about experiences, perceptions of using of WCAG
How: Observe how people use WCAG (best done in person)

The value of contextual inquiry is that insights come from direct observation rather than reported perspectives. Observing processes and practices that use WCAG (e.g., for teaching, decision-making, etc) will show how WCAG supports activities, and ways it can be improved.

For the design-driven process, contextual inquiry will be:

Comprehensive: addresses multiple roles
Structured: designed to answer key questions
Unstructured: also open-ended, for unexpected insights
Personal: in-person observation

Self-reporting

What: Combination of interviews and survey/reporting on use of WCAG
Why: Learn about experiences, perceptions of using of WCAG
How: Observe how people report using WCAG (could be done via phone and with self-reporting vehicle)

Self-reporting provides the means to understand the context of use without in-person observation. For the design-driven process, self-reporting provides the means to get a more comprehensive view of how WCAG is used day-to-day for roles that are not included in the contextual inquiry activities. To be effective, the self-reporting method must be carefully designed, with specific objectives. Design of the self-reporting study should follow the in-person research, to fill gaps in understanding.

For the design-driven process, self-reporting will be:

Comprehensive: addresses multiple roles
Structured: designed to answer key questions

Research

For the design-driven process, research will focus on defining the problem space that we seek to understand and address with the next version of WCAG.

Secondary research

What: Collect and synthesize existing information and data
Why: Learn about standards evolution from comparable efforts with more data/evidence (look at HTML5)
How: Done through literature/article reviews and interviews

We can learn from parallel initiatives about how standards and guidelines can advance social change (e.g., LEED standards for sustainability in the built environment). We can also learn from other W3C efforts about how to evolve standards over time.

For the design-driven process, the secondary research will be:

Exploratory: looks into broad range of similar efforts, including those external to W3C and unrelated to digital accessibility
Summative: comprehensive analysis and articulation

WCAG analysis

What: Systematic examination of WCAG and its component parts, including the guidelines and the process of creating/maintaining WCAG
Why: Learn about the technical, cultural, and practical aspects of WCAG
How: Done through inventory and analysis

We must have a complete understanding of the various components that comprise WCAG, including the principles, guidelines, techniques, etc., as well as the process for maintaining WCAG. The next major version must address shortcomings not only with the guidelines but with the supporting processes that affect how the guidelines change over time.

For the design-driven process, the WCAG analysis will be:

Investigative: includes full breadth of WCAG components
Summative: comprehensive analysis and articulation

Analysis of WCAG adaptations

What: Systematic examination of secondary adaptations/interpretations/resources
Why: Understand the gaps adaptions seek to fill and how they differ from primary sources
How: Done through inventory and analysis

Different organizations have adapted WCAG. We must understand the drivers behind creating adaptations, and the gaps the adaptations intend to fill. We can also learn from how adaptions succeed or fail to meet their objectives.

For the design-driven process, the WCAG adaptations analysis will be:

Investigative: includes broad range of WCAG adaptations
Summative: comprehensive analysis and articulation

Literature review

What: Systematic examination of articles about WCAG
Why: Learn about the technical, cultural, and practical aspects of WCAG
How: Done through literature/article reviews and analysis

There has been a good deal of research, analysis, evaluation, and review of WCAG. We can learn from others about the strengths and weaknesses of WCAG, and where there are opportunities to build on successes and overcome shortcomings.

For the design-driven process, the literature review will be:

Investigative: includes broad range of WCAG research
Summative: comprehensive analysis and articulation

Communication

For the design-driven process, communication of the outcomes of the discovery phase will be thorough, with in-depth reporting of the results of the discovery phase activities.

Phase 2: Interpretation

Transform data into insights

Synthesis

For the design-driven process, interpretation of the perspectives gathered from user research will be accomplished using stories.

Case studies

What: Articles that capture details about how people use WCAG
Why: Understand how WCAG is used in different contexts
How: Subgroup members create case studies using discovery data and case study template

Case studies are a way to describe and illustrate how individuals and organizations make use of WCAG. They can serve as a reporting vehicle, focusing on describing the current state of WCAG use and identifying shortcomings.

For the design-driven process, case studies will be:

Comprehensive: addresses multiple roles and multiple uses
Detailed: illustrates roles and usage

Personas

What: Composite descriptions of people who use WCAG
Why: Understand the needs and preferences of people who use WCAG
How: Subgroup members create personas using discovery data and persona template

The process of creating personas helps with sense-making the insights and perspectives from the discovery phase. Once completed, personas are a resource that helps guide decision-making throughout the process.

For the design-driven process, personas will be:

Comprehensive: addresses multiple roles and multiple uses
Detailed: illustrates roles and usage

User Stories

What: Short stories describing how personas use WCAG
Why: Understand the various tasks and activities that WCAG needs to support
How: Subgroup members create user stories using discovery data and user story template

User stories, or use cases, are a means to put the personas in motion. They illustrate the needs of different stakeholders by demonstrating how different roles make use of WCAG in meeting the responsibilities of their role.

For the design-driven process, user stories will be:

Comprehensive: addresses multiple roles and multiple uses
Detailed: illustrates roles and usage

Analysis

For the design-driven process, analysis of the data, perspectives, and insights must produce common themes to pursue in the next version of WCAG.

Analysis / inventory / grouping

What: Identify themes/insights
Why: Choose key themes/insights to pursue
How: Subgroup members start building inventory remotely and refines together in a face-to-face workshop

We will gather many observations and perspectives during the discovery phase. We will start with a comprehensive inventory of key themes and considerations, and use grouping methods such as card sorts and affinity diagrams to understand the relationships between the themes.

For the design-driven process, the analysis, inventory, and grouping activities will be:

Informed: done by those who participate closely in discovery phase activities Participatory: done in person

Communication

For the design-driven process, communication of the outcomes of the interpretation phase will provide context through case studies, personas, and user stories, and rationale for the common themes and directions to pursue.

Phase 3: Ideation

Build insights and opportunities into possibilities

Concept generation

For the design-driven process, concept generation is founded on divergent thinking, gathering many different ideas from diverse perspectives.

Facilitated workshop

What: Workshop using design studio methodology
Why: Participatory design produces new ideas and involves stakeholders in creating solutions
How: Face-to-face workshops and online workshops

The design studio methodology is a structured approach to generating many possible solutions, then choosing and refining those that are viable. The basic framework is as follows:

Brainstorming: Take what we’ve learned from the discovery and interpretation phases and brainstorm options
- Generate ideas
- Group ideas
- Vote for ideas
- Discuss results
Sketch and refine: Take ideas and sketch/workshop them, refine them based on feedback
- Describe core values of approach
- Describe constraints

For the design-driven process, the facilitated workshop will be:

Participatory: run using Design Studio methodology
Comprehensive: engages many perspectives

Choosing

For the design-driven process, the subgroup will choose a subset of solutions to move to the experimentation phase. The subgroup will share the choices and rationale with the working group for approval.

Phase 4: Experimentation

Make possibilities tangible and testable and choose an approach

Methods

For the design-driven process, the experimentation methods will help narrow down options to one that is most likely to be successful and usable by WCAG stakeholders, and provide the greatest outcome for WCAG beneficiaries.

Prototyping

What: Turn solutions from ideation into prototypes
Why: Test the viability of different approaches in meeting needs and preferences
How: Subgroup builds out chosen ideation sketches into framework and components

Prototypes allow us to collect feedback early in the process and adjust our approach. We can develop prototypes at the broad framework for the guidelines down to individual components. The aim is to build out ideas just far enough that they are clear and can be used to elicit a response from stakeholders.

For the design-driven process, the prototypes will be:

Informed: done by those who participate closely in Silver process

User research on prototypes

What: Test prototypes with stakeholders Why: Evaluate the effectiveness of different solutions How: Utilize various UX methods to evaluate prototypes with users

Testing prototypes with users will allow us to determine which aspects of the prototypes are effective and which need refinement. User research will also help us choose which approach will work best. The following are some UX methods that we might enlist to evaluate the effectiveness of the prototypes:

A/B testing: Compare versions to see which works better for a given task
Focus groups: Present prototypes at conference and gather feedback
Desirability testing: Share prototypes and ask for basic response (positive, negative, neutral)

For the design-driven process, the user research on prototypes will be:

Informed: done by those who participate closely in Silver process
Clarifying: helps identify strengths of multiple viable options

Refinement of prototypes

What: Refine and consolidate prototypes
Why: Make improvements to different approaches to better suit stakeholder needs
How: Subgroup refines prototypes based on feedback

The insights from the user research on the prototypes will help us eliminate certain approaches and refine others so they better meet stakeholder needs.

For the design-driven process, the user research on prototypes will be:

Refining: incorporates insights to improve outcomes

Choosing

For the design-driven process, the subgroup will choose a prototype to move forward to the production and evolution phase. The subgroup will share the choice and rationale with the working group for approval.

Phase 5: Production and Evolution

Create Silver

Resources

The success of the design-driven process depends on the the availability of time, funding, and the availability of people with expertise to execute the process.

People and budget

Funding: Budget for workshops and face-to-face meetings
Time: Commitment of human resources to support the design-driven activities
Research expertise: Expertise to help design, develop, and analyze surveys and research studies
Subgroup: Small group of experts who value data- and design-driven decision-making and have time to allocate to the process activities
Facilitation: Subject matter expert for facilitation of process activities

Management

Schedule: Dates for key milestones (e.g., reporting progress, choosing options)
Communication: Plan for communicating progress

Production

With a design-driven process, production is more straightforward since the path forward was defined by the activities in the previous phases.

Production

Collaboration: Working meetings of subgroup (phone and face-to-face)
Distributed work: Subgroup members work independently on different components of Silver

Communication

Reporting: The subgroup will regularly share progress with the working group for review and approval.

Evolution

Since supporting evolution will be among the early considerations in the design-driven process, maintenance and evolution should also be more straightforward.

Maintenance and evolution

Ongoing support: Commitment of time and resources to sustaining user focus and research driven evolution

Return to Designing Silver home page