AxesWeb Accessibility Solution
| 开发者 | axesweb |
|---|---|
| 更新时间 | 2025年9月12日 21:31 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.8 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
AxesWeb Accessibility Solution adds an accessibility toolbar to your WordPress site to help users customize their reading experience, in line with WCAG 2.1 and 2.2 guidelines. The widget is lightweight, configurable from the settings page, and designed to be theme-agnostic.
安装:
- Upload the plugin folder to
wp-content/plugins/or install it via the WordPress admin. - Activate the plugin via Plugins → Installed Plugins.
- Go to Settings → AxesWeb Accessibility to configure the widget position, theme, and options.
常见问题:
Does it require a specific theme?
No. It is designed to work with any theme.
Can I change where the widget button appears?
Yes. You can choose among multiple on-screen positions from the Settings page.
How do translations work?
The plugin is translation-ready. The base language is English and translations are managed on translate.wordpress.org.
Does this plugin collect personal data?
No. The plugin itself does not collect personal data. If you enable the user feedback form, the submitted information is emailed to the address you configure and not stored by the plugin.
Does the plugin load external resources?
Yes. It enqueues a single JavaScript file from the AxesWeb CDN to render the accessibility widget UI.
- URL:
https://cdn.axesweb.com/widget/{version}/accessibility-widget.js - Versioning: the plugin loads the latest available widget version from the CDN.
- Privacy: no tracking, no ads, and no public links are injected into the front-end by the plugin.
- Security: the script is enqueued via WordPress APIs (
wp_enqueue_script). No third-party PHP code is downloaded or executed.
更新日志:
1.0.5
- Move inline admin JS to enqueued
admin/admin.js - Use
wp_register_script/wp_enqueue_scriptand set async/crossorigin attributes - Document external service usage (AxesWeb CDN) with ToS/Privacy links
- Add API key activation flow; front-end widget script is enqueued only when activation is valid
- Replace base64 storage with hex-encoded IV/cipher for key persistence (backward-compatible)
- PHPCS/WPCS compliance fixes (Yoda conditions, comment punctuation, trailing commas) and minor hardening (TTL jitter for verify rechecks)
- Prefixed all plugin identifiers and option names to avoid collisions
- Added ABSPATH guards where applicable
- Ensured English descriptions in readme and headers
- Removed deprecated global alias to avoid generic
wpnaming - Minor hardening and cleanup
- Admin settings improvements and minor fixes
- Fixed support form handling and applied graphical corrections
- Initial stable release