Will this make my site fully WCAG compliant?
No plugin can guarantee full compliance by itself. Open Accessibility helps with many visitor-facing controls, but accessibility also depends on content structure, alt text, headings, forms, keyboard behavior, and theme markup.
Where does the widget appear?
The widget can be positioned on the left side, right side, bottom left, or bottom right of the screen.
Can users hide the widget?
Yes. Visitors can hide the accessibility panel when they do not need it.
Can I create an accessibility statement?
Yes. The plugin includes an accessibility statement generator for site owners.
Does this slow down my website?
The plugin is designed to be lightweight, but you should still test it with your active theme, cache layer, and performance tooling.
What changed in 1.4.01?
Version 1.4.01 fixes the widget becoming unreachable when a contrast mode is switched on, raises the skip-to-content link above theme chrome, improves content detection for page builders including Divi, and adds a Reading Mask control. See the release notes for the full list, including what landed in 1.4.0.
The shared targeting layer that scopes text size, line height, readable fonts, link underlining, hide images, and grayscale to resolved content targets arrived earlier, in 1.3.02.
What is the difference between Reading Guide and Reading Mask?
Reading Guide draws a horizontal guide line that follows the pointer. Reading Mask dims the whole page except a band that tracks the pointer. They are separate controls and can be enabled independently under Accessibility → Features.
Does the plugin collect usage statistics?
Only if you turn it on. Usage Logging is opt-in and off by default as of 1.4.0. Enable it under Accessibility → Advanced if you want feature usage recorded.
Can I add Help or Feedback links to the widget?
Yes. The Links settings tab adds optional Help and Feedback links to the widget panel and exposes the Sitemap link. Developers can also filter the panel link list with open_accessibility_panel_links.
Can I rename the widget panel heading?
Yes. Use the Panel Title setting, or filter it with open_accessibility_panel_title. Any other widget label can be overridden with open_accessibility_strings.
My skip-to-content link goes to the wrong place. Can I change it?
Yes. Use the open_accessibility_skip_target_candidates filter to control which elements are considered. As of 1.4.0 the link resolves a real target on themes without an #content element, including block themes, and moves keyboard focus there rather than only scrolling.
Can my theme control where accessibility changes apply?
Yes. Themes can use PHP filters, HTML attributes, and the frontend JavaScript API. Start with data-oa-root, data-oa-target, and data-oa-ignore for template-level adjustments. Use PHP filters for global theme behavior.
Can I disable a default target group?
Yes. In open_accessibility_target_config, returning an empty selector array disables that default selector set. Empty roots also disables the automatic body fallback unless markup opts back in with data-oa-root. Built-in widget exclusions and explicit ignore attributes still apply.
How do I debug targeting?
In the browser console, run:
localStorage.setItem('openAccessibilityDebug', '1');
location.reload();
After the page reloads, inspect:
window.OpenAccessibility.debug();
window.OpenAccessibility.getTargets('readable_text');
Disable browser-side diagnostics with:
localStorage.removeItem('openAccessibilityDebug');
location.reload();