Savoy Accessible – Drop-In PDF Accessibility for WordPress (WCAG 2.1 AA)

説明

Savoy Accessible scans the PDFs on your WordPress site and uses the Savoy cloud service to generate WCAG 2.1 AA-friendly HTML versions of each one, so screen readers and other assistive technologies can read the content directly. It also includes a set of on-demand audits and opt-in hardening toggles for common WCAG issues elsewhere on your site.

The plugin is intended for sites that publish a lot of PDF content (schools, universities, government agencies, nonprofits, and businesses).

Key features

  • Automatic PDF detection across posts, pages, and the media library
  • Conversion of PDF text content to semantic HTML using the Savoy service
  • OCR for scanned (image-only) PDFs via vision AI on the Savoy service
  • Automatic alt-text generation for images inside PDFs
  • Generated documents are stored as a custom post type so you can edit them in Gutenberg
  • Optional AI chat sidebar in the document viewer (off by default)
  • Inline accessibility badge next to PDF links
  • Optional automatic link rewriting so visitors land on the HTML version
  • Daily automatic scanning to catch newly uploaded PDFs
  • Works with any theme

On-demand audits

  • Image alt text audit
  • Generic link text audit (WCAG 2.4.4) — flags “click here”, “read more”, bare URLs
  • Heading hierarchy audit (WCAG 1.3.1, 2.4.6) — flags multiple H1s and skipped levels
  • Tables-without-headers audit (WCAG 1.3.1)
  • Empty or missing button labels audit (WCAG 4.1.2)

Opt-in hardening toggles

  • Inject <html lang> if missing
  • Visible focus outlines for keyboard navigation
  • Respect prefers-reduced-motion
  • “Skip to main content” link

Software as a Service

This plugin is a client for the Savoy service at savoy.chat. PDF processing, OCR, HTML generation, and AI chat all run on Savoy’s servers. The plugin only communicates with Savoy when you provide an API key. See the Savoy Terms of Service and Privacy Policy at savoy.chat/terms and savoy.chat/privacy.

The free portion of the plugin (PDF detection and the audit/hardening tools) does not require an API key and does not contact Savoy’s servers. PDF conversion and link rewriting require a Savoy subscription.

How it works

  1. Install and activate the plugin.
  2. Go to Settings > Savoy Accessible. Click “Rescan all content” to see how many PDFs are on your site.
  3. (Optional) Sign up at savoy.chat/accessible, paste in your API key, and click Save and Verify.
  4. Detected PDFs are sent to the Savoy service for conversion.
  5. Each converted document is stored as an Accessible Document post in WordPress, which you can edit.
  6. Links on your site are optionally rewritten to point at the accessible HTML version.

What happens to my original PDFs?

The plugin never modifies your original files. It creates parallel HTML pages and optionally points visitors to them. You can disable link rewriting at any time.

インストール

  1. Install the plugin from the WordPress Plugin Directory, or upload the zip via Plugins > Add New > Upload.
  2. Activate the plugin.
  3. Go to Settings > Savoy Accessible.
  4. Click “Rescan all content” to see how many PDFs on your site need accessibility work. This step is free and works without an API key.
  5. (Optional) Sign up at savoy.chat/accessible, get an API key, paste it in, and click “Save and Verify”.
  6. Once an API key is connected, the plugin sends detected PDFs to Savoy for conversion.

FAQ

Is this free?

Scanning, PDF detection, the WCAG audits, and the hardening toggles work without any account and without contacting an external service. Conversion and link rewriting require a Savoy subscription.

Does this guarantee compliance with any specific regulation?

No. The plugin generates WCAG 2.1 AA-friendly HTML, which is the conformance level cited by Section 508 and by the updated ADA Title II rule. Whether your site as a whole conforms depends on your theme, your other content, and your authoring practices. We strongly recommend a professional accessibility audit for any formal compliance certification.

Is this an overlay?

No. The plugin generates real HTML pages with semantic structure, alt text, and reading order, stored as WordPress posts. It does not inject an overlay widget.

What about scanned PDFs (image-only PDFs)?

The Savoy service uses vision-AI OCR for scanned PDFs.

Can I edit the generated HTML?

Yes. Each converted document is a custom post type. You can edit it in Gutenberg like any other page; revisions are preserved.

How does pricing work?

See savoy.chat/accessible for current pricing and plan tiers.

Does this slow down my site?

The plugin adds a lightweight content filter on the frontend. PDF conversion and OCR run on Savoy’s servers, not yours.

What if I cancel my subscription?

Already-converted documents remain in your WordPress install. New conversions stop.

Can I use this for Section 508?

The HTML output is designed to meet WCAG 2.1 AA, which Section 508 references as its conformance standard. As with any accessibility work, a professional audit is recommended for formal compliance certification.

評価

このプラグインにはレビューがありません。

貢献者と開発者

Savoy Accessible – Drop-In PDF Accessibility for WordPress (WCAG 2.1 AA) はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献しています。

貢献者

変更履歴

1.0.32

  • Moved the three opt-in hardening styles (focus outline, reduced-motion, skip link) out of inline <style> tags and into the wp_enqueue_scripts pipeline via wp_register_style() and wp_add_inline_style(). No visual or behavioral changes.

1.0.31

  • Removed the small “Powered by Savoy” link from the document viewer’s chat sidebar footer.
  • Hardened the PDF link rewriter: only plugin-controlled attributes are emitted on rewritten links; link text passed through wp_kses_post().
  • Moved the document viewer’s inline <style> and <script> blocks into properly enqueued asset files. PHP values supplied via wp_localize_script().

1.0.30

  • Code quality: cleared WordPress.org plugin-check warnings. No behavior changes.

1.0.29

  • Documentation: rewrote readme to remove promotional superlatives and definitive compliance claims. No behavior changes.

For the full changelog see changelog.txt.