Quality assurance docs/testing
Hi ppl,
I have been a regular reader of the accessify website for some months now and am a major advocate of accessible websites.
I am trying to create some quality assurance documents and reports to do an assessment of a site..
I have got categories like: validation (coding/css) Accessibility (WAI), Usability, Browser compatibility, Meta tag analysis, But I'm having problems thinking how to lay these out. (or structure them)
Does anyone have any examples of these - or any futher ideas to add?
Basically I want to put in place a quality assurance system where work needs approval (to meet a certain standard) and these could be used to document the process and aid improvement
Has anyone been involved with (major) website quality assurance testing?
Regards
Gavin
Share: 
| phiger wrote: |
| I have got categories ... But I'm having problems thinking how to lay these out. (or structure them) |
This is only an informal opinion. (I'm not qualified to give more than that.)
You could put a list of your categories at the top of the page, making each a link to a section further down the page, where you say what you want to say about each category and/or where you give a list of links relating to that category. That's what is done by Trace Research and Development Center.
I originally found that page in Mark Pilgrim's Accessibilty Statement. Actually, I like what Mark says in his own statement, because he makes it explicit that what he does in each case depends on the context. (For example, see Links (1) and Visual Design (1).)
Michael
Share: