# Overview

## What is Accessibility Testing?

Accessibility testing ensures your website, app or product can be used by people with disabilities. An estimated 1 billion people worldwide have some form of disability that impacts how they access digital content. 

{% hint style="danger" %}
Therefore, accessibility is both an **ethical issue** and a **business imperative**.
{% endhint %}

<div data-full-width="true"><figure><img src="https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2Ftse1.mm.bing.net%2Fth%3Fid%3DOIP.6p4AcZYaXSSV6_SjKdwRJQHaDP%26pid%3DApi&#x26;f=1&#x26;ipt=a16f2c051e869dd84538d979973061f09535a6da8f3d95e9a23414c6d1180b99&#x26;ipo=images" alt="" width="563"><figcaption></figcaption></figure></div>

## Advantages:

• Inclusiveness - Makes your product accessible to people with disabilities, reaching a wider audience.

• Compliance - Helps ensure you meet accessibility standards like WCAG and legal requirements like ADA.

• Usability - Improvements for accessibility often benefit all users, making your product more usable in general.

• Brand reputation - Shows you care about inclusion, helping your brand reputation.

• Lower support costs - Proactively designing for disabilities can reduce support calls and issues.

## Disadvantages:

• Time and resource intensive - Thorough accessibility testing requires time, tools and resources.

• Requires expertise - You need people with accessibility expertise to properly perform and review the testing.

• Additional costs - Any fixes or changes required from testing can add to development costs.

• Complex technologies - Assistive technologies like screen readers add another layer of complexity to testing.

• Ongoing effort - Accessibility needs to be maintained over the life of your product, requiring continuous vigilance.

Overall, the advantages of inclusive design, compliance and usability generally outweigh the disadvantages of accessibility testing. But it does require a proactive, ongoing commitment and investment of resources to implement effectively.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://qatesting.gitbook.io/qa/accessibility-testing/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.