W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2009

On test suite pages

From: <Anna.Zhuang@nokia.com>
Date: Fri, 20 Feb 2009 13:53:37 +0100
To: <w3c-wai-eo@w3.org>
CC: <judy.brewer@w3.org>
Message-ID: <D1E1C1C072023846AC4A55088BAA4B033094927DC6@NOK-EUMSG-04.mgdnok.nokia.com>
Dear EOWG,

We were actioned to review and comment "Evaluating Web Sites for Accessibility" and here are my ideas.

First have a look at RNIB http://www.rnib.org.uk/xpedio/groups/public/documents/publicwebsite/public_testing.hcsp
And WebAIM http://www.webaim.org/articles/
I myself have had more than one look at these two sites and that's where my look remains. Not on "Evaluating Web Sites for Accessibility" pages, sorry. This is both feedback and suggestion in one.

The current testing resource has too many pages that do not deliver distinct message and don't grab one's attention. (most of the titles, not all). The content of the pages feels to be overlapping.

OK, OK, we were supposed to provide some ideas.

Each page has its own introduction. There should be one high level introduction and other pages should represent different parts of the testing story. Need to isolate those parts.

It would be good to have a couple of downlaodable Templates for Accessibility Evaluation Reports.

Separate testing and maintenance into different subjects.

The very bottom of this e-mail has a collection of the headings I gathered from al the pages in this resource. Just for reference.

There should not be too much emphasis on automated testing but rather on manual  and semi-manual testing. Automated testing is feeding a URL to a website and getting a report or having an installed tool to examine and report. Manual testing needs to be explained as many tools and toolbars are the aid in manual testing and although being tools they are not automated testing tools.

Need to link what is to be tested with how it is to be tested.

Give more attension to the browser toolbars.

Explain how to maniputale browser settings to achieve needed tests.

Testing tools search engine should be a collection of tools one can filter by search criteria and only search engine. Due to the fact that tools greatly vary in their form and yield, the main guiding page on which tools to use when and how should be the page explaining which tools can help testing which feature and such page can/should contain the link to filtered out list of aids for each testable feature.

Below is the sample site map that I produced. Titles are not refined, just want to capture my ideas. All entries that appear with * are the titles to appear on the same page and have dedicated second level pages.

* Introduction
* Evaluation checklist
---> How about having the actual checklist template?
* When to test
---> Testing at design phase
---> Testing at implementation phase
---> Testing at conformance evaluation state
---> Testing at the maintemance phase
* How/what to test
---> some intro: manual vs. automated
---> images switched off
------> (for each testable item in the list)purely manual accessment guidelines
------> what browser settings to manipulate
------> what kind of tool could be useful
------> necessary links to the tools and other pages
---> sound switched off
---> contrast test
---> markup validators (must be at the top of the list)
---> all other areas to be tested
* Testing aids
---> explain testing with different browsers, where to change settings
---> non GUI browsers, what to test and how
---> screen readers, how to user them
---> browser toolbars
---> colour contrast and other checkers
---> magnifiers
---> anything else
* Automated testing tools
---> One page or the whole site?
---> selecting sample pages
---> classification of the tools
* User testing
---> involving users with and without disabilities
---> when to involve users
---> User Testing at design phase
------> How about some checklist what designer can ask user to test at each phase
---> User Testing at implementation phase
---> User Testing at conformance evaluation state
---> User Testing at the maintemance phase
* Result analysis
---> Analyzing results from user testing
---> Analyzing reports produces by automated tools
---> Combining results from different sources
* Reporting
---> Accessibility accessment report templates
* Testing tools search engine


>From the current resource:
==========================
Select a representative page sample
Examine pages using graphical browsers
Examine pages using specialized browsers
Use automated Web accessibility evaluation tools
Summarize obtained results
Determine the scope of the evaluation
Use Web accessibility evaluation tools
Manually evaluate representative page sample
Apply accessibility checklist to page sample
Examine pages using graphical browsers
Examine pages using specialized browsers
Read and evaluate page content
Evaluation during the development process
Ongoing monitoring
Evaluation of legacy sites
Evaluation of dynamically generated Web pages
Involving Users Effectively
Including Diverse Users
Analyzing Accessibility Problems
What evaluation tools can do
What evaluation tools can not do
Considerations for selecting evaluation tools
Usages of evaluation tools
Features of evaluation tools
Finding Evaluation Tools
Recommended Expertise
Approaches for Collaborative Evaluation
Considerations in Combining Expertise
Template for Accessibility Evaluation Reports

Br, Anna
Received on Friday, 20 February 2009 12:54:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:57 UTC