WCAG accessibility for websites and apps

Start with the tasks people need to finish

A website accessibility audit needs a defined scope: pages, shared components, important journeys, and the states within them. A contact form includes its instructions, validation errors, and confirmation message. A checkout includes choosing an option, correcting a mistake, and completing payment. We agree on that scope before testing.

The review combines automated checks with manual testing of keyboard use, screen reader output, zoom, and interactive behavior. Findings should explain the barrier, where it occurs, how to reproduce it, and which WCAG criterion is relevant. We separate shared component problems from isolated content issues so the repair plan is useful to whoever implements it.

Agree on the target before changing the code

Bring any requirement that names WCAG 2.1 AA or WCAG 2.2, including its required conformance level. We put the agreed version, level, test coverage, and exclusions into the scope. A sample review covers the pages and states listed in that scope; its findings are not a statement about every untested part of a product.

If AODA website compliance or ADA website accessibility is driving the request, include the requirements supplied by your legal or procurement contact. We help implement the technical side and document the work; we do not provide legal advice or certify compliance. If the target is still unclear, paid discovery can help define the technical scope for your organization to review.

Typical fixes, from navigation to native screens

You can bring us an existing audit, a specific broken interaction, or a redesign that needs accessibility work before launch. Typical tasks include:

• Repair keyboard navigation, visible focus, and focus movement when dialogs open and close.
• Give form controls clear labels and connect instructions and error messages to the relevant fields.
• Review headings, landmarks, link names, and image alternatives in reusable templates and content.
• Adjust text contrast, layout at larger text sizes, and controls that are difficult to distinguish or activate.
• Add reduced motion behavior and check that essential information remains available when animation is reduced.
• For an accessible app, review screen reader labels, reading order, text scaling, and alternatives to gesture-only actions.

From first email to a checked handoff

Start with the website address or app build, platform, deadline, and the journeys that matter most. Include previous findings, known complaints, and any launch or procurement criteria. Tell us who owns the code and which parts depend on outside vendors. Arrange test accounts and staging access when needed; leave passwords out of the first email.

We define the review and repair scope, then agree on deliverables and the engagement. That may be paid discovery, a fixed-price project, or hourly work for a bounded fix. We take on a small number of projects at a time, so you work directly with the people doing the work.

Repairs are followed by checks of the affected interactions and agreed journeys. The handoff can include code changes, reproduction steps, retest notes, and remaining issues with clear ownership. We identify anything blocked by a platform or vendor and distinguish completed repairs from work still awaiting a decision.

Work with the platform you already have

Our website work covers custom sites, WordPress, Shopify, WooCommerce, Webflow, Squarespace, and Wix, plus Next.js, React, and TypeScript web apps. The repair scope depends on access to templates, components, and third-party interfaces. We inspect those boundaries before promising a particular change.

Testing tools can include browser accessibility inspectors, automated checks, contrast checks, and screen readers such as VoiceOver. Manual checks cover the agreed interactions. Native app work can address Swift and SwiftUI, Kotlin and Jetpack Compose, or React Native and Flutter, with testing scoped to the devices and platforms involved.

This suits owners with a specific backlog, product teams preparing a release, and agencies needing an implementation sub-project. We also fix products we did not build. An engagement expecting a compliance certificate or legal sign-off is outside this service.

Our proof is in products we own

We design, build, and maintain our own products end to end, including nine apps live on the App Store and this hand-built website. SNAAAAKE, one of our games, honors Reduce Motion and has VoiceOver menus. These are specific implementation examples, not a claim that every screen has passed a complete accessibility evaluation.

Rain, Moonflower, Broski, and ICD Atlas are also our own products. They demonstrate hands-on product development and maintenance; they are not client case studies. We bring that implementation experience to a defined accessibility scope, with findings and repairs you can inspect.