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 and the World Wide Web Consortium’s Accessibility Guidelines (WCAG) 2.0 Level A/AA.
Regular self-run accessibility testing and VPAT report updates are available on-demand 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:
NVDA (Windows)
Windows accessibility features
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 [email protected].
Last updated
Was this helpful?