Log in   Register a New Account

Accessify Forum - Discuss Website Accessibility

New to the forum?

Only an email address is required.

Register Here

Already registered? Log In

Currently Online

No registered users are online.

Formal report

  • Reply to topic
  • Post new topic
Reply with quote I'm being doing some freelance consultancy on a website's accessibility and the customer has asked me for a formal report.
What would you expect it to include? Has anyone ever done anything like this before and would be willing to show me a sample?
Reply with quote Do an Audit Report saying what your goals were and whether the website passed X Accessibility criteria and your suggested solutions.

Basically think of the WCAG Checklist group the topics and contrast and compare which user groups would have issues with the site at the moment and highlight possible solutions, etc.

For example JavaScript alone was powering the Navigation, this could be problematic because 13% of users have JavaScript disabled, etc. thus making the site inaccessible to...

};-) http://www.xhtmlcoder.com/

WVYFC chose the Yorkshire Air Ambulance as the main charity to fund raise for in 2006
Reply with quote What I should've said is I've advised the customer of errors/problems as they've been developing the site and they've all been fixed.
Reply with quote Give them a conclusion of what you told them to fix and why, how it was achieved, etc. Then tell them if they have passed or failed your testing criteria and any possible improvements, or ongoing web maintenance tasks they should to perform to stay accessible.

};-) http://www.xhtmlcoder.com/

WVYFC chose the Yorkshire Air Ambulance as the main charity to fund raise for in 2006
Reply with quote
Daz wrote:
What I should've said is I've advised the customer of errors/problems as they've been developing the site and they've all been fixed.


So, are they wanting the formal report so that they have "proof" that it passes some arbitrary criteria?

When preparing formal reports based on our audits, we generally include a preamble, an overview of all the issues that we uncovered along with suggestions for fixing the problems, and references that point to relevant W3C documents, best practices etc...

Our preamble always includes text that indicates that many of the tests that we perform are subjective, and that we offer no "stamp of approval", only opinion.

In some cases we are asked to verify that third party work has been changed based on our recommendations and report. In those cases, we include a summary of the issue referring back to the original report, as well as indication of whether or not we believe each issue has been addressed.

feather.
Reply with quote Robert and feather, thank you both for very much for your input. I have a good idea of where to start now Smile

Display posts from previous:   

All times are GMT

  • Reply to topic
  • Post new topic