Accessible Web and App Development to WCAG 2.2 AA
LaunchPad Lab builds and fixes web and mobile apps so they meet WCAG 2.2 AA, Section 508 and the ADA Title II rule. We audit what you have, fix the issues that block real users, and build new products that are accessible from the first sprint.
What Does WCAG Compliance Mean for Your App or Website?
The Web Content Accessibility Guidelines (WCAG) are the international standard for accessible websites and apps, published by the W3C. They have three levels, A, AA and AAA, and Level AA is the one laws and contracts usually require. The current version, WCAG 2.2, became a W3C standard in October 2023 and adds nine success criteria, including minimum target sizes, focus that stays visible, and logins that don’t depend on memory tests.
Depending on who you serve, one or more of these may apply:
- ADA Title II: a Department of Justice rule requiring state and local governments, including public colleges and universities, to make web content and mobile apps meet WCAG 2.1 AA.
- Section 508: accessibility requirements for federal agencies, often passed on to vendors and grant recipients through contracts.
- European Accessibility Act: accessibility requirements for many digital products and services sold in the EU, including e-commerce and banking.
Building to WCAG 2.2 AA covers WCAG 2.1 AA as well, so you meet today’s rules and are ready when standards move forward.
Why We Build Accessibility In From Day One
At LaunchPad Lab we put people first. It's one of the Company Constants we've carried since our earliest days. In practice, accessibility costs far less when it's part of design and development than when it's fixed after launch.
Accessible design system components
Buttons, forms, menus and dialogs are designed and tested for accessibility once, then reused everywhere. New screens start accessible instead of needing fixes later.
Automated and manual testing, including screen readers
Automated scanners catch some issues, but not most. We pair them with manual keyboard testing and screen reader testing on real flows like signing up, checking out and submitting forms.
Keyboard and focus management
Every action works without a mouse, focus moves logically through each page, and dialogs and menus trap and return focus the way assistive technology expects.
Keeping content accessible in your CMS
We set up your content tools so editors can’t easily break accessibility, with required alt text, heading structure and accessible embeds. Read how to maintain accessibility when using a CMS.
Better performance and search visibility
Accessible code uses clean, semantic HTML. That same structure loads faster, works on more devices and helps search engines understand your pages.
Accessibility Services
Accessibility audit
We review your key user flows against WCAG 2.2 AA and deliver a prioritized report, with each issue rated by severity and effort and paired with a clear fix.
Remediation of existing apps
We fix code, design and content issues in priority order, starting with the barriers that stop people from completing tasks, then retest to confirm each fix.
Accessible new builds
For new products, accessibility is part of every sprint: in the design system, the acceptance criteria and the definition of done.
Monitoring and team training
We set up ongoing checks so new releases don’t introduce regressions, and train your designers, developers and content editors on what to watch for.
Accessibility Deadlines to Know
| Requirement | Who it covers | Standard | Deadline |
|---|---|---|---|
| ADA Title II rule | State and local governments, including public universities and community colleges | WCAG 2.1 AA | April 24, 2026 for entities serving 50,000+ people; April 26, 2027 for smaller entities and special districts |
| Section 508 | Federal agencies, and vendors through federal contracts | WCAG 2.0 AA, through the 2017 refresh | In effect |
| European Accessibility Act | Businesses selling covered digital products and services in the EU | EN 301 549, aligned with WCAG | In effect since June 28, 2025 |
| ADA Title III | Businesses open to the public | No technical standard in the regulation; courts commonly reference WCAG | Ongoing legal risk |
This table is a summary, not legal advice. Talk with your counsel about which requirements apply to you.
Using AI Responsibly for Accessibility
AI can speed up accessibility work by drafting alt text and captions and flagging likely issues across large sites. We always keep a person in the loop to review what it produces, because a wrong description can be worse than none.
When you add AI features like chat assistants or agents, we make those accessible too. They work with a keyboard, announce new and streaming responses to screen readers, and show errors clearly.
What Clients Experience
More people can use your product
Customers, students and patients who rely on assistive technology can complete every task.
Lower legal risk
Documented WCAG conformance puts you in a stronger position with regulators, contracts and complaints.
Fewer support requests
Clear forms, readable content and predictable navigation help everyone, not only people with disabilities.
Better search performance
Semantic structure and descriptive content are the same signals search engines rely on.
Remediate or Rebuild?
Most apps can be fixed in place. Remediation makes sense when the architecture is sound and the issues are mostly markup, color, content and focus handling. A rebuild makes more sense when the app runs on an outdated framework, uses inaccessible custom components everywhere, or is due for a redesign anyway. An audit tells you which path costs less.
Frequently Asked Questions
What is WCAG 2.2 AA?
WCAG 2.2 is the current version of the Web Content Accessibility Guidelines, published by the W3C in October 2023. Level AA is the conformance level most laws and contracts require. It covers things like color contrast, keyboard access, screen reader support, visible focus and accessible forms and logins.
Is WCAG 2.1 still enough for ADA Title II?
The ADA Title II rule names WCAG 2.1 AA as the standard. We build to WCAG 2.2 AA, which includes everything in 2.1 AA plus newer criteria. That meets the rule today and leaves you ready if requirements are updated.
Do accessibility overlays make a site compliant?
No. Overlay widgets add a toolbar on top of a site but don’t fix the underlying code, so screen reader and keyboard users still run into the same barriers. Lasting compliance comes from fixing the code, design and content themselves.
How do you test for accessibility?
We combine automated scanning with manual testing. That means navigating every key flow by keyboard, testing with screen readers, checking color contrast and zoom, and reviewing content and forms. Automated tools alone miss many issues, so manual testing is where most real barriers are found.
Does the ADA Title II rule apply to our university or agency?
If you’re a state or local government entity, including a public college, university or community college, the rule applies to your websites and mobile apps. Private universities and businesses generally fall under ADA Title III instead, which carries legal risk but no specific technical standard. Check with your counsel to confirm your status.
Can you fix an existing app without rebuilding it?
Usually, yes. Most accessibility issues can be fixed in place by correcting markup, contrast, focus handling, labels and content. We start with an audit, fix the most serious barriers first, and recommend a rebuild only when the existing code would cost more to fix than to replace.
How long does an accessibility audit take?
For a typical web app, an audit of the key user flows takes a few weeks, depending on the number of flows, templates and platforms involved. You get a prioritized report you can act on right away, and we can start remediation as soon as it’s delivered.
Ready to Meet WCAG 2.2 AA?
Book an accessibility audit. We'll review your key flows, show you where people get stuck, and give you a prioritized plan to fix it.