tombragg

DocAccess is an accessibility service from CivicPlus that automatically makes PDF documents and other files on your website accessible to people with disabilities. This is the official DocAccess plugin: install it, flip the switch, and the DocAccess service handles the rest.
This plugin does not process documents itself. It adds a small helper script to your pages that lets the DocAccess service (operated by CivicPlus at docaccess.com) discover document links and make them accessible to your visitors. An active DocAccess account with your domain registered is required.
How it works:
<ol>
<li>Install and activate the plugin</li>
<li>Go to Settings > DocAccess</li>
<li>Toggle the switch to enable</li>
<li>Log in to your DocAccess account at <a href="https://docaccess.com" rel="nofollow ugc">docaccess.com</a> to configure your documents</li>
</ol>
Features:
<ul>
<li>One-click setup — no code editing required</li>
<li>Automatic document link discovery on all pages</li>
<li>Accessible document viewer for your visitors</li>
<li>Lightweight — adds a single async script with zero impact on page speed</li>
<li>Fully accessible and keyboard navigable settings page</li>
</ul>
Requirements:
An active DocAccess account from CivicPlus is required. Your website domain must be registered in your DocAccess dashboard. Visit <a href="https://docaccess.com" rel="nofollow ugc">docaccess.com</a> to get started.
<h3>External services</h3>
This plugin relies on the DocAccess service, operated by CivicPlus, to provide its functionality. When you enable the plugin’s toggle, the plugin loads a helper script from docaccess.com on the front end of your site. The helper script then communicates with the DocAccess service on behalf of your visitors.
The plugin and helper script connect to the following endpoints on docaccess.com (operated by CivicPlus):
1. Helper script (docaccess.com)
<ul>
<li>What it is: The DocAccess helper script (<code>docbox.js</code>), used to discover document links and serve the accessible document viewer.</li>
<li>When it runs: On every page load on the front end of your site, but only after you toggle DocAccess on in the plugin settings. The script is not loaded when DocAccess is toggled off.</li>
<li>What is sent: A standard HTTP request to docaccess.com to fetch the script. The request includes information your browser normally sends with any third-party script request (IP address, user agent, referring page).</li>
</ul>
2. Domain configuration (docaccess.com)
<ul>
<li>What it is: A read-only configuration file describing how DocAccess should behave on your domain (e.g., whether the domain is registered, which file patterns to look for).</li>
<li>When it runs: Once per page load, when the helper script initialises.</li>
<li>What is sent: Your site’s hostname (e.g., <code>example.com</code>), so the service can return the configuration for that domain.</li>
</ul>
3. Document link intake (docaccess.com/api/v2/documents/intake/url)
<ul>
<li>What it is: The DocAccess document intake endpoint, used to register newly discovered document links so they can be processed for accessibility.</li>
<li>When it runs: When the helper script finds a document link (PDF, DOCX, etc.) on a page that has not yet been seen.</li>
<li>What is sent: The URL of the document link and the URL of the page it was found on. No visitor personal data is sent.</li>
</ul>
All three endpoints are operated by CivicPlus, Inc. at docaccess.com. Use of these services is governed by the DocAccess terms and privacy policy:
<ul>
<li>DocAccess Terms of Service: <a href="https://docaccess.com/terms-of-service" rel="nofollow ugc">https://docaccess.com/terms-of-service</a></li>
<li>DocAccess Privacy Policy: <a href="https://docaccess.com/privacy-policy" rel="nofollow ugc">https://docaccess.com/privacy-policy</a></li>
</ul>
The fonts used on the plugin’s settings page (Lato) are bundled with the plugin and served locally — no font CDN or other third-party host is contacted by this plugin.

DocAccess

The official DocAccess plugin from CivicPlus. Make your website's documents accessible to everyone with one click.

UserWay

Web accessibility can seem complex and overwhelming if you don’t know where to start.
Let us make it easier, and, to coin a phrase, more accessible for everyone. UserWay’s Accessibility Widget creates a simpler and more accessible browsing experience for your users while increasing compliance with WCAG 2.1, ATAG 2.0, European EN 301 549, ADA, & Section 508 requirements.
UserWay’s Accessibility Widget will strengthen any weak areas that could cause accessibility issues on your site. We are proud to say that a significant number of websites are more accessible today thanks to UserWay.
UserWay’s Accessibility Widget makes smart modifications to elements on your site that are identified as being non-compliant, that may prevent keyboard-only navigation, or are in violation of ADA regulations.
Install UserWay’s Accessibility Widget today. 
After installing UserWay’s Accessibility Widget, you will receive login instructions to the widget via email.
ADA & WCAG 2.1 Compliance 
UserWay’s best-in-class accessibility solutions move your site towards ADA and WCAG 2.1 compliance.
Shield Against Lawsuits 
Increasing your accessibility provides real, sustainable improvement for all users, and protects you from accessibility-related lawsuits.
Improve SEO, Boost Traffic 
Make your commitment clear: a more inclusive site for everyone expands your demographic and boosts your SEO.

Accessibility by UserWay

There is no such thing as a quick fix (one button click) for accessibility. This widget may be, at best, work like a small band aid. 

An accessible website needs amongst other things, semantic HTML5, good keyboard accessibility, meaningful (handwritten) alt texts for images and good screen reader feedback. This widget cannot provide that.

The claim: “WCAG 2.1 AA Compliance is Within Reach” is a very bold one.

Design and build a website from the start with accessibility in mind.
The WordPress Accessibility Handbook is a good starting point.

Note to the developer:
The button to activate the widget doesn’t get keyboard focus. So can’t be activated by keyboard users.

If you want to know more, I recommend reading:
Reminder: Accessibility can’t be solved automatically by Joe Dolson.

There is no such thing as a quick accessibility fix

UserWay’s Accessibility Widget creates a simpler and more accessible browsing experience for your users.

DocAccess vs Accessibility by UserWay