# 2.0 How to build better content? Test your work.

In the following pages, we will go into detail on how you can improve your web content for accessibility.

Each page will focus on a specific aspect of web content, such headings, images, and hyperlinks. The page will start with a description of how the screen reader, or other assistive technology, interprets and allows the user to interact with that element of the page. It will be followed by examples and tips for how you can make powerful contributions to making your content universally accessible.

## Install a testing tool

Before we jump into the details of making your content better, let's install a simple accessibility testing tool for your content that can double check your work as it is created.  **Testing Tip**: Test a preview version of your page and not the editing version of your page.

### **WAVE Accessibility Evaluation Tool**

The WAVE accessibility toolkit was created specifically with web content creators in mind. It can help you test each of the issues in our guide. Install a browser extension or enter your site URL in the website version. 

* [Website version](http://wave.webaim.org/) and information
* Extensions: [Chrome,](https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh) [Firefox,](https://addons.mozilla.org/en-US/firefox/addon/wave-accessibility-tool/) and [Edge](https://microsoftedge.microsoft.com/addons/detail/wave-evaluation-tool/khapceneeednkiopkkbgkibbdoajpkoj) versions.

### **Additional testing tools** 

* [Axe Dev Tools](https://www.deque.com/axe/browser-extensions/): advanced tools for accessibility testing. 
* [Color Contrast Checker](https://webaim.org/resources/contrastchecker/): Test web colors for contrast
* [Color-reliant Link Contrast Checker](https://webaim.org/resources/linkcontrastchecker/): See if your link colors pass contrast tests.
* [A11y color blindness empathy tool](https://chromewebstore.google.com/detail/a11y-color-blindness-empa/idphhflanmeibmjgaciaadkmjebljhcc) (Chrome extension)


---

# 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://www.liba11y.org/howto/how-to-build-better.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.