Looks like you're in . Want the local site?
ACCESSIBILITY & RESPONSIVE UX
ADA Title III and Section 508 make web accessibility a legal requirement for US businesses and organisations. Lawsuit filings for web accessibility are in the thousands every year. We audit your site against WCAG 2.1 AA, fix what is non-compliant, and give you documentation that shows your compliance effort.
We are proudly featured on
Trusted by businesses we have shipped growth for
/ This is for you if
Web accessibility lawsuits under ADA Title III have been filed against e-commerce companies, restaurants, hospitality businesses, financial services firms, and retailers. If you have received a demand letter, the first step is demonstrating that you have identified the issues and are remediating them. We produce the audit report and fix documentation your legal team needs.
Section 508 of the Rehabilitation Act requires that electronic and information technology developed or procured by federal agencies be accessible. Contractors, vendors, and organisations that deliver digital products or services to federal agencies need to meet WCAG 2.1 AA as the technical standard. We audit to that standard and produce a Voluntary Product Accessibility Template (VPAT) ready report.
ADA web accessibility complaints do not require intent. A site can be fully functional for most users and still be inaccessible to a screen reader user trying to complete a purchase. If you have never had an accessibility audit, you do not know your exposure. We show you exactly where the failures are before someone else does.
/ What's broken
Product images, marketing graphics, and decorative icons without correct alt text are invisible to screen reader users. For an e-commerce site, this means a blind customer cannot identify what they are considering purchasing. It is one of the most common ADA web accessibility complaint triggers.
Brand colours that look intentional in a style guide may fail the 4.5:1 contrast ratio for normal text required by WCAG AA. White text on brand colour buttons, light grey body copy, and pale captions on image overlays. Each one is a measurable failure, not a subjective judgment.
A screen reader user navigating to a form field hears the field type (edit, combo box) but not what the field is for if there is no label. Contact forms, account creation forms, and checkout fields without correct labels are both a WCAG failure and a documented category in ADA web accessibility complaints. Placeholder text alone is not a label.
Horizontal scroll is a WCAG 1.4.10 (Reflow) failure. A layout that cannot reflow to a single column at 320px CSS width fails a Level AA success criterion. This is not just a mobile UX issue. It is a documented accessibility failure that affects users who zoom in due to low vision, as well as users on smaller or older devices.
/ What we engineer
Each workstream is built by the team that audits it, and wired into the rest of your growth system.
We run automated scans with Axe and WAVE and conduct comprehensive manual testing. Automated tools identify 30 to 40 percent of WCAG failures. Manual testing covers the remainder: logical heading structure, meaningful link text, focus order, form usability with a screen reader, keyboard trap issues, and time-based media alternatives.
We test with NVDA on Windows and VoiceOver on macOS and iOS. We navigate the complete site including menus, modals, carousels, accordions, and forms. We document what is announced, what is skipped, and what is navigated incorrectly, including any element that produces the kind of user experience that triggers an ADA complaint.
We navigate the full site using only a keyboard. We check that all interactive elements are reachable by tab, focus indicators are visible (not just present), modals release focus correctly on close, and skip navigation links function. We check for focus traps, which are a common source of ADA complaints in modal-heavy interfaces.
Every text-background combination is measured against WCAG AA (4.5:1 for normal text, 3:1 for large text and UI components). We document the exact ratio, the WCAG success criterion it fails, and the corrected colour value that passes.
We audit all images, icons, and non-text elements. We implement ARIA roles, labels, live regions, and landmark regions where missing or incorrect. We check that ARIA usage is correct, since incorrect ARIA is worse than no ARIA.
We test at breakpoints from 320px to 1440px on real and emulated devices. We identify WCAG 1.4.10 (Reflow) failures, 2.5.5 (Target Size) failures, and 1.4.4 (Resize Text) failures. We implement fixes in your codebase or theme files.
After implementation, we retest every issue from the original audit. The confirmation report documents pass or fail for each item with WCAG criterion reference. This document is what your legal team, DOJ, or federal procurement officer will want to see.
/ What changes
/ How it works
Automated scan plus manual testing across the full site. Screen reader navigation with NVDA and VoiceOver. Complete keyboard navigation pass. Colour contrast check on every text-background combination. Responsive testing from 320px to 1440px. You receive the complete audit report at the end of the week, with every issue categorised as critical, major, or minor, referenced to its WCAG 2.1 AA success criterion and level.
We review the audit report with you and agree on scope. We clarify which fixes are in our scope to implement and which require your team's input, such as alt text on images managed through your CMS. We confirm the timeline for the implementation phase.
We implement fixes in your codebase, CMS templates, or component library. For ARIA and focus management we work at the JavaScript and HTML level. For responsive and reflow fixes we work at the CSS level. Every fix is documented with a reference to the original audit issue it resolves.
We retest every item from the original audit. The confirmation report records pass or fail with WCAG criterion reference for each issue. We provide guidance on maintaining compliance, including how to handle alt text for new images and how to check new component additions against WCAG before deploying. You receive the final report in a format suitable for legal, procurement, and DOJ use.
/ Common questions
Straight answers on scope, timelines and cost. Anything else, ask us directly.
Ask us directlyThe Department of Justice has confirmed that Title III of the ADA applies to websites of businesses that are places of public accommodation, which includes most commercial websites. The DOJ issued final rules in 2024 requiring state and local government websites to comply with WCAG 2.1 Level AA, and has consistently treated WCAG 2.1 AA as the standard for private sector compliance as well. Thousands of ADA web accessibility lawsuits are filed annually in US federal courts, and the volume has increased each year since 2017.
ADA Title III covers businesses open to the public, including e-commerce, hospitality, financial services, and retail. It does not prescribe a specific technical standard, but WCAG 2.1 AA is the benchmark applied by courts and the DOJ. Section 508 applies to federal agencies and organisations that do business with federal agencies. It references WCAG 2.1 Level A and AA as the specific technical standard. The practical requirements are very similar, but Section 508 work produces a formal Accessibility Conformance Report (ACR) and VPAT.
An audit alone does not provide legal protection. What provides protection is demonstrated good faith effort: conducting an audit, documenting the findings, implementing fixes, retesting, and maintaining compliance over time. Courts and the DOJ look for evidence that a business took accessibility seriously and acted on it. Our documentation is structured to show exactly that.
A standard commercial website of 10 to 20 pages takes approximately three to five business days. E-commerce sites with product listing pages, checkout flows, and account management take longer because each flow must be tested separately. Dynamic content, carousels, and modal-heavy interfaces add additional testing time. We scope the audit before we start and give you a clear estimate.
We produce an audit report and retest confirmation report that contain all the information required to populate a VPAT or ACR. If you need a formally structured VPAT document for a federal procurement submission, we can produce that as an additional deliverable. Tell us upfront and we will include it in the scope.
Start here
We audit your site against WCAG 2.1 AA, test it with screen readers and keyboard navigation, and give you a prioritised report of every failure by severity. The documentation you receive after the fix cycle is structured for legal, DOJ, and procurement use. If you are responding to a demand letter, we move quickly.
Ignited Nepal
Growth engineering · replies within 1 business day
By continuing you agree to our privacy policy.
