WebMax<\/a> accessibility service and loads an accessibility widget on your front end after you connect an account.<\/p>\n\nThis is the official WordPress plugin from WebMax (webmax.co).<\/p>\n\n
What this plugin does<\/strong><\/p>\n\n\n- Loads the WebMax accessibility widget on your public pages when your account is connected<\/li>\n
- Lets you customize widget colors, position, language, statement link, and trigger options<\/li>\n
- Syncs those settings with your WebMax account<\/li>\n
- Shows plan\/subscription status and lets you start checkout on WebMax<\/li>\n
- Displays an accessibility statement generated for your site<\/li>\n
- Includes a dashboard with usage status and measured accessibility comparison scores<\/li>\n<\/ul>\n\n
External service<\/strong><\/p>\n\nThis plugin is a client for the WebMax accessibility service. Widget CSS and JavaScript ship inside the plugin (public\/css\/<\/code>, public\/js\/<\/code>) and are not loaded from remote CDNs. The plugin calls WebMax over HTTPS only for account\/API operations (service calls):<\/p>\n\n\n- API and account:
https:\/\/webmax.co\/api\/v1\/<\/code><\/li>\n- Widget initialization:
https:\/\/webmax.co\/api\/initWidget<\/code> (proxied through this site\u2019s REST route when serving the front-end widget)<\/li>\n<\/ul>\n\nA WebMax account is required. Data sent may include your site URL\/domain, account email, authentication token, widget customization settings, subscription\/billing requests, and (when you run a comparison audit) scan requests for your site URL.<\/p>\n\n
Creating an account, connecting the plugin, saving settings, managing billing, and running audits are user-initiated actions from the WordPress admin.<\/p>\n\n
The plugin does not add promotional \u201cPowered by\u201d credits or external marketing links on the public site.<\/p>\n\n
\n- Terms of Service: https:\/\/webmax.co\/pages\/term-and-conditions<\/li>\n
- Privacy Policy: https:\/\/webmax.co\/pages\/privacy-and-cookies-policy<\/li>\n<\/ul>\n\n
After activation, go to WebMax \u2192 Accessibility Controls<\/strong>, connect your account under Plan & Subscription<\/strong>, then customize the widget.<\/p>\n\nDevelopment \/ Source<\/h3>\n\n
The WordPress plugin PHP, admin assets, and styles are GPL-2.0-or-later (see LICENSE<\/code>).<\/p>\n\nThe front-end accessibility widget ships as a production Webpack build in public\/js\/main.js<\/code> (mode: production<\/code>, devtool: false<\/code>, no eval()<\/code> \/ eval source maps).<\/p>\n\nHuman-readable TypeScript source, Webpack config, and package.json are in widget-src\/<\/code>. Build steps are in widget-src\/README.md<\/code> and public\/js\/README.md<\/code>.<\/p>\n\nThird-party libraries bundled in public\/js\/main.js<\/code> (@popperjs\/core, axios) are attributed in licenses.txt<\/code>.<\/p>\n\n\n\n- Upload the
webmax-accessibility-for-wcag-section-508-ada-eaa-compliance<\/code> folder to \/wp-content\/plugins\/<\/code><\/li>\n- Activate the plugin through the Plugins screen in WordPress<\/li>\n
- Go to WebMax \u2192 Accessibility Controls<\/li>\n
- Connect your WebMax account under Plan & Subscription<\/li>\n
- Customize the widget and save your changes<\/li>\n<\/ol>\n\n\n
\nDo I need a WebMax account?<\/h3><\/dt>\nYes. The widget and cloud settings require a WebMax account. You can register or log in from the Plan & Subscription tab.<\/p><\/dd>\n
Why is the widget not showing on my site?<\/h3><\/dt>\nThe front-end widget loads only after a WebMax account is connected and the site has an active app ID. Confirm the status badge shows that accessibility is on.<\/p><\/dd>\n
Does deactivating the plugin delete my settings?<\/h3><\/dt>\nNo. Deactivation keeps your settings. Deleting the plugin removes stored options from WordPress.<\/p><\/dd>\n
Are passwords stored in WordPress?<\/h3><\/dt>\nNo. Login and registration send credentials to WebMax over HTTPS. WordPress only stores the returned account token and site identifiers.<\/p><\/dd>\n
Does this plugin guarantee legal compliance?<\/h3><\/dt>\nNo. The plugin provides an accessibility widget and related tools. It does not provide legal advice and does not guarantee ADA, WCAG, or other regulatory compliance.<\/p><\/dd>\n
Is this plugin translation-ready?<\/h3><\/dt>\nYes. Strings use the webmax-accessibility-for-wcag-section-508-ada-eaa-compliance<\/code> text domain.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n\n- Initial release<\/li>\n<\/ul>","raw_excerpt":"Add a WebMax accessibility widget so visitors can adjust text, contrast, and navigation for WCAG, Section 508, ADA, and EAA needs.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/354849","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=354849"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/webmaxco"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=354849"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=354849"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=354849"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=354849"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=354849"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=354849"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}