A widget is one layer
Visitor controls may help some people adjust presentation, but they do not replace accessible design, semantic code, captions, text alternatives, keyboard behavior, documents, or content.
Included accessibility support widget
UserWay on CMS Max Websites
Offer visitor-controlled presentation tools as one part of a broader accessibility program.
Installing the CMS Max UserWay plugin activates a shared accessibility widget script with no tenant credentials or additional plugin settings. CMS Max does not load that script after a visitor explicitly rejects optional cookies, and installation also enables the site cookie-policy banner.
- Included widget
- No tenant credentials
- Consent-aware loading
- Cookie banner
- Accessibility program
with CMS Max
01Install widget
02Test real journeys
03Remediate + govern
Program architecture
Technology supports the decision; it does not own the outcome.
Define the purpose, data boundary, customer experience, operator, limitations, failure path, evidence, and success measures before installing or connecting a service.
Use standards and human evaluation
W3C notes that tools cannot determine accessibility by themselves. Combine automated checks, manual testing, assistive-technology review, and feedback from people with disabilities.
Maintain accessibility continuously
New pages, products, forms, media, documents, scripts, popups, checkout changes, and third-party widgets can introduce barriers after launch.
Current or scoped capabilities
Build the narrow workflow the business can operate well.
Availability depends on the documented scope, active plugin or completed custom implementation, required accounts, current provider features, data quality, consent, plan limits, and tenant configuration.
Install-and-enable workflow
Activate UserWay from CMS Max plugins. The current settings page contains no tenant fields, keys, account synchronization, or editable widget configuration.
Shared client-side widget
When active and eligible to load, CMS Max injects the shared UserWay widget script into the public page for visitor use.
Optional-cookie rejection gate
The CMS Max frontend does not inject the UserWay script after a visitor explicitly rejects optional cookies. Review actual regional consent and disclosure requirements.
Banner activation
Installing UserWay enables the CMS Max cookie-policy banner. The website owner must review copy, categories, privacy-page link, defaults, and interaction behavior.
Presentation adjustment tools
The provider widget can offer supported visitor controls such as text, contrast, cursor, reading, and navigation adjustments, subject to the current provider service.
Accessibility work remains in the site
CMS Max teams must still design, write, code, test, remediate, document, train, monitor, and respond across the actual customer journeys.
Decision and operating flow
Keep every handoff observable and reversible.
Each stage needs valid inputs, an explainable result, an exception path, and a named owner.
Inventory
Map pages, templates, media, forms, documents, and integrations.
Evaluate
Use automated, manual, assistive-technology, and user testing.
Remediate
Fix source content, design, code, and process barriers.
Support
Offer the widget, statement, and feedback channel.
Govern
Retest releases, content, and third-party changes.
Implementation sequence
Move from intent to production evidence.
Use representative users, data, devices, edge cases, failures, provider states, and operational reviews before relying on the workflow.
01. Establish the accessibility program
Assign executive, product, design, development, content, QA, legal, procurement, and support ownership with standards, scope, budget, and timelines.
02. Inventory representative journeys
Cover navigation, search, product discovery, forms, errors, account, cart, checkout, documents, video, popups, support, and third-party widgets.
03. Activate and disclose UserWay
Install the CMS Max plugin, review the cookie banner and privacy information, and test widget availability under each relevant consent state.
04. Evaluate beyond automation
Combine automated tools, keyboard-only review, zoom and reflow, screen-reader testing, captions, color and contrast checks, cognitive review, and disabled-user feedback.
05. Remediate the source
Prioritize blockers and high-impact journeys, fix templates and reusable components, update content and documents, verify third-party dependencies, and retest.
06. Publish and maintain evidence
Keep an accurate accessibility statement, contact path, issue backlog, release criteria, training, procurement checks, test records, response targets, and regular reassessment.
Operational ownership
Know which system and team controls each outcome.
Clear boundaries make customer support, privacy, security, accuracy, billing, incident response, and controlled change faster.
- CMS Max
- Provides the installation signal, consent-aware shared script injection, cookie-banner activation, website platform, and source components that teams configure and test.
- UserWay
- Owns the current widget script, visitor controls, provider service, infrastructure, documentation, and product changes.
- Website owner
- Owns accessibility strategy, conformance claims, legal review, content, policies, feedback, remediation priorities, third parties, staffing, and public communication.
- Delivery team
- Owns accessible design, semantic implementation, content quality, manual and assistive-technology testing, defect remediation, regression prevention, and evidence.
Documentation and related resources
Confirm current standards and provider requirements.
Provider products, data, plans, APIs, scripts, policies, and supported features change. Use official documentation and the live account during implementation.
Implementation FAQ
Resolve the practical questions before launch.
Turn each answer into configured rules, representative tests, monitoring, and written ownership.
Is UserWay included with CMS Max?
The current CMS Max plugin page describes UserWay as part of the core website platform and included with the CMS Max subscription. Provider offerings and account terms may still change.
Does the plugin require a UserWay API key?
No. The current CMS Max UserWay plugin has no settings fields or tenant-specific credentials. Installation status controls whether the shared widget script is eligible to render.
Does UserWay load after optional cookies are rejected?
No. CMS Max tests confirm that the shared UserWay script is not injected after the visitor explicitly rejects optional cookies. Review the full consent and disclosure design for the site.
Does installing UserWay make a website ADA or WCAG compliant?
No tool or widget alone can determine or guarantee accessibility or legal compliance. W3C recommends automated and manual evaluation plus knowledgeable human judgment.
What work is still required?
Review and remediate templates, content, media, documents, navigation, forms, errors, keyboard behavior, screen-reader output, zoom and reflow, contrast, motion, checkout, and third-party tools.
How should accessibility be maintained?
Assign owners, publish an accurate statement and feedback path, include disabled users, train teams, test representative journeys, fix source issues, monitor regressions, and reassess after meaningful changes.
Build with evidence
Connect the service to a workflow the business can explain and improve.
Bring the use case, account, data, standards, consent requirements, owners, test plan, exception handling, and success measures. CMS Max will help map the supported path.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.