> WAI Web site
redesign project
WAI Site UCD
Analysis Summary
Version: 2004.03.22
Note: This Web page is a working draft
and should not be referenced or quoted under any circumstances.
on this page: vision | users | tasks | information architecture | heuristic
evaluation | ideas for redesign
@@ this is summary. links to details@@ ... also link to UCD intro
The redesigned WAI Web site:
- is welcoming, encourages visitors to use the site; draws people in -
into the site, into WAI process, into Web accessibility
- "talks" to wide range of audiences, identifying needs and meeting
needs
- implements best practices: an inspiring model for graphic design/visual
appeal, accessibility, usability, technology; is elegant, uncluttered
- facilitates easy understanding of web accessibility issues; inspires
confidence that people can "do" accessibility
- is seen as the definitive (re)source, authoritative, credible;
comprehensive, yet not overwhelming
- fosters accessibility adoption and "evangelism"; increases positive
attitudes towards accessibility; is inspiring
User/audience analysis is documented in:
- The User Group List includes 32 user
groups that are organized as:
- web developers and content providers
- tool developers
- managers and assistants to managers
- related to contracts
- disability focused
- other (including standards developer, government
policy maker, educator, journalist, internal public relations,
researcher, W3C Team member, WAI WG member, Web accessibility
specialist, and more)
Primary user groups are:
- People who are new to Web accessibility
- Web developers
Most of the users fall into two categories:
- The User Matrix lists the Web
experience, HTML knowledge, disability knowledge, Web accessibility
knowledge, and frequency of use for each user group.
- Three primary Personas are:
- Martina Prado is a Web developer in
a small "shop" who prides herself on excellent visual design. She has
recently been heard to exclaim: "I'm just not sure which guidelines
to follow. What's the difference between the national standards and
the WAI guidelines?"
- Andy Petroff is a hard-core coder with
a software development background. Andy's knowledge of Web
accessibility is apparent in his statement: "I have a deadline, and
it's not like we have any disabled users anyway. I looked at the
server logs, I should know."
- Chandra Weesaw is an executive
assistant at a large university. She started researching Web
accessibility in preparation for a new work item to establish a
university. policy. She is following up at home to learn more about
Web accessibility in hopes she can help her mother who uses the Web a
lot (and even helps with the Web site of a non-profit group she
volunteers with) and has age-related diminishing abilities.
Additional personas include Web developer, Web accessibility specialist,
manager, student with a disability, educator, legislator, and reporter user
groups.
User/audience analysis reveals the following aspects that will heavily
influence the site design:
- Finding: There are a large number of different users
with very different characteristics and motivations.
Implication: Some content should be presented for novice
users - especially the highest level documents (including home page and
navigation pages) will need to err on the side of novice users. Some
advanced, technical documents can focus more on the experienced users.
However, because novice users are likely to end up on a more advanced,
technical document (from an outside link or search), it would be good to
make it easy for them to get to more simple, introductory documents.
- Finding: Almost all users have low knowledge of
disability and Web accessibility when they first come to the site; for
example, users don't know the basic language and concepts of Web
accessibility, WAI, W3C guidelines.
Implication: Important to support novices: for example,
have very basic introductory material "up front" as well as linked from
other documents.
- Finding: Many users do not visit the site regularly;
rather, they visit it often at first or when they are working on a
particular issue, and then visit it seldom or not at all other times.
Implication: In making specific design decisions,
easy-to-use for first-time and infrequent users is higher priority than
efficient-to-use for frequent users (with the possible exception of areas
and documents targeted for working group members).
Task/Purpose analysis is documented in:
- The Task
List includes more than 50 tasks.
- The Task-User
Matrix table shows how much of the time spent with the WAI site is
spent doing specific tasks, by each user group.
Information architecture work is still in development. WSTF expects to
have draft material for review in early April 2004.
WAI Site Heuristic
Evaluation documents an evaluation of the current WAI Web site.
A format for ideas for the redesigned site will be posted in early April
2004.
Document Information
@@ to do: check acronym tags, HTML & access check & validation
Editor: Shawn Lawton Henry. This Web page is is under development by the
WAI Site Task Force of EOWG. Last updated
$Date: 2004/03/22 22:15:00 $ by $Author: shawn $