Skip to content
This repository was archived by the owner on Apr 15, 2026. It is now read-only.
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
151 changes: 151 additions & 0 deletions _tips/evaluating.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,151 @@
---
title: Tips on Evaluating Web Accessibility
nav_title: Evaluating
order: 4
title_icon: /tips/img/icons.svg#evaluating
footer: >
<p>
<strong>Status:</strong>
Updated
@@@
(first published @@@)
<br>
<strong>Editors:</strong>
<a href="https://www.w3.org/People/#kevin">Kevin White</a>,
<a href="https://www.w3.org/People/shadi">Shadi Abou-Zahra</a>, and
<a href="https://www.w3.org/People/Shawn">Shawn Lawton Henry</a>.
<a href="../acknowledgements/">Acknowledgements</a>.
Developed by the <a href="https://www.w3.org/WAI/EO/">Education and Outreach Working Group (EOWG)</a>.
Developed with support from the <a href="https://www.w3.org/WAI/DEV/">WAI-DEV project</a>, co-funded by the European Commission <abbr title="Information Society Technologies">IST</abbr> Programme.
</p>
---

{::options toc_levels="2" /}

{::nomarkdown}
{% include_cached toc.html type="start" title="Page Contents" class="full" %}
{:/}

- TOC is created automatically.
{:toc}

{::nomarkdown}
{% include_cached toc.html type="end" %}
{:/}

## Evaluate early and throughout the process

Evaluate accessibility from the earliest inception and redesign stages of a website. For example, evaluate the inclusion of accessibility considerations in the mission statement, target audience, personas, and other planning resources. Evaluate accessibility implementation throughout the remaining design and development process using a combination of cursory and comprehensive checks. The later an issue is identified, the more difficult it will be to address it, especially when issues relate to the principal design.

{::nomarkdown}
{% include_cached box.html type="start" title="More Information" class="simple" %}
{:/}

{::nomarkdown}
{% include_cached box.html type="end" %}
{:/}

## Perform cursory checks

Many accessibility checks can be carried out right away, also by non-technical people such as content writers. While such cursory checking does not substitute for more comprehensive evaluation, it helps to understand the overall situation and plan for accessibility. Cursory checks also help identify key issues and avoid obvious mistakes during the design and development process. Everyone involved in the process should perform cursory checks.

{::nomarkdown}
{% include_cached box.html type="start" title="More Information" class="simple" %}
{:/}

* [Easy Checks](/WAI/eval/preliminary): Provides simple steps to help determine if a web page addresses accessibility

{::nomarkdown}
{% include_cached box.html type="end" %}
{:/}

## Carry out comprehensive evaluation

Carry out comprehensive evaluation at key stages, such as before go-live, and periodically, to ensure that it meets the set accessibility requirements. Use a standard reporting template for evaluations, to allow for easy comparison throughout a project and across similar projects. Also capture and communicate commonly identified issues to support development teams in avoiding errors.

{::nomarkdown}
{% include_cached box.html type="start" title="More Information" class="simple" %}
{:/}

* /WAI/eval/report-tool/
* /WAI/eval/template.html

{::nomarkdown}
{% include_cached box.html type="end" %}
{:/}

## Use web accessibility evaluation tools

While most accessibility aspects cannot be automatically checked, evaluation tools can assist throughout the design, development, and maitainance process. For example, some evaluation tools specialize on specific aspects, such as color contrast checking, while others focus on large-scale evaluation of entire websites. It is important to understand the strengths and limitation of such tools, and how they fit into your workflow.

{::nomarkdown}
{% include_cached box.html type="start" title="More Information" class="simple" %}
{:/}

* /WAI/eval/selectingtools
* /WAI/ER/tools/index.html

{::nomarkdown}
{% include_cached box.html type="end" %}
{:/}

## Involve users with disabilities

Seek feedback from people with disabilities. This includes informal checking by individual users and formal usability testing with a panel of users. This helps identify subtle issues that are not easy to identify, even by experienced accessibility evaluators. Beware that processing feedback from users can be difficult and misleading without the involvement of usability professionals.

{::nomarkdown}
{% include_cached box.html type="start" title="More Information" class="simple" %}
{:/}

* /WAI/eval/users.html

{::nomarkdown}
{% include_cached box.html type="end" %}
{:/}

## Use combined expertise

Evaluating web accessibility requires diverse kinds of skills and expertise. For example, some requirements relate to the design, writing, and development aspects of a website, while others relate to assistive technologies and their use by people with disabilities. Sharing evaluation tasks in a team of reviewers can help make evaluation more effective and efficient.

{::nomarkdown}
{% include_cached box.html type="start" title="More Information" class="simple" %}
{:/}

* /WAI/eval/reviewteams

{::nomarkdown}
{% include_cached box.html type="end" %}
{:/}

## Seek external help where necessary

In some cases development teams might not have the full skillset needed to carry out evaluation during each stage of the design and development process, so that it might be more effective to seek external help for these steps. For example, accessibility consultants could carry out an initial comprehensive evaluation as input into a redesign project.

{::nomarkdown}
{% include_cached box.html type="start" title="More Information" class="simple" %}
{:/}

{::nomarkdown}
{% include_cached box.html type="end" %}
{:/}

## Learn more about accessibility

These tips are just some of the important accessibility points to address when evaluating websites. There are more things to consider. The following resources will help you learn more about accessibility — why it is important for people with disabilities, for designers, and for organizations; about web accessibility guidelines; and much more.


{::nomarkdown}
{% include_cached box.html type="start" title="More Information" class="simple" %}
{:/}

* [<abbr title="World Wide Web Consortium">W3C</abbr> Accessibility](/standards/webdesign/accessibility): Introduces accessibility and provides links to many helpful resources
* [Accessibility Principles](/WAI/intro/people-use-web/principles): An introduction to the <abbr title="Web Content Accessibility Guidelines">WCAG</abbr> requirements
* [How people with disabilities use the web](/WAI/intro/people-use-web): Real-life examples of the benefits of accessibility for people with disabilities
* [Easy checks](https://www.w3.org/WAI/eval/preliminary): Simple steps to help assess if a web page addresses accessibility
* [Website Accessibility Conformance Evaluation Methodology](https://www.w3.org/WAI/eval/conformance): A methodology designed to assist in evaluating the conformance of websites to <abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 2.0
* [Involving Users in Web Accessibility Evaluation](/WAI/eval/users.html): Provides guidance on including people with disabilities in accessibility evaluation
* [Web Accessibility Evaluation Tools List](/WAI/ER/tools/): Provides a range of tools to help automated and manual evaluations

{::nomarkdown}
{% include_cached box.html type="end" %}
{:/}
4 changes: 1 addition & 3 deletions _tips/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,4 @@ Get started with accessibility. These tips introduce some basic considerations f
* [<span>Designing</span> for Web Accessibility]({{ "/tips/designing/" | relative_url }})<span class="">: </span>Tips for user interface and visual design.
* [<span>Writing</span> for Web Accessibility]({{ "/tips/writing/" | relative_url }})<span class="">: </span>Tips for writing and presenting content.
* [<span>Developing</span> for Web Accessibility]({{ "/tips/developing/" | relative_url }})<span class="">: </span>Tips for markup and coding.
* [<span>Evaluating</span> Web Accessibility]({{ "/tips/evaluating/" | relative_url }})<span class="">: </span>Tips on checking and assessing.
* [<span>Procuring</span> Web Accessibility]({{ "/tips/procuring/" | relative_url }})<span class="">: </span>Tips on @@@@.
* [<span>Advocating</span> for Web Accessibility]({{ "/tips/advocating/" | relative_url }})<span class="">: </span>Tips for understanding and promoting accessibility.
* [<span>Evaluating</span> Web Accessibility]({{ "/tips/evaluating/" | relative_url }})<span class="">: </span>Tips on checking and assessing.