Halvane Accessibility Fixes
| 开发者 | minawefky |
|---|---|
| 更新时间 | 2026年9月19日 22:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Missing alt text — copies the alt text your media library already holds for that image. It only reuses words you wrote; it does not invent a description.
- Spacers and dividers — marks images whose filename says they are decorative with an explicit empty alt, so screen readers skip them instead of announcing a filename.
- Page language not declared — sets the
langattribute from your WordPress site language. - Captions as a fallback — where an image has no alt anywhere but does have a caption, uses the caption. A caption is not always a good description, so this one is worth reviewing afterwards, and the plugin says so.
- Links with no accessible name — uses the link's own title attribute as its accessible name, leaving the visible text alone.
- Untitled iframes — titles embeds from the embedded page.
- Skip link — adds a keyboard skip-to-content link where the theme has none.
- Page builders. Elementor, Divi, WPBakery, Avada, Beaver Builder and Bricks store page content inside themselves rather than in the WordPress editor, so a plugin editing posts cannot reach it. On those sites this plugin fixes site-wide settings and any page not built with the builder — and it names the pages it had to skip rather than counting them as done. Roughly half of WordPress sites use one of these, so please read this line before installing.
- Judgement calls. It will not write alt text for a photograph it has never seen, or decide whether your colour contrast is a brand decision. Those stay in the report as instructions for you.
- Guarantee compliance. No automated tool can. Automated testing catches roughly a third of WCAG criteria; the rest need a person.
安装:
- Install and activate the plugin.
- Go to Tools › Halvane. The fixes are there and ready — no account, no key, nothing to sign up for.
- To scan as well: create a free account at https://adascanner.org, copy the API key from Dashboard › API keys, paste it on that screen and save. It confirms straight away whether the key was recognised.
- Press Scan now to see what needs fixing, then apply the fixes you want, one at a time.
屏幕截图:
常见问题:
Is this an accessibility overlay?
No, and that is the point. Overlays inject JavaScript that repaints the page in the visitor's browser while the underlying content stays exactly as inaccessible as it was. Around a third of the accessibility lawsuits filed in 2025 named sites running one. Halvane changes stored content and real WordPress settings instead. Nothing is added to your pages for visitors, there is no widget in the corner, and every change has an Undo.
Will this make my site ADA compliant?
No automated tool can make that claim, and any that does is selling you something. Automated testing reaches roughly a third of the WCAG success criteria; the rest need a person to judge — whether your alt text actually describes the image, whether the page can be operated by keyboard, whether the reading order makes sense. This fixes seven common failures properly and tells you honestly about the rest.
Does it work with Elementor, Divi or another page builder?
Partly, and you should read this before installing. Elementor, Divi, WPBakery, Avada, Beaver Builder and Bricks store content inside themselves rather than in the WordPress editor, so no plugin editing posts can reach it. On those sites Halvane fixes site-wide settings and any page not built with the builder, and it names the pages it had to skip rather than counting them as done. Roughly half of all WordPress sites use one of these.
Does it write alt text for my images with AI?
No. It copies the alt text your own media library already holds for that image, and falls back to the caption where there is one. It only ever reuses words you wrote. A plugin inventing a description for a photograph it has never seen produces confident nonsense that a screen reader then reads aloud as fact.
Do I need an account?
Not for the fixes. They are ordinary PHP running on your own server, and nothing in this plugin checks a licence, counts uses, or expires. Scanning needs a free account because that part genuinely runs on adascanner.org — axe-core is a browser engine and cannot run inside PHP.
What about the European Accessibility Act?
The EAA has applied since June 2025 and is enforced against EN 301 549, which adopts WCAG Level A and AA wholesale. The same failures this plugin finds and fixes are the ones that standard is measured on. It is not a compliance guarantee — see above — but the fixes are real fixes.
Does it slow my site down?
No. Nothing runs on the front end. The scanning and fixing happen in wp-admin when you ask for them, and the only thing that reaches a visitor is a skip link, if your theme lacks one.
Frequently Asked Questions
Is this an accessibility overlay?
No, and it is built to be the opposite of one. Overlays add a script that rewrites the page in the visitor's browser; the stored content stays broken, which is why sites running them keep being sued. This plugin edits the content itself. Deactivate it and your fixed alt text is still there, because it is now genuinely part of your site.
What happens to my fixes if I uninstall?
They stay. Alt text, page language and link names are your content once written, and quietly reverting them on uninstall would leave a site less accessible than it was five minutes earlier. If you want them gone, press Undo on each fix before you remove the plugin. Uninstalling deletes the plugin's own settings and nothing else.
Does it work with Elementor or Divi?
Partly, and it tells you where it cannot help. Those builders keep page content in their own storage, out of reach of anything editing WordPress posts. Site-wide fixes still apply; builder pages are named as skipped rather than silently counted as fixed.
Is it free?
The fixes are, permanently, with no account. Scanning needs a free account because it runs on our servers rather than yours. Nothing in the plugin code is switched off, time-limited or reserved for a paid plan.
Will this make my site legally compliant?
No tool can promise that, and be sceptical of any that does. Automated testing reliably catches about a third of WCAG success criteria. This plugin fixes a subset of that third and reports the rest so a person can deal with them.
Does it slow my site down?
No. Nothing runs for visitors on a normal page load. Scanning happens when you press the button, in the admin, and the work is done by the remote service rather than your server.
Is my content sent to your servers?
No. The scanner is given your site's public URL and fetches those pages the way any visitor would. Your database, drafts, private posts and credentials never leave your server. See the "External services" section for the exact list of what is transmitted.
更新日志:
- When a scan is refused because the month's allowance is used up, the message now carries a link to the plans instead of naming prices and leaving you to find the site. Only an allowance problem gets the link — a network failure or a bad key is not solved by spending money.
- The Tools menu entry and the settings heading now read Halvane rather than ADA Scanner, so the plugin is findable under the name it was installed as.
- Renamed to Halvane Accessibility Fixes, with the text domain and slug to match.
- Renamed to Includio Accessibility Fixes, with the text domain and slug to match.
- Renamed to ADAScanner Accessibility Fixes, with the text domain and slug to match.
- The skip link's CSS is enqueued through wp_add_inline_style() instead of being printed as a style block, so a site can dequeue, cache or concatenate it.
- Corrected the fix list. Earlier versions of this readme claimed repairs to heading order and to images inside links; neither was ever implemented. The seven fixes now listed are the seven that exist. Alt text from captions was implemented but had been left out.
- Text domain changed to ada-scanner so it matches the directory slug. Translations do not load otherwise.
- The fixes no longer ask the server for permission. They are local code and now run for everybody, with no account and no time limit — the previous build gated them behind a plan check, which is not something a hosted plugin may do.
- Removed the countdown banner that advertised that gate.
- An account is now only for scanning, which genuinely runs remotely.
- A rating is only offered when an account is connected, since there is otherwise nothing to attribute it to.
- Added the API key field to the settings screen. Without it a fresh install had no way to connect an account, which made every other feature unreachable.
- Admin JavaScript moved out of the page into an enqueued file.
- Uninstall cleanup moved to uninstall.php so it runs even if the plugin cannot load.
- A rating can no longer be sent without recording which fix it was about.
- First public release.
- Seven fixes: alt text from the media library, alt text from captions, decorative images, page language, link names from title attributes, iframe titles, skip link.
- Every fix is reversible from the same screen that applied it.
- Page builder detection: Elementor, Divi, WPBakery, Avada, Beaver Builder and Bricks pages are reported as out of reach rather than counted as fixed.