by quicksloth 0 (0 reviews)

Quicksloth Accessibility Toolbar

Name: Quicksloth Accessibility Toolbar
Author: quicksloth

Accessibility toolbar with 25 tools for contrast, text size, fonts and reading. No account. No external requests. No branding.

Quicksloth Accessibility Toolbar ranks #61,619 among WordPress.org plugins with 0+ active installations, is #496 of 765 in the Accessibility category, and was last updated Oct 26, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v0.1.2 Current Version v0.1.2

Updated 6 days ago Last Update on 26 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#496 of 765 in Accessibility Downloads -67.8% this week Actively maintained

View on WordPress.org

Rank

#61,619

— No change

Active Installs

— No change

KW Avg Position

100.7

0.7 worse

Downloads

179

+1 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

34,051

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 #61,619

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: 0.1.2
Last Updated: Oct 26, 2026
Requires WP: 6.0+
Tested Up To: 7.1.4
PHP Version: 7.4 or higher
Author: quicksloth

Support & Rating

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

Keywords

a11y accessibility accessibility toolbar accessibility widget dyslexia

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 Quicksloth Accessibility Toolbar

No. An accessibility toolbar helps some visitors; it does not make a website conform to WCAG or to the law. Fix your content and code first. The work that matters is in your content and theme: text alternatives for images, a logical heading order, enough color contrast, labels on form fields, and everything usable with a keyboard. Test with real assistive technology where you can. The toolbar is an extra that lets some visitors adjust the page to their needs.

No script or style of the plugin blocks the first paint. It loads about 9 KB of JavaScript and 2 KB of CSS (gzipped); the page rules (about 2.4 KB) and the dyslexia-friendly font (about 100 KB) load only when a visitor turns on a tool that needs them. In our Lighthouse test (mobile, a long page) the score stayed at 100 and Total Blocking Time at 0 ms.

Yes. The toolbar's HTML is the same for every visitor and choices are applied in the visitor's browser, so cached pages work. We tested WP Super Cache (Simple mode) and LiteSpeed Cache with JavaScript minify, combine and deferred loading and CSS combine turned on. If your optimization plugin delays JavaScript until the first interaction (often called "Delay JavaScript execution"), the button appears only after the visitor scrolls, taps or presses a key. To show it right away, add quicksloth-accessibility-toolbar and QSAB_CONFIG to that feature's exclusions.

The tools work through classes on the page's <html> element and the panel lives in a Shadow DOM, so they do not depend on your builder. We tested the block editor on Twenty Twenty-Five and Elementor: text size and the readable fonts reach Elementor widgets, and the toolbar does not load inside the Elementor editor canvas. If the toolbar shows up inside another builder's editor, turn it off there with the qsab_should_load filter (example below).

Yes. With the language setting on "auto", the toolbar follows the language WordPress sets for each page, which is what multilingual plugins change. We tested Polylang in Italian and in Arabic, where the panel mirrors itself for right-to-left. WPML uses the same WordPress setting; we have not tested it ourselves. All texts can be translated on translate.wordpress.org; until a translation for your language exists, the labels stay in English. You can also set a fixed locale, such as it_IT, under Settings → Accessibility Toolbar.

On your server: the plugin settings, the date the plugin was activated (for the one review request) and whether you dismissed that request. Deleting the plugin removes all three. In the visitor's browser: the tools the visitor turned on, in localStorage under the key qsab:v1, and, if they click "Hide toolbar for this visit", one flag in sessionStorage. Nothing is sent to your server or to us. See the Privacy section.

Yes, under Settings → Accessibility Toolbar: untick the tools you do not want under Tools shown; list page or post IDs under Do not show on these pages; hide the button on screens narrower than 768 px; or enter a CSS selector under Use my own button (CSS selector) so your own button or menu item opens the panel instead of the floating button. Developers can decide case by case with a filter, for example to hide the toolbar on WooCommerce checkout pages: add_filter( 'qsab_should_load', function ( $load ) { return function_exists( 'is_checkout' ) && is_checkout() ? false : $load; } );

No account, no API key, no logo or link on your pages (unless you turn on the optional credit line) and no external requests: the script, the styles and the font are served from your own site. Your theme, page builder or other plugins may make their own external requests (for example web fonts); those are not part of this plugin.