Skip to main content
ABØ STUDIOS

Accessibility problems don't need another report.

They need engineering.

ABØ Studios identifies, remediates, verifies, and documents accessibility barriers in real digital products.

Finding a failure and repairing its behavior are different jobs.

The Report

A document that names a failure. It sits in a backlog because no one knows how to fix the source code, or who owns it.

The Engineering

A person opens the codebase, locates the broken component, refactors it, and verifies the fix with assistive technology.

The Process

Five steps. One codebase. Verified evidence at the end.

  1. 01

    DETECT

    Automated scans flag potential failures. Assistive-tech testing finds what scanners miss.

  2. 02

    DIAGNOSE

    Source review locates the exact component, the broken pattern, and the accessibility tree mismatch.

  3. 03

    REMEDIATE

    The actual source code is refactored. Semantic HTML, ARIA attributes, focus management — whatever the component needs.

  4. 04

    VERIFY

    The fix is tested with NVDA, VoiceOver, and keyboard-only navigation. Behavior matches what sighted users see.

  5. 05

    PROTECT

    Automated regression tests are merged into your repository. The barrier cannot silently return.

The proof, immediately

Not a demo. A real product, a real barrier, a verified fix.

Cal.diy is a real, open-source scheduling app. A person using NVDA could not reliably tell which date was which. Here is exactly what that sounded like — before ABØ touched the code, and after.

Before — NVDA, date cell

11 button

A bare number. No indication it was a date, a button, available, or selected.

After — NVDA, same date cell

August 2026 grouping Tuesday, August 11, 2026, available toggle button pressed

Full accessible name, locale-aware, with selection state exposed via aria-pressed.

Before — NVDA, time slot

4:00am button

A bare time. No date context, no availability status.

After — NVDA, same time slot

4:00am on Tuesday, August 11 toggle button not pressed

Date context and availability state announced. Screen reader user can make an informed choice.

23/23 targeted unit tests passing

Read the full technical teardown
The Flagship

From accessibility backlog to verified remediation.

01

Scope

We identify the critical flow, the component boundary, and the success criteria.

02

Baseline

Current state is documented with assistive technology. What breaks today.

03

Engineering

The source is refactored. Semantic HTML, ARIA, focus management — whatever the component needs.

04

Verification

Fixes are tested with NVDA, VoiceOver, and keyboard navigation. Behavior matches intent.

05

Evidence / Handoff

Dated screenshots, transcripts, and regression tests merged into your repository.

Discuss a Conformance Sprint

Scoped pilots available from approximately $1,500.

Procurement Readiness

Technical evidence for procurement conversations.

When your organization needs to demonstrate accessibility compliance to a vendor, evaluator, or public body — we provide the engineering evidence that makes the conversation credible.

Technical Assessment

Current state documented against WCAG 2.2 criteria with source-level findings.

Remediation

The actual barriers are fixed in the codebase. Not reported — repaired.

Verification

Behavior confirmed with assistive technology. Evidence is dated and reproducible.

Documentation

Engineering evidence organized for ACR/VPAT preparation. No compliance claims.

We do not provide legal advice, guarantee ADA compliance, or claim WCAG conformance on your behalf. We provide the engineering evidence your procurement process needs.

Start a Procurement-Readiness Pilot
For Agencies

Your accessibility engineering layer.

You build digital products for clients. You need accessibility expertise without hiring a full-time specialist. ABØ embeds into your engineering workflow — reviewing components, remediating barriers, and handing you verified evidence your clients can trust.

White-label or co-branded. We work inside your repository, follow your patterns, and make your agency the one that ships accessible products.

Start an Agency Partnership Conversation
Engineering Rigor

How we test.

Keyboard

Tab order, focus traps, visible focus indicators, and state management through keyboard-only interaction.

Screen Reader

NVDA and VoiceOver. Verifying semantic meaning, announcements, and navigation landmarks.

Visual / Interaction

Contrast ratios, target sizes, layout reflow at 400% zoom, and reduced-motion behavior.

Engineering

Source-level review of ARIA attributes, semantic HTML, and component architecture.

Evidence

Dated screenshots, NVDA transcripts, keyboard walkthroughs, and regression test logs.

No overlays.

No fake compliance scores.

Fix the interface.

Verify the behavior.

Show the evidence.

Show us the workflow that needs to work.