Description
Feel Accessibility adds a floating button that opens a panel where each visitor can adapt your website to the way they read and browse. Everything is served from your own WordPress: no external scripts, no CDN, no cookies and no tracking.
It is a preferences toolbar, not a compliance tool. It does not make a website accessible by itself and it does not guarantee compliance with WCAG, EN 301 549 or any law. That depends on how the site is designed and built. We say so in the panel itself, and we ask you not to describe it to your visitors as “compliance”.
What visitors can do
- Text: enlarge it up to 150%, increase letter, word and line spacing (level 2 meets the WCAG 1.4.12 values), choose a legible typeface (Atkinson Hyperlegible) or one designed for dyslexia (OpenDyslexic), align text to the left.
- Colour and contrast: dark or light high contrast, or greyscale.
- Reading and content: highlight links and headings, a reading guide (a line or a mask that follows the mouse, the finger or the keyboard focus), hide images, read aloud (selection or main content, using the browser’s own voices).
- Motion and navigation: pause animations and autoplaying videos (turned on automatically if the device asks for reduced motion), large cursor, very visible keyboard focus.
The panel opens with the floating button, with Alt + Shift + A, or from any link or button with the attribute data-feel-acc-open. Preferences are saved in the visitor’s browser (localStorage) and can be reset with one click.
Built to be accessible itself
- Native buttons and radio inputs with accessible names; touch targets of at least 44 px.
- Keyboard: it opens, Esc closes it and returns focus to where you were. It never traps the keyboard.
- State is never conveyed by colour alone. It respects reduced motion and forced colours.
- The floating button moves above fixed bottom banners (cookie notices, chat bubbles) instead of covering them.
- Built in a Shadow DOM, so your theme’s CSS does not break it and it does not break your theme.
Privacy
No cookies. No third-party requests. Fonts are bundled with the plugin and only downloaded if a visitor turns them on. Choices stay in the visitor’s browser and are never sent anywhere. The plugin does not detect whether someone uses a screen reader or other assistive technology.
What it does not do
- It does not add alternative text to images, labels to forms or an ordered heading structure.
- It does not make a site work with a keyboard or a screen reader if it did not already.
- It does not pause carousels built with JavaScript or embedded third-party content (it does pause CSS animations, autoplaying videos and marquees).
- It is not a screen reader: read aloud uses the voices of the visitor’s browser, and for some languages there are few or none.
- It does not protect you from a complaint, and it does not make your site “compliant”.
Languages
The panel is available in Spanish, English, Catalan, Galician and Basque, following the language of the page (compatible with Polylang). The admin screen is in Spanish and English.
Third-party components
Two typefaces are bundled and only downloaded when a visitor turns them on: Atkinson Hyperlegible (Braille Institute of America) and OpenDyslexic (Abbie Gonzalez). Both are licensed under the SIL Open Font License 1.1; the licence text is in assets/fonts/LICENSE-FONTS.txt. There are no other third-party libraries: the plugin has no JavaScript dependencies and no build step, so the code you read is the code that runs.
Tested
Tested with automated browsers and axe-core against a real WordPress, including the widget open, closed, on mobile (320 px) and with every option on. Not yet tested with real screen readers on real devices. If you use one every day and find a problem, please tell us.
Screenshots
Installation
- Upload the
feel-accessibilityfolder to/wp-content/plugins/, or install it from the Plugins screen. - Activate the plugin. The button appears at the bottom right.
- Go to Settings Feel Accessibility to choose the position, size, colour, which options visitors see, and a link to your accessibility statement.
Tip: tick “Test mode” to see it only as an administrator before publishing it.
FAQ
-
Does it make my website accessible or compliant with WCAG?
-
No. It gives your visitors reading preferences. Real accessibility comes from how the site is designed, built and written. Treat this as a complement, never as a substitute.
-
No. The visitor’s choices are stored in their own browser (localStorage) and are not sent to any server. We still recommend mentioning it in your privacy policy; check with your adviser.
-
Does it work with my theme or page builder?
-
The panel lives in an isolated Shadow DOM, so it should work with any theme. The effects it applies to the page (contrast, text size…) should be checked on each site. It does not load inside the Avada, Elementor, Divi, Oxygen or Bricks visual editors.
-
Can I hide it on some pages?
-
Yes. Return false from the
feel_accessibility_enabledfilter, for example:add_filter( 'feel_accessibility_enabled', function ( $on ) { return is_page( 'landing' ) ? false : $on; } ); -
Can I open the panel from my own link?
-
Yes. Add the attribute
data-feel-acc-opento any link or button, or link to#feel-accessibility. You can also hide the floating button in the settings. -
Why is the contact block off by default?
-
An optional block at the bottom of the panel can link to Feel Hospitality Advisory (“Interested in this plugin? Contact us”), and an optional credit line can say “Accessibility by Feel”. Both are off by default: you decide whether to show them to your visitors.
-
Is it free?
-
Yes. The plugin is free and fully functional. If you need real accessibility work on your site (audit, fixes, content), Feel Hospitality Advisory offers it as a service.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Feel Accessibility” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Feel Accessibility” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.2.1
- The admin screen now shows a small, unobtrusive note instead of a highlighted contact card.
- Plugin header description in English. Licences of the bundled typefaces are now listed in the readme.
0.2.0
- The contact block (“Interested in this plugin?”) and the “Accessibility by Feel” credit line are now off by default and can be turned on in the settings.
- Banner, icon and screenshots for the plugin directory.
0.1.4
- The floating button now hides only when a fixed element leaves no room above it, so it stays reachable above large banners.
0.1.3
- Fix: the high-contrast modes (and every other effect) could lose against site rules with higher specificity. All page rules now carry extra specificity.
- The floating button hides while a fixed dialog covers almost the whole screen instead of covering its controls. Alt + Shift + A still opens the panel.
0.1.2
- The floating button moves above fixed bottom banners (cookie notices, chat bubbles) instead of covering them.
0.1.1
- Fix: “Hide images” no longer leaves light text on a light background.
- The panel only slides in (no opacity fade, which passed through low-contrast frames).
- The accessibility statement link follows the visitor’s language (Polylang).
0.1.0
- First version.