Royal Access – Accessibility Toolbar & WCAG Tools

No. Royal Access is NOT an overlay. Overlays reparse the DOM, interfere with screen readers, and inject automated ARIA — practices condemned by over 1,000 accessibility professionals. Royal Access simply adds CSS classes to the page based on user preferences, working WITH existing assistive technology.

No. Royal Access helps users customize their browsing experience and addresses some common automated accessibility issues (skip links, focus indicators, zoom restrictions). The built-in Accessibility Audit page also flags common content problems that plugins can detect reliably — missing alt text, heading hierarchy skips, empty or non-descriptive link text, and missing HTML language attribute — with plain-English guidance for fixing each one. However, full WCAG compliance requires manual auditing of your content, semantic HTML structure, alternative text for media, proper form labels, and more. No plugin can make a site fully compliant on its own — that requires human review and ongoing effort. Royal Access is a helpful tool, not a compliance solution.

No. ADA compliance for websites involves meeting WCAG standards, which requires comprehensive manual auditing beyond what any plugin can provide. Royal Access helps improve the user experience for visitors with accessibility needs, but it is not a substitute for a professional accessibility audit. This plugin does not provide legal advice.

Minimal impact. The toolbar CSS and JS together are under 15KB (gzipped). The OpenDyslexic font (~100KB) is only loaded when a user activates the dyslexia font feature.

No. User preferences are stored in localStorage, which stays in the browser and is never sent to any server. This makes Royal Access GDPR-friendly by default.

Yes. Since the toolbar HTML is the same for all visitors and preferences are handled client-side via localStorage, it works perfectly with all caching plugins.

Yes. Go to Royal Access > Settings and use the color pickers to set background, text, and accent colors for the toolbar.

No. No plugin, including Royal Access, can guarantee ADA or WCAG compliance — that requires manual auditing of your content, semantic HTML, alternative text for media, proper form labels, keyboard navigation, and ongoing review by qualified people. Royal Access is a helpful tool for improving the user experience, but treat real WCAG compliance as a process, not a checkbox. We strongly recommend a professional accessibility audit if compliance is a legal requirement for you.

Yes. The accessibility toolbar appears on the frontend and applies CSS classes to the document body, so it works with any block theme, classic theme, or page builder that outputs standard HTML. There is no integration step required.

Yes. The toolbar appears on every public-facing page including shop, cart, checkout, account pages, and member-restricted content. There are no per-store or per-membership integration requirements.

Frontend assets total under 60KB gzipped and load with defer . The OpenDyslexic font is only loaded when a user activates the dyslexia feature. Some of the automatic code-level fixes (consistent focus indicators, ensuring viewport meta allows pinch-zoom, skip-to-content link) can actually improve Lighthouse Accessibility scores.

Included. OpenDyslexic is bundled with Royal Access under its SIL Open Font License. There is nothing to install or download — when a user activates the dyslexia font in the toolbar, the font loads from your own server (no Google Fonts, no third-party CDN, no privacy concerns).

Yes. Royal Access is fully internationalized — every string in the toolbar, settings, and admin pages uses WordPress translation functions. Translations can be contributed via translate.wordpress.org, or you can use Loco Translate or Poedit to create custom .po/.mo files for your language.