Loading
Same Team · No Context Lost
Accessibility Remediation From Engineers, Not Consultants
Hands-on code fixes from the same engineers who understand what auditors look for. Every fix is verified with real assistive technology, not just checked off a list.
100%Post-Remediation Pass Rate
12+Years Experience
5,000+Issues Remediated
Trusted by teams who value quality
Why Remediation Fails
You have the audit. The spreadsheet is sitting in someone's inbox with 200 issues sorted by severity. Now what? Your development team looks at the findings and sees unfamiliar WCAG criteria, screen reader behaviors they have never tested, and ARIA patterns they were never trained on.
So they start guessing. Adding aria-hidden to things that should be visible. Wrapping everything in role="button" because it seems right. Hiding content with display:none and creating new barriers while trying to fix old ones. Three months later, the revalidation fails with a different set of issues. We have inherited this exact situation more than once.
The problem is not the audit. It is the gap between identifying issues and knowing how to fix them correctly. Accessibility remediation requires the same expertise as the audit itself: understanding how assistive technology actually interprets the DOM, how focus management works across dynamic interfaces, and how ARIA contracts interact with browser implementations. That gap is where most remediation fails. We close it.
What We Fix
Every category of accessibility barrier, from quick markup corrections to complex interactive pattern rebuilds.
Keyboard Navigation & Focus
Tab order, focus visibility, skip links, keyboard traps, and focus management in modals, dropdowns, and dynamic content. The most common source of critical failures.
Screen Reader Compatibility
Ensuring content is announced correctly by JAWS, NVDA, and VoiceOver. Live regions, announcements, reading order, and meaningful alternative text for all non-text content.
ARIA Implementation
Correct use of ARIA roles, states, and properties. Fixing misused ARIA that creates more barriers than it solves. One of the most common issues we encounter.
Color & Visual Accessibility
Color contrast ratios, information conveyed through color alone, text spacing, content reflow at 400% zoom, and motion sensitivity for users with vestibular disorders.
Semantic HTML & Structure
Heading hierarchy, landmark regions, list structure, table markup, and document language. The foundation that assistive technology relies on to parse your interface.
Forms & Error Handling
Label associations, error identification, input purpose, and status messages. Ensuring every form is completable by keyboard and screen reader users without confusion.
What You Get
Remediated Codebase
Production-ready code fixes implemented directly in your repository. Submitted through your PR process, following your existing code conventions.
Detailed Change Log
Every change documented: what was fixed, which WCAG criteria it addresses, and the technical approach. Your team understands exactly what changed and why.
Testing Confirmation
Verification that each fix passes with keyboard navigation, screen readers (JAWS, NVDA, VoiceOver), and browser zoom. Documented per-issue testing results.
Design Recommendations
Issues that require design-level changes are documented separately with specific recommendations. Your design team gets actionable guidance, not vague suggestions.
Revalidation Support
Optional revalidation audit at 50% of the original audit price. Confirms all fixes pass and no new issues were introduced during remediation.
How It Works
Review
We review your audit findings, assess the codebase, and identify patterns. Issues that share a root cause get grouped together. Fix the pattern once, and it resolves everywhere.
Prioritize
Critical issues blocking user access come first. Then serious barriers, moderate friction points, and minor improvements. You get a clear remediation plan with timeline and effort estimates.
Fix
Production-ready code changes submitted through your repository and PR process. Each fix follows your coding conventions and is documented with the WCAG criteria it addresses.
Verify
Every fix is tested with JAWS, NVDA, VoiceOver, keyboard navigation, and browser zoom. No fix ships without confirmation that it actually works with real assistive technology.
How We Fix It
Most remediation fails because developers fix issues one at a time, page by page, element by element. This is slow, inconsistent, and guarantees that the same issue reappears the next time someone builds a similar component.
We work at the component level. If a dropdown menu has a keyboard trap, we do not fix the dropdown on page A and then fix the same dropdown on page B. We fix the dropdown component itself, which resolves the issue everywhere it appears. This approach is faster, cheaper, and produces consistent results from our office in Boise to codebases across the country.
For issues that require ARIA implementation, we follow the WAI ARIA Authoring Practices, the canonical reference for how interactive patterns should behave with assistive technology. Every ARIA role, state, and property is implemented according to specification, not guesswork.
Component-Level Fixes
AT-Verified Changes
ARIA Best Practices
Keyboard Testing
PR-Based Workflow
Per-Issue Verification
Investment
$175/hrBase Rate · All Engagement Types
$2.5K–$50K+Typical Project Range
1–8 WeeksTypical Timeline
Pricing depends on the number and severity of issues, codebase complexity, and whether the code is modern or legacy. We provide a fixed-price estimate after reviewing your audit findings.
Estimation Guide by Severity
Critical / Serious Issues2–4 hrs each
Moderate Issues1–2 hrs each
Minor Issues15–30 min each
Legacy Codebase Adjustment+25–50%
Federal and government engagements: contact us for pricing and contract vehicle information.
Results in Practice
Case Study
Federal ServiceNow Portal Accessibility Overhaul
Full remediation of a federal agency's ServiceNow portal serving 10,000+ employees. 47 widgets brought into Section 508 compliance, passing federal review on the first attempt.
47Widgets Remediated
100%Pass Rate
3moTimeline
Case Study
Healthcare Portal Remediation Sprint
Remediated 200+ accessibility issues across 30 templates in a patient-facing healthcare portal. Prioritized by severity to resolve critical barriers first.
200+Issues Fixed
30Templates
6wkTimeline
Case Study
E-Commerce Checkout Remediation
Remediated 42 accessibility issues across a multi-step e-commerce checkout flow. Fixed keyboard traps, ARIA patterns, and form labeling to achieve full WCAG 2.2 AA compliance.
42Issues Fixed
35%Faster Flow
3wkTimeline
Let's Look at Your Audit Findings
Send us your audit findings and we will provide a scoped estimate within two business days. No pitch, no pressure. Just a clear picture of what remediation involves and what it costs.
What our clients say
Real feedback from teams we've worked with.
We came to Modern Softworks with an outdated website that was hurting our business. They didn't just rebuild it, they rethought the entire user experience. The site went from embarrassing to something we're proud to send people to. They walked us through every decision like we were part of the team.
Common Questions
What people usually ask before starting remediation. The honest answers.
Yes. Remediation requires documented findings to work from. If you already have an audit from another firm, we can work from that. If you need an audit first, our Accessibility Audit service provides the exact documentation we need to begin remediation efficiently.
Yes. We fix issues from any well-documented audit, ours or someone else's. We just need clear issue descriptions, WCAG success criteria references, and ideally reproduction steps. If the audit documentation is thin, we may need a brief scoping assessment first. You would be surprised how often audit reports leave out reproduction steps.
Critical and serious issues first. Things that completely block users from completing tasks or accessing content. Then moderate issues that create significant barriers. Minor issues like suboptimal labeling come last. Within each tier, we prioritize by user impact and the number of templates affected.
Yes. We work in whatever stack your application is built on. React, Angular, Vue, vanilla HTML/CSS, WordPress, ServiceNow, or legacy codebases. We follow your existing code conventions, submit through your PR process, and document every change. Your codebase, your conventions. We are guests in your repo and we act like it.
Some accessibility issues cannot be fixed with code alone. They require design-level decisions like restructuring navigation, rethinking color usage, or redesigning form flows. We document these separately with specific recommendations so your design team can address them.
Every fix is verified with the same assistive technology real users rely on: JAWS, NVDA, and VoiceOver screen readers, keyboard-only navigation, and browser zoom up to 400%. We document our testing for each remediated issue.
Yes. Revalidation is available at 50% of the original audit price. It confirms that all remediated issues pass and that no new issues were introduced during the fix process. We recommend revalidation for any engagement where compliance documentation is required.
Legacy codebases are the norm in remediation work, not the exception. Older patterns like table-based layouts, inline event handlers, and non-semantic markup require more careful fixes and additional testing. We factor this into our estimates, typically adding 25 to 50 percent for legacy code.
Related Services
Accessibility Emergency?
Facing an ADA demand letter, failed audit, or critical compliance deadline? We offer rapid-response accessibility remediation at $250/hr (minimum $5K engagement).