WebAIM's primary goal is to empower organizations to implement and support accessibility of their own web content. That is why we usually focus on training, reporting, and certification. There are times, however, when it makes sense to have WebAIM repair accessibility errors instead of, or in addition to, providing a report, or training staff. Here are a few examples:
- You have a body of content that needs to be made accessible in order to conform to a grant or contact. This content will not be updated.
- Your site was developed by a web design firm. You seldom make changes to the site.
- You are creating an accessibility policy and want to train your developers so that future content will be made accessible, but you would rather have WebAIM repair all errors as we come across them instead of having us document and report on these errors.
- Your site is, for the most part, accessible. You would like WebAIM to repair errors as part of a final review.
- You have an accessibility issue that is very complex and you would rather have it resolved quickly by an expert.
In many instances, you may find that a combination of reporting and repair works well. For example, you may want WebAIM to report on and repair the template and first level pages and provide documentation on the accessibility issues on your site. This can serve as an example for all other pages. This then gives your organization a jump-start into accessibility and empowers you with the knowledge you need to fully implement accessibility across your site.