Savoy Accessibility – Drop-In PDF Accessibility for WordPress (WCAG 2.1 AA)
| 开发者 | peteclark3 |
|---|---|
| 更新时间 | 2026年5月20日 20:01 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Savoy Accessibility 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
- Automatic scanned PDF detection — text is extracted directly when a text layer is present; vision AI OCR is used when the entire document is image-only (e.g. a scanned page). Embedded images in any PDF are described separately via vision AI for alt text.
- 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
- 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)
- Inject
<html lang>if missing - Visible focus outlines for keyboard navigation
- Respect
prefers-reduced-motion - "Skip to main content" link
- Install and activate the plugin.
- Go to Settings > Savoy Accessibility. Click "Rescan all content" to see how many PDFs are on your site.
- (Optional) Sign up at savoy.chat/accessible, paste in your API key, and click Save and Verify.
- Detected PDFs are sent to the Savoy service for conversion.
- Each converted document is stored as an Accessible Document post in WordPress, which you can edit.
- Links on your site are optionally rewritten to point at the accessible HTML version.
安装:
- Install the plugin from the WordPress Plugin Directory, or upload the zip via Plugins > Add New > Upload.
- Activate the plugin.
- Go to Settings > Savoy Accessibility.
- 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.
- (Optional) Sign up at savoy.chat/accessible, get an API key, paste it in, and click "Save and Verify".
- Once an API key is connected, the plugin sends detected PDFs to Savoy for conversion.
屏幕截图:
常见问题:
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.
更新日志:
1.0.39
- Fix: database schema migrations now run automatically on plugin upgrade, not just on fresh activation. Fixes cases where columns added in recent releases (validation_score, etc.) were missing after an auto-update, which prevented processing progress from being stored and displayed.
- New: WCAG validation score shown alongside each converted document (Pass / Warnings / Needs review), powered by axe-core.
- Security: viewer URLs no longer contain the API key. The site ID (a read-only identifier) is used instead, so API keys are never exposed in browser history or server logs.
- PDF links in navigation menus are now rewritten to point at the accessible HTML version, the same as links in post content.
- When HTML is regenerated server-side, Refresh Statuses now detects the change and automatically re-syncs the accessible HTML to the WordPress post.
- Error messages from document processing (e.g. broken PDF links, access errors) now persist in the database and display below the status badge in the documents list. Previously errors were only visible while the processing job was active.
- Renamed plugin display name to Savoy Accessibility. No behavior changes.
- Moved the three opt-in hardening styles (focus outline, reduced-motion, skip link) out of inline
<style>tags and into thewp_enqueue_scriptspipeline viawp_register_style()andwp_add_inline_style(). No visual or behavioral changes.
- 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 viawp_localize_script().
- Code quality: cleared WordPress.org plugin-check warnings. No behavior changes.
- Documentation: rewrote readme to remove promotional superlatives and definitive compliance claims. No behavior changes. For the full changelog see changelog.txt.