Design Requirements
From ATHEN
A set of Design Requirements is the outcome of a multi-step process, which includes the following steps. Ultimately each step will probably be organized into a separate page, and assigned separate working groups.
In an earlier outline, Saroj documented the following points related to Design focus, which I'm pasting here for now so it doesn't get lost:
- Accessibility of UI (user interface) and access to content for total environment and all tools
- Provision for alternative outputs
- Built-in authoring tools that promote and facilitate crafting of accessible content
Contents |
Functional Requirements
This section will document cognitive and physical functional requirements for different disabilities, clearly delineating the cognitive, processing, physical and sensory tasks people need to perform to functionally use web applications and tools.
Best Practices Guidelines
This section documents best practices guidelines, based on the functional requirements from the previous section.
Design Requirements
This is the ultimate goal - translating the best practices guidelines into specific requirements for developers.
Resources
From Saroj:
There are a number of pretty good specifications and guidelines that can serve as a framework for translating user functional needs to design specifications that are needed by developers. They are long and can be hard for non-disability professional to understand and follow.
