Requirements Analysis for Cognitive Accessibility Introduction

Background

The purpose of the existing page Cognitive Accessibility at W3C was to answer the questions:

• Does WCAG cover cognitive accessibility?
• What is W3C WAI doing related to cognitive accessibility?

(More info is in the Requirements Analysis for the "Cognitive Accessibility at W3C" Page.)

This requirements page is an initial draft of EOWG's idea to either:

• Change that page to meet other goals or
• Create a new page to meet other goals

For now, below is written as if it is an additional page — yet we might decide to have just one page.

A somewhat similar page is Older Users and Web Accessibility: Meeting the Needs of Ageing Web Users. A primary purpose of that page was to encourage people who were focusing on older users to use existing web accessibility guidelines and resources (rather than creating new ones just for older users). (Requirements for the Older Users and Web Accessibility page)

Purpose

• Provide a consumable, short, welcoming introduction to accessibility for people with cognitive and learning disabilities (“CaLD” and “cognitive accessibility” for short just in this internal document).
• Direct people to related resources with more information.

Objectives

• People get an idea of the scope of cognitive accessibility.
• People are compelled to make their products better for people with CaLD.
• People easily get to more info for their specific interests:
  • Everyone who wants to understand CaLD more – get to https://www.w3.org/WAI/people-use-web/abilities-barriers/#cognitive
  • Designers, developers, and content creators – get to the Design Patterns.
  • Project managers – get to the Planning and Managing suite, and the Involving Users pages.
  • Usability professionals – get to the Involving Users pages.
  • Policy makers get to Cognitive Accessibility at W3C
  • Advocates get to the relevant Perspectives Videos and the Business Case

Audience

Primary audiences for this page:

• Developers
• Designers
• Project managers
• QA testers

Also:

• Cognitive accessibility advocates
• Accessibility specialists

Open Issues

• What are the pros and cons of expanding the existing Cognitive Accessibility at W3C page to cover these different goals, objectives, audience — vs. creating a new page?
• If we used the existing page, would we change the title? Would we change the location in the IA, e.g., put it under “Accessibility Fundamentals”?