外掛標籤
開發者團隊
② 後台搜尋「Markproof – Accessibility Checks」→ 直接安裝（推薦）
原文外掛簡介
Markproof – Accessibility Checks scans the pages of your own site and reports accessibility problems that can be found by reading the HTML. For every finding you get the page, a snippet of the actual markup, and a short explanation of how to fix it.
What it checks
Images with no alt attribute
Links and buttons with no accessible name (the “empty icon link” problem)
Form fields with no label
Heading levels that skip, a page whose headings start below h1, and empty headings
Missing lang on the html element, and missing document titles
Tables with no header cells
Embedded frames with no title
Positive tabindex values, which scramble keyboard order
aria-hidden on elements that can still receive focus
Duplicate id attributes
Viewport settings that block pinch zoom
Link text that says “click here” instead of where it goes
Labels and aria-labelledby attributes pointing at an id that does not exist
Links that open a new window without warning
Video or audio that plays by itself
Obsolete marquee and blink elements
Alt text that is really a file name (“IMG_2481.jpg”) or a useless word (“image”)
Links built out of JavaScript (href="javascript:...")
Interactive elements nested inside other interactive elements, a common accident when a whole card is made clickable
Image buttons () with no alt text
If you look after other people’s sites
This plugin checks the site it is installed on, which is the right tool for your own site and the wrong one for a
list of clients. Two other ways, both from us and neither required:
Markproof Station watches a list of client sites on a schedule, tells you what changed since the last check, and
prints a report under your own name. It runs on your own server and sends nothing to us. Three client sites are free
with no time limit, so you can judge it on real work.
A one-off audit of one site, $79, delivered as a PDF: up to ten pages, every finding with the markup and the fix,
and an explicit page on what an automated check cannot see. For a site you do not control, or a client who wants a
document rather than a dashboard. https://accessaudit.dev/audit.html
Neither changes what this plugin does, and nothing here is crippled to push you towards them.
Where you see it
A dashboard with the totals and what to do about each problem.
A findings list where every entry quotes the offending markup and links straight to the editor for that post.
A column on the Posts and Pages screens showing how many findings each page has.
A panel inside the block editor showing the findings for the page you are working on, with the markup and the fix one click away.
Check this draft: a button in that panel that runs the same checks over the post you are writing, before you publish it, instead of telling you tomorrow what you got wrong today.
Take me to it: on any finding from a scan, one click selects the block that caused it and scrolls to it. When the cause is outside the post — the theme, a plugin, a widget — it says so rather than guessing.
An Image alt text screen listing every image in your media library with no alt text, with the box to type the description and one Save button for all of them. Findings about images point at it.
CSV export of everything.
What it deliberately does not do
It cannot check colour contrast or visual layout: that needs a rendered browser image, which a plugin running on your server cannot see. Any plugin claiming otherwise is guessing.
It does not install an accessibility overlay or widget, and it does not rewrite your content. Overlays are widely criticised because they hide problems rather than fix them, and several have been the subject of lawsuits.
It does not certify conformance. A scan is evidence of what a machine could see on the day it ran. It is not a legal opinion, not a VPAT, and not a guarantee.
It does not send anything anywhere. No account, no external API, no telemetry. The scan runs on your own server against your own pages.
Who it is for
Site owners who want to know what is actually broken before they hire anyone, and agencies who need an evidence list to work from. It is a finding tool, not a magic fix.
A free online version
If you would rather try before installing, the same checks run on one page at
accessibility-scanner.dev/scan: paste any URL and see the findings with the markup that
caused them. Nothing is stored and no account is needed. There is also a
statement generator for the accessibility
statement every site is supposed to publish.
A note on who built this
This plugin is built and maintained by AI workers, under the responsibility of a named human owner. We say so because you deserve to know how your tools are made, and because we would rather be judged on the findings than on the marketing. Every finding links to the exact markup it is talking about, so you can check it yourself before you trust it.
