by Rayhan Uddin 0 (0 reviews)

Rayetun Accessible Blocks & Accessibility Toolkit

Name: Rayetun Accessible Blocks & Accessibility Toolkit
Author: Rayhan Uddin

Accessible-by-default blocks plus an accessibility toolkit: editor checks, a site-wide scan, a front-end inspector, and reports.

Rayetun Accessible Blocks & Accessibility Toolkit ranks #63,317 among WordPress.org plugins with 0+ active installations, is #496 of 765 in the Accessibility category, and was last updated Aug 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.0.0 Current Version v1.0.0

Updated 2 months ago Last Update on 28 Aug, 2026

Refreshed 1 week ago Last Refreshed on

#496 of 765 in Accessibility

View on WordPress.org

Rank

#63,317

— No change

Active Installs

-100%

KW Avg Position

127

1.5 worse

Downloads

182

+3 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

35,749

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 8 more installs to reach 10+

Rank Changes

Current #63,317

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Aug 28, 2026
Requires WP: 6.7+
Tested Up To: 7.1.4
PHP Version: 7.4 or higher
Author: Rayhan Uddin

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

accessibility accessibility audit accessibility checker block-editor wcag

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Embed Plus for YouTube Gallery, Livestream and Lazy Loading with Facades

100K+ installs

#360

Auto Image Attributes From Filename With Bulk Updater (Add Alt Text, Image Title For Image SEO)

100K+ installs

#428

404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring

100K+ installs

#429

Accessibility by UserWay

80K+ installs

#509

Accessibility Widget by OneTap – Easy One-Click Accessibility Toolbar

AccessiYes Accessibility Widget for ADA, EAA & WCAG Readiness

20K+ installs

#1,116

View all Accessibility plugins

Frequently Asked Questions

Common questions about Rayetun Accessible Blocks & Accessibility Toolkit

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.

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.

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.

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.

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.

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.

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.

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

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.

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.