# Accessibility

### Overview

We're committed to ensuring digital accessibility of WProofreader for people with disabilities. We are continually improving the user experience for everyone, and applying the relevant accessibility standards.

The current version of the WProofreader core (shipped as part of WebSpellChecker Server v5.28.3 package) is compatible with the [Section 508 Guidelines](https://www.access-board.gov/ict/) and the [World Wide Web Consortium’s Accessibility Guidelines (WCAG) 2.0 Level A/AA](http://www.w3.org/TR/2008/REC-WCAG20-20081211).

Regular self-run accessibility testing and VPAT report updates are available [on-demand](https://webspellchecker.com/contact-us/) to make sure WProofreader is still convenient for all users. The majority of success criteria on Level A and AA of WCAG 2.1 are covered, incl. keyboard navigation.

Our accessibility testing targets the **desktop web experience**, including:

* keyboard interaction
* desktop screen-reader compatibility
* automated accessibility validation
* semantic and structural checks
* visual and focus-state accessibility
* behavior inside standard HTML inputs and supported editors

Mobile devices, touch-based interaction, and mobile assistive technologies are **not part of the product design** and are therefore **out of scope**.

The WProofreader core was tested on macOS Ventura/Chrome using the below tools and methods:

* [Google Screen Reader](https://chrome.google.com/webstore/detail/screen-reader/kgejglhpjiefppelpmljglcjbhoiplfn)
* [Mac VoiceOver](https://support.apple.com/uk-ua/guide/voiceover/vo2682/mac)
* [WAVE Evaluation Tool](https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh)
* [axe DevTools](https://chrome.google.com/webstore/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)
* [Stark](https://www.getstark.co/figma)
* [Figma built-in A11y](https://www.figma.com/community/plugin/733159460536249875/A11y---Color-Contrast-Checker)
* NVDA (Windows)
* Windows accessibility features
* [Lighthouse Accessibility](https://chromewebstore.google.com/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk)
* WebSpellChecker documentation
* Code inspection
* Keyboard-only interaction

### Accessibility testing coverage

#### Structural & semantic

* correct semantic roles and ARIA usage
* heading hierarchy
* name/role/state exposure
* valid and logical DOM structure

#### Keyboard navigation

* complete traversal using keyboard only
* visible focus states
* no keyboard traps

#### Forms & controls

* labels associated with inputs
* accessible error states and descriptions
* accessible buttons, toggles, dropdowns

#### Screen readers (web and desktop)

* correct announcements in screen readers
* proper reading order
* correct labeling of toolbar elements
* accessible interaction with editor-embedded components

#### Automated checks

* contrast validation
* ARIA correctness
* missing labels or alt attributes
* structural errors
* non-navigable interactive elements

**Current known issues:**

* Enhanced contrast does not meet WCAG AAA 1.4.6
* Visual presentation AAA not satisfied (user cannot control spacing/line length)
* Help and reading-level AAA not met
* Semantic purpose identification (1.3.6) not implemented

When accessibility issues are identified—internally or through client reports—we treat them as defects and address them as part of ongoing product maintenance.

For more information, send us a request to <accessibility@webspellchecker.net>.

### Related

* [How would keyboard users be able to access the spell check suggestions?](/faq/technical/wproofreader/how-would-keyboard-users-be-able-to-access-the-spell-check-suggestions.md)


---

# 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.wproofreader.com/features/accessibility.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.