| 开发者 | realmediail |
|---|---|
| 更新时间 | 2026年10月20日 03:49 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
#real-accessibility works, for example in your footer or main menu./wp-content/plugins/real-accessability.Yes. Every profile, adjustment, language and design setting is free. There's no paid version, no account and no usage limit.
No plugin can do that by itself. The menu lets visitors change how your site looks and behaves, which helps a lot of people, but WCAG, the ADA and similar laws are about the site itself: its code, content, images, forms and documents. If you want to know where your site stands, you can ask for a free quote for a professional audit on the plugin's "Accessibility audit" screen.
It gives visitors useful tools and a link to your accessibility statement. Like other accessibility laws, though, the EAA applies to the website itself. Use the menu together with an accessible theme, accessible content and, ideally, an accessibility audit.
No. The menu's code is about 30 KB compressed. It doesn't use jQuery or web fonts, and it doesn't load anything from other servers.
It sets no cookies and sends nothing about your visitors anywhere. Each visitor's choices are saved in their own browser (localStorage), so they carry over from page to page.
Yes. The plugin adds the menu itself and runs it in an isolated Shadow DOM, so it works with any theme or page builder, and your theme's styles can't change how it looks.
Yes. All adjustments are applied in the visitor's browser, so cached pages work as usual.
Yes. You can set the brand color, the button icon (a wheelchair or the accessibility symbol), the icon color, a circle, rounded or square shape, the size, the corner radius, one of 9 positions and the distance from the edge of the screen.
Yes. Desktop, tablet and mobile each have their own position, size, distance from the edge and menu side, and you can hide the button on any of them.
Yes. Any link to #real-accessibility opens the menu, for example a link in your footer, your main menu or your accessibility statement page.
46 languages and regional variants, including English, Spanish, Portuguese, Arabic, Russian, Hebrew, French, German, Italian, Dutch, Polish, Turkish, Ukrainian, Japanese, Chinese, Korean and Hindi. You decide which ones the menu offers, and visitors switch between them from the top of the menu.
Yes. Hebrew, Arabic, Persian and Urdu are fully supported. The menu and the settings screens both switch to right-to-left.
Add a complete translation of Real Accessibility to your site, either from translate.wordpress.org or as a .mo file in wp-content/languages/plugins. It will then show up under Real Accessibility > Languages.
No. You publish the statement as a normal page on your site, and the plugin adds an "Accessibility statement" button to the menu that links to it.
Yes. You can turn off any profile or adjustment on the Features screen, and the menu will only show the ones you keep.
Yes. Go to Real Accessibility > Accessibility audit in your admin and fill in the short form to get a free quote for a professional audit.
Only if you say yes. When you turn the menu on, you can choose to show a small credit at the bottom of the menu with a link to the plugin page on WordPress.org, or turn it on without one. You can change this at any time under Real Accessibility > Features.
The Button and menu, Features and Languages screens show a Cloudways hosting banner (or a WooCommerce hosting banner if WooCommerce is active). It's an affiliate link, so if you sign up through it, REALMEDIA may earn a commission at no extra cost to you. While one of those screens is open, the banner image loads from cloudways.com, which means Cloudways receives your browser's IP address and user agent. There is no impression counter or tracking script, and nothing from Cloudways is loaded on your site's front end or shown to your visitors.
It was removed in version 2.0. Screen readers, and the reading features that come with browsers and operating systems, do this job better.