# Accessibility statement

This accessibility statement applies to the present [OA.Report](https://oa.report) website and excludes other product websites ([OAbutton.org](https://oabutton.org/), [InstantILL.org](https://instantill.org/), [ShareYourPaper.org](https://shareyourpaper.org/)), our [main website](https://oa.works), and our [blog](https://blog.oa.works/).

This website is run by OA.Works. Our organization is committed to accessibility and inclusivity for all people with disabilities, in accordance with the [Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018](http://legislation.gov.uk/uksi/2018/952/contents) (in the United Kingdom) and the requirements of [Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d)](https://www.section508.gov/manage/laws-and-policies/section-508-law/) (in the United States).

We want as many people as possible to be able to use this website. For example, that means you should be able to:

* Zoom in up to 400% without the text spilling off the screen.
* Navigate most of the website using just a keyboard.
* Navigate most of the website using speech recognition software.
* Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).

We’ve also made the website text easy to understand using Simple English (US).

We continue to improve the website’s accessibility and performance for as many devices as possible. We do not, however, support Internet Explorer.

[AbilityNet](https://mcmw.abilitynet.org.uk/) has advice on making your device easier to use if you have a disability.

### Measures to support accessibility

OA.Works takes the following measures to ensure accessibility of the OA.Report website:

* Included accessibility throughout our internal policies.
* Appointed an accessibility officer.
* Assigned accessibility goals and responsibilities.

### Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

OA.Works’ website is fully compliant with the **Web Content Accessibility Guidelines (WCAG) version 2.2 AA** standard.

#### Known accessibility problems

None found following an accessibility audit conducted on 13 March 2026.&#x20;

### Feedback and contact information

We welcome your feedback on the accessibility of the OA.Report website. Please let us know if you encounter accessibility barriers or if you need information on this website in a different format:

* Email: <accessibility@oa.works>
* Phone: [+1 (631) 498-8938](tel:+16314988938)

We try to respond to feedback within seven days.

### Preparation of this accessibility statement

This statement was prepared on 22 June 2023. It was last reviewed on **27 April 2026**. This website was last tested on 13 March 2026.

[Torchbox](https://torchbox.com/) carried out an accessibility audit on 13 March 2026 using the following methods:

* Automated tools:&#x20;
  * Accessibility Insights for Web (Axe, Chrome).
* Manual testing:&#x20;
  * Keyboard navigation testing (Chrome)
  * Screen reader testing (VoiceOver on macOS, Safari)
  * Full-page zoom testing (Chrome, up to 400%)
  * General manual accessibility testing (Chrome)

Our own team at OA.Works provided fixes to the issues found in the audit and re-tested them using:

* Automated tools: [Lighthouse](https://developers.google.com/web/tools/lighthouse/) and [axe](https://www.deque.com/axe/) (via [Ghost Inspector](https://ghostinspector.com)).
* Manual testing: MacOs’ VoiceOver and navigating using just the keyboard.


---

# 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://about.oa.report/help/accessibility-statement.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.
