A managed accessibility service is an ongoing arrangement where an accessibility provider monitors accessibility, fixes issues each month, and tracks WCAG 2.2 AA conformance over time. Accessible.org’s managed accessibility service is built on this pattern: a flat monthly fee, a defined block of remediation time, AccessibilityTracker as the platform that holds the work, and custom orders available when an issue requires more than the included time.
The structure matters because WCAG conformance is not a fixed state. Every code deployment, content update, or template change can introduce new accessibility issues. A managed service keeps a website’s audit posture current as the site evolves.
| Key Point | What It Means for You |
|---|---|
| Flat monthly fee | $99 per month covers up to one hour of remediation work each billing cycle. |
| AccessibilityTracker required | You sign up for AccessibilityTracker separately. Scan results inside the platform drive the work that gets done each month. |
| Site code access required | Remediation happens directly in your site’s code, so Accessible.org needs working access before remediation begins. |
| Manual audit foundation | Issues acted on come from manual audit work against WCAG 2.1 AA, not scan results alone. |
| Custom orders for larger work | Items that exceed the included hour are quoted and fixed under the same workflow and tracking system. |
| Hour notification | You’re notified through Accessible.org’s channels when the monthly hour is reached or close to exhausted. |
How does the managed accessibility service work?
The service combines four parts that feed each other:
- Manual audit work against WCAG 2.1 AA
- AccessibilityTracker as the platform of record
- One hour of monthly remediation at a flat $99 per month
- Custom orders for any item that goes beyond the included hour
Each month, scan results generated through AccessibilityTracker, along with manual audit findings, identify the issues that need attention. Remediation happens directly in your site’s code. Each fix is tracked back to the WCAG 2.1 AA criterion it addresses, then re-tested before being marked closed in the platform.
How does the audit fit into the managed service?
An audit is the foundation is the foundation to WCAG conformance and a complement to our managed service. Think of our audits as individual projects whereas managed accessibility is our maintenance and managed of accessibility after you’ve remediated.
What types of issues get fixed during the included monthly hour?
The included hour typically covers issues that can be fixed at the code level without major restructuring. Common examples:
- Missing or weak alt text on meaningful images
- Empty buttons or links without accessible names
- Heading order corrections
- ARIA attribute fixes
- Color contrast adjustments in CSS
- Form labels that are missing or incorrectly associated
These are the highest-frequency issues in most audits. They are also the ones that, when left alone, repeatedly appear in scan reports across cycles. Fixing them inside the managed service keeps the same items from cluttering future audits.
Larger structural work, such as a full keyboard navigation rebuild or a complex widget remediation, typically falls outside the included hour and is quoted as a custom order.
Why is AccessibilityTracker required for the managed service?
AccessibilityTracker is the platform of record for every issue, fix, and validation status. The managed accessibility service runs through it from start to finish, which is why an active AccessibilityTracker subscription is required as a separate sign-up.
Inside AccessibilityTracker:
- Scan results identify candidate issues for review
- Audit findings sit alongside scan results, tied to WCAG 2.1 AA criteria
- Each issue tracks through identification, remediation, and re-testing
- Time spent on remediation is logged against the monthly hour
- Validation status is recorded once a fix passes re-testing
You keep access to the platform regardless of the managed service. The tracking history lives with your subscription, not the engagement.
Why is site code access required?
Genuine WCAG conformance requires changes in the underlying code. Overlay-style patches cannot reliably correct issues like keyboard focus order, semantic structure, or ARIA roles, because those issues live in the markup itself.
The managed service needs code access so remediation can:
- Edit templates, components, or theme files
- Adjust ARIA attributes and HTML semantics
- Update CSS for contrast and focus indicators
- Modify form structures and label relationships
This is why the service fits well with platforms like Shopify, where theme files can be edited directly, and with WordPress sites where changes can be made inside the theme or relevant plugin templates. Until working access is provided, remediation cannot begin, and any delay caused by access issues does not consume your monthly hour.
How is remediation tracked and validated?
Tracking is the record-keeping layer of the managed service. Each issue moves through defined states:
- Identified through audit or scan
- Assigned for remediation
- Fixed in code
- Re-tested against the relevant WCAG 2.1 AA criterion
- Marked closed once validation passes, or returned for further work
AccessibilityTracker tracks every issue from first identification through final validation, which is what gives the managed service its accountability over time. New audits add new issues to the same record, so the audit history stays connected month over month.
What happens when remediation needs go beyond the included hour?
The included monthly hour is a starting point, not a ceiling. When the hour is reached or close to exhausted, you receive a notification through Accessible.org’s communication channels. From there, any remaining or larger items can be moved into a custom order.
Custom orders follow the same workflow:
- Identified through the same audit and scan process
- Tracked in AccessibilityTracker
- Fixed in your site’s code
- Re-tested against the same WCAG 2.1 AA criteria
This keeps the audit trail clean and avoids splitting accessibility work across multiple vendors with different methodologies.
When does the managed accessibility service make sense?
The managed accessibility service is the right fit when:
- The site changes regularly through deployments or content updates
- The organization has ongoing ADA exposure across multiple states
- The European Accessibility Act (EAA) creates continuous obligations across EU markets
- The site runs on a frequently updated platform such as Shopify
- New features ship to the site month over month
A one-time audit ages out quickly in these conditions. Issues fixed in March may be undone by code shipped in May. The managed service keeps the audit current and the tracking system honest.
Frequently asked questions about the managed accessibility service
Is the managed accessibility service the same as a one-time WCAG audit?
No. A one-time audit produces a report at a single point in time. The managed service combines audit work with monthly remediation and ongoing tracking through AccessibilityTracker, so issues are fixed and re-validated as the site evolves.
Is AccessibilityTracker included in the $99 monthly fee?
No. AccessibilityTracker is a separate subscription that you sign up for independently. The $99 monthly fee covers up to one hour of remediation work performed against issues identified inside the platform.
Does the managed service support European Accessibility Act obligations?
The service supports ongoing WCAG 2.1 AA conformance, which is the technical standard most often referenced for EAA obligations. Continuous audit and remediation work helps keep a site aligned as content and code change across EU markets.
Can the managed service work for a Shopify site?
Yes. Shopify themes can be edited directly, which gives the provider the code access needed to fix issues at the source rather than through surface patches. The same workflow applies regardless of the underlying platform.
What happens if a remediation item takes longer than the included hour?
You’re notified when the monthly hour is reached or close to exhausted. Larger items are quoted as custom orders and follow the same audit, tracking, and validation workflow as the standard monthly remediation work.
Practical takeaways for organizations weighing managed accessibility
When considering a managed accessibility service, focus on:
- Whether the provider performs manual audit work, not just automated scans
- Whether issues are tracked in a platform you can access and review directly
- Whether code access is built into the working arrangement
- Whether the service ties remediation explicitly to WCAG 2.1 AA criteria
- Whether custom remediation work follows the same audit and tracking process
These markers separate a maintained accessibility relationship from a recurring scan subscription. For organizations with ongoing ADA exposure or EAA obligations, that distinction is what determines whether the audit work actually holds up between cycles.
