# OUR ACCESSIBILITY GUIDELINES

> "We believe that enabling and empowering our people, and the partners we work with, is vital - and that means every individual should find it easy to connect and contribute."
>
> *Keri Gilder, Chief Executive Officer*

## DELIVERING COLT'S ACCESSIBILITY ROADMAP

To deliver the ambition outlined in the [Colt Accessibility Roadmap](https://docs.colt.net/accessibility/our-accessibility-roadmap), we need the right tools, skills and ways of working in place to empower our teams. This knowledge base will empower our project, technical and content producing teams, to be more inclusive in everything they do, delivering digital products and services for both employees and customers.

The Colt Accessibility Guides have been designed to make delivery of the [Web Content Accessibility Guidelines](https://www.w3.org/WAI/fundamentals/accessibility-principles/) (WCAG) more achievable. This site also provides our project managers and product managers with guidance on how to embed accessibility end to end.

These guidelines are aligned with the values outlined in Colt's [Diversity, Equity and Inclusion](https://www.colt.net/about/our-people/dei) strategy, and are to be used in conjunction with Colt's [Brand Guidelines](https://docs.colt.net/brand/brand-foundation).

The Colt Accessibility Guides have been divided into four distinct sections so Product Owners, Project Manager, Developers, Test Managers and Content Producers can easily access guidance that is relevant to them. In addition to that an [Accessibility RACI](https://www.colt.net/wp-content/uploads/2024/09/COLT-Accessibility-RACI-with-links.xlsx) has been designed to help embed accessibility into Colt's processes. This RACI should be reviewed by the whole team to ensure everyone knows when specific activities should happen and where ownership sits in terms of delivery and reporting.

## CONTENTS

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><ol><li>FOR CONTENT PRODUCERS</li></ol></td><td><a href="/pages/Q125NCJlB8NqfW3boKzs">/pages/Q125NCJlB8NqfW3boKzs</a></td></tr><tr><td><ol start="2"><li>FOR DEVELOPERS + QA TESTERS</li></ol></td><td><a href="/pages/44e72aeb7ebf4db7cd517cd100fcd0bea4364b51">/pages/44e72aeb7ebf4db7cd517cd100fcd0bea4364b51</a></td></tr><tr><td><ol start="3"><li> FOR PROJECT MANAGERS</li></ol></td><td><a href="/pages/04bb63b32e74e2b640cdd9c373f5b66fcc847545">/pages/04bb63b32e74e2b640cdd9c373f5b66fcc847545</a></td></tr><tr><td><ol start="4"><li>FOR PRODUCT OWNERS</li></ol></td><td><a href="/pages/c5233f18e5507e5b952ab3a4527d0a4a68228a60">/pages/c5233f18e5507e5b952ab3a4527d0a4a68228a60</a></td></tr></tbody></table>


---

# 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://docs.colt.net/accessibility/our-accessibility-guidelines.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.