This Wiki page is edited by participants of the Cognitive and Learning Disabilities Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.

Design Guide

From Cognitive Accessibility Task Force
Jump to: navigation, search

This page is to explore the way a Design Guide can be extracted from the content usable for an interactive version aim at developers


  • Audience: 1: content providers, creators and developers 2) policy makers and others wanting guidelines
  • Purpose: provide Patterns that can be readily applied to content and will improve cognitive accessiblity.
  • Structure: A set of Patterns grouped into Objectives. Each pattern includes instructions, explanation of how it helps, examples and links to related documentation such as user requirements in the Gap Analysis.
  • Format: Currently part of a W3C TR Note. Exploring an interactive web resource.

Published Format

Currently this is an appendix of the Content Usable Editor's Draft W3C TR note.

The target audience are likely to be better served and prefer an interactive web resource on the W3C WAI Website


Review of current version for migration to web

Comments by Steve Lee (talk) on the latest published iteration as we think about the transfer across to the web version.

General Observations

tl;dr; make sure is a succinct 'what to do guide' for developers. Extract and link all "secondary" content that supports this.

User story: As a designer or developer I want to know what to implement with just enough background to set the context and explain why. If I need more info, for example to better understand the users or to check edge cases, I want links to the details.

See the working [1] for discussion of possible changes from the TR note document.

Easy Reading project

These resource are also of interest to the Easy Reading project which features:

  • Adjustment of layout and structure of web-pages
  • Explanation of web content with symbols, pictures and videos
  • Translation of content into a different language level, e.g. Plain Language or Easy-to-Read, symbol writing systems

The software provides these (semi-)automated support features by using Human-computer interaction (HCI) techniques like pop-ups, Text-To-Speech (TTS), captions through mouse-over or eye-tracking. This allows the user to remain and work within the original digital document.

List of candidate Patterns for Web Version

  • Help users understand purpose and interactions
    • Clearly identify controls and their use
    • Use symbols that help the user
  • Help users find what they need
    • Ensure most important things are easy to find
  • Use clear and understandable content (select a couple of these)
    • Use clear words
    • Use simple language
    • Do not use double negatives or clauses inside clauses
    • Use literal language
    • Keep text succinct
    • Use white spacing
    • Use clear and accurate text formatting and punctuation
    • Provide alternatives for numbers
  • Help users avoid mistakes or correct them
    • Use clear labels and instructions
  • Ensure processes do not rely on memory
    • Ensure log in does not require good memory or cognitive skills
  • Provide help and support
    • Make it easy to find help and give feedback
  • Support Adaptation and Personalization
    • Support Simplification
    • Support Personalisation

Name mapping

The names in the design guide are currenty in consistent in 'voice' and style and some are much to long. The web version needs shorter more consistent titles