Priced, Not Patched: A Studio Discipline for Accessibility Work

Accessibility work has a familiar arc in independent studios: it enters late, arrives as a list of defects, and lands on the designer who is already closing out the project. The result is predictable. Hours are absorbed, margins narrow, and the client receives a remediation exercise rather than a designed outcome. For US studios entering 2026, that pattern is no longer a sustainable way to operate.

FNAD’s position is straightforward: accessibility is design work, and design work belongs in the scope. The discipline is not to treat every engagement as a compliance emergency. It is to estimate accessibility tasks with the same rigor applied to research, wireframes, or visual design, then price and contract them accordingly.

Define the work before estimating it

Accessibility is not a single activity. In most studio projects it spans four workstreams: design decisions, content structure, implementation review, and verification. A studio that estimates only a final audit will underprice the engagement because the most expensive accessibility problems are usually created earlier, when interaction patterns, color systems, form behavior, and content models are chosen.

A workable scope separates these activities. Design review covers contrast, focus states, target sizes, motion preferences, and reading order. Content work covers heading structure, link purpose, alternative text guidance, captions, and transcripts. Implementation review covers semantic markup, keyboard behavior, form errors, and assistive technology output. Verification covers manual testing and a documented handoff record. Each workstream should have an owner, an estimated range, and a stated assumption.

An hour-estimation framework that survives scrutiny

Independent studios do not need a universal formula, but they do need a defensible starting point. The following ranges are intentionally broad. They should be adjusted by project complexity, the number of unique templates and components, and the client’s capacity to supply content and make decisions.

• Discovery and accessibility requirements: 4–8 hours. Confirm the target standard, usually WCAG 2.1 AA for many US engagements, and identify procurement or regulatory obligations early.
• Design review per unique template: 2–4 hours. Review layout, interaction states, form design, and content hierarchy.
• Component library review per component: 1–2 hours. Account for menus, modals, carousels, accordions, tables, and custom controls.
• Content and authoring guidance: 4–6 hours. Provide alt-text and caption guidance, heading rules, and a simple content checklist for the client’s team.
• Implementation support and quality assurance: 10–15 percent of build hours. This covers developer questions, pull-request review, and iteration on defects.
• Pre-handoff audit: 8–16 hours. Include automated scans, manual keyboard testing, screen-reader spot checks, and documentation.
• Remediation reserve: 10–20 percent of the accessibility budget. Hold this explicitly rather than hiding it in general contingency.

Complex forms, data tables, media players, third-party embeds, and legacy content management systems push estimates upward. So does any requirement for independent third-party testing. The estimate should state those modifiers in plain language. A proposal that says “accessibility included” without a range is not a scope; it is a promise the studio may later regret.

Tiered options can help clients make an informed choice. An essential tier might cover design review and a pre-handoff audit. A standard tier adds implementation support and content guidance. An extended tier adds remediation cycles, assistive technology testing, and a post-launch review. The tiers should be described by activities, not by vague levels of assurance.

Contract language that assigns client responsibilities

Most accessibility failures at handoff are not purely technical. They involve content the client authored, third-party tools the client selected, or decisions the client delayed. The contract should make those boundaries visible without turning the relationship adversarial.

Useful clauses include:

• The client is responsible for accurate content, including alternative text for images it supplies and captions or transcripts for media it provides.
• The client will designate an accessibility contact empowered to review defects and approve remediation priorities.
• Third-party plugins, embeds, chat tools, mapping services, and payment processors are excluded unless specifically listed and tested.
• Content added after the agreed audit date is outside the reviewed scope and subject to a separate review fee.
• The studio will use commercially reasonable efforts to meet the stated standard within the defined scope; the client remains responsible for ongoing content governance after handoff.
• Re-testing after client-side changes is billed at an agreed hourly rate or covered by a retained accessibility block.

This language is not a shield against accountability. It is a map of who controls which inputs. Clients generally accept that map when it is presented at the proposal stage rather than discovered during a final review.

A pre-handoff audit checklist

A repeatable audit protects both quality and margin. At minimum, the studio should verify semantic headings and landmarks; full keyboard operation; visible focus; logical tab order; form labels, instructions, and error messages; color contrast for text and interface components; alternative text for meaningful images; captions and transcripts; reduced-motion support; zoom and reflow at 200 percent; language attributes; data-table headers; skip links; and accessible names for custom controls. PDFs and third-party embeds should be listed separately, with a clear statement of whether they were tested.

Automated tools are useful for catching some issues, but they do not replace manual testing. A short screen-reader check and a keyboard-only pass will reveal problems that scans miss. Keep a record of what was tested, on which browsers and assistive technologies, and what remains unresolved. That record is valuable to the client and instructive to the studio.

Explaining the business case without fear

The 2026 context matters, but it should be described accurately. State and local government entities with 50,000 or more residents face an April 2026 compliance date under the Department of Justice’s Title II rule; smaller entities have additional time. Federal agencies and many contractors continue to work under Section 508. Private-sector clients encounter accessibility in procurement questionnaires, internal standards, and litigation risk. These are real pressures, but a compliance scare is a weak sales argument and a poor basis for a professional relationship.

The stronger conversation is specific. Accessibility reduces rework late in a project. It improves usability for people using mobile devices, temporary injuries, aging eyesight, and noisy environments. It supports search visibility and maintainability. It can be the difference between qualifying for a public-sector contract and being screened out. For clients with 2026 deadlines, the business case is not abstract: an unplanned remediation cycle in the final month is more expensive than a scoped review in the first week.

Studios should also be candid about limits. No responsible studio should promise perfect conformance when the client controls content, third-party tools, and post-launch updates. The credible promise is a defined process, documented testing, and a clear path for remediation.

A line item and a professional habit

Pricing accessibility is not a surcharge. It is an accurate description of work that has always existed, often performed without a budget line. Independent US studios that name the work, estimate it in ranges, assign client responsibilities, and audit before handoff will produce better outcomes and more stable margins. FNAD encourages members to track these hours and share anonymized benchmarks so the profession can negotiate scope from evidence rather than habit.