Linux 软件免费装
Banner图

Rayetun Accessible Blocks & Accessibility Toolkit

开发者 rayetun
更新时间 2026年8月28日 05:21
捐献地址: 去捐款
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPL-2.0-or-later
版权网址: 版权信息

标签

accessibility wcag block editor accessibility checker accessibility audit

下载

1.0.0

详情介绍:

Rayetun Accessible Blocks combines two things in one plugin: accessible blocks, and a toolkit for checking and improving the accessibility of your whole site. Accessible blocks. Interactive components — modals, sliders, tables, mega menus, carousels, before/after, and more — built to be keyboard-operable and screen-reader-correct against WCAG 2.2 Level AA, each with a published Accessibility Conformance Report you can hand to a compliance team. An accessibility toolkit. An accessibility panel in the editor as you write, a site-wide axe-core scan with a dashboard and trend history, a front-end inspector that outlines problems on the live page, an image alt-text audit and bulk editor, readability and contrast help, scheduled email summaries, and an exportable accessibility report. Every feature described here is included in the plugin — there are no locked panels or upgrade prompts. A separate add-on aimed at agencies (managing many client sites from one place, branded client reports, and the like) may follow later; it would only add to what is already here. How Rayetun Accessible Blocks is organised 🧱 The Blocks Both carousels respect prefers-reduced-motion, and every dot and arrow meets the WCAG 2.2 24×24px target-size minimum. 🎛️ Works on Every Block These apply to any block — ours or WordPress's own. 👁️ Conditional Display Show or hide any block by login state or user role. Hidden blocks are removed on the server, so screen readers, search engines, and feeds all see the same page a visitor does — not content hidden with CSS that assistive tech still reads out. A note on Conditional Display: it controls presentation, not access. Hidden text still exists in the post, so it can surface in site search or an export. It's stronger than CSS-hiding and weaker than a membership plugin — please don't use it to protect genuinely private content. ✨ Motion Entrance animations, parallax, and sticky positioning on any block. Every effect is skipped entirely for visitors who ask their system for reduced motion, and the code loads only on pages that actually use it. 🔍 In-Editor Accessibility Checker Every block this plugin adds gets an "Accessibility" panel that checks its setup as you build, and shows a clear all-clear when it's right. 📊 Site-Wide Accessibility Scan An Accessibility screen in wp-admin scans your published pages with axe-core against WCAG 2.2 AA and keeps the results. 🖍️ Front-End Inspector The same checks, on the live rendered page — for logged-in editors only. This is the opposite of an accessibility overlay. It changes nothing a visitor sees; it shows problems to the person who can fix them. 📧 Scheduled Email Reports Have a summary of your accessibility findings emailed to you weekly or monthly. Off by default; you choose the address. The email reports your last stored scan — it does not run a new one, because a real scan needs a real browser to render your pages. The email says so itself, and the settings screen tells you when the last scan actually ran. 📋 Accessibility Conformance Reports Each block ships a published ACR documenting how it meets each relevant WCAG 2.2 AA success criterion, the testing environment, and any known limitations — including defects found and fixed during screen-reader testing. Each block has been tested with a real screen reader (NVDA + Firefox), and its report records the testing environment along with any defects found and fixed during that testing. 🧭 What Rayetun Accessible Blocks Will Not Do Worth stating plainly, so you know what to expect: Automated checks are a floor, not a certificate. They catch a portion of WCAG failures; the rest needs a keyboard and a screen reader. A clean scan does not mean a page is accessible, and Rayetun Accessible Blocks says that on the dashboard itself. Compatible With

安装:

  1. Upload the plugin folder to /wp-content/plugins/rayetun-accessible-blocks/, or install via Plugins → Add New.
  2. Activate Rayetun Accessible Blocks through the Plugins screen.
  3. Add any of the plugin's blocks from the inserter — look for the Rayetun Accessible Blocks category.
  4. Open the Accessibility panel in the block sidebar to see live checks as you build.
  5. Visit Accessibility in the admin menu and run a site-wide scan.
  6. Optional: turn on Email reports to get a weekly or monthly summary.
No configuration is required to get started.

屏幕截图:

  • In-editor accessibility panel — live checks on a block as you build, with an all-clear state.
  • Front-end inspector — accessibility issues outlined in place on the live page, with an explanation popover.
  • Per-page findings — every finding with its rule, severity, and offending markup.
  • Email reports — schedule a weekly or monthly summary of your stored scan.
  • Post Grid — grid view
  • Countdown — An accessible countdown timer to a date and time (Cards, Solid, Minimal view)
  • Image Before / After — An accessible before-and-after image comparison.

升级注意事项:

1.0.0 First public release of Rayetun Accessible Blocks.

常见问题:

♿ Does this plugin make my site ADA / EAA compliant?

No plugin can, and you should be sceptical of any that claims it does. Most of WCAG conformance comes from your content and design decisions — alt text, contrast choices, heading structure, plain language. Rayetun Accessible Blocks handles the part a plugin can own: correct markup, keyboard operability, focus management, and accessible defaults for the interactive components on your pages.

📏 Which WCAG version do you target?

WCAG 2.2 Level AA — the version cited by EN 301 549 (European Accessibility Act) as it converges on 2.2, and a superset of the WCAG 2.1 AA cited by ADA Title II rules.

🚫 Is this an accessibility overlay or widget?

No. An overlay adds a floating toolbar that changes what visitors see while leaving the underlying markup unchanged. Rayetun Accessible Blocks works on the markup itself, and its front-end inspector is visible only to logged-in editors — never to visitors.

🎨 Does it work with my theme?

Yes. Blocks inherit your theme's colours, spacing, and typography via theme.json/global styles before adding their own controls. Block themes and classic themes are both supported.

🖥️ Why do scans run in my browser instead of on the server?

Because a meaningful accessibility check needs a real rendered page — computed colours, actual layout, focus order. That only exists in a browser. It's why the scheduled email reports your last stored scan rather than running a new one, and why the email says so.

🔒 Does Rayetun Accessible Blocks send my data anywhere?

No. Scan results, findings, dismissals, and settings are stored in your own WordPress database. There is no telemetry and no account. The only outbound requests come from the Video Popup block when a visitor chooses to play an embedded YouTube or Vimeo video — see the External Services section.

⚡ Is it fast? What is it built on?

Built the modern WordPress way, on official core APIs: the Interactivity API for front-end behaviour, the Block API v3 (block.json), and server-side rendering. So there's no jQuery and no extra framework runtime on your visitors' pages, and each block's script loads only where it's actually used (the Motion and inspector assets, too). And because every block is rendered on the server and only enhanced by a little JavaScript, the content works even before that script loads — or if it never does. That's good for speed, and it's the same reason the blocks hold up for screen readers and search engines.

🛒 Do the Product blocks need WooCommerce?

No. Product Card and Products are author-populated, so they work on any site with no e-commerce plugin installed.

🧩 Does it conflict with other accessibility checkers?

No. The in-editor panel checks interactive block configuration — the pitfalls only a block author can fix. Full-content checkers like Block Accessibility Checks cover different ground, and the two complement each other.

♻️ What happens if I uninstall Rayetun Accessible Blocks?

Everything is removed cleanly: the scan table, its schema option, per-post scan meta, and all plugin settings. Your posts, pages, and media are never touched. If you generated an accessibility statement page, that page is your own content and is left in place.

💬 Get Support

Post in the WordPress.org support forum.

更新日志:

1.0.0