Accessibility vs Usability: Trade-offs of 3 Implementation Approaches

There are three ways to implement accessibility: adjusting style baselines, updating component specifications, or conducting a dedicated audit. The right choice…

Insights:Accessibility vs Usability: Trade-offs of 3 Implementation Approaches

Option 1: Start with Style Baseline

Approach: Enforce contrast, font size, line height, and focus styles in global CSS.

  • Pros: A single change covers the whole site — lowest cost.
  • Cons: Only addresses the visual layer; structural issues remain.
  • Best for: Existing sites needing quick wins.
  • Cost: 1–3 person-days.

Option 2: Built-in Standards in Component Library

Approach: Bake accessibility requirements (focus management, labels, ARIA) directly into components.

  • Pros: New pages are compliant by default — lowest long-term cost.
  • Cons: Requires refactoring existing components; high upfront investment.
  • Best for: Teams refactoring or maintaining a design system.
  • Cost: 1–3 weeks.

Option 3: Audit-Driven Remediation

Approach: Run tools plus manual audits, then fix issues one by one from a generated checklist.

  • Pros: Most comprehensive coverage; uncovers deep-rooted problems.
  • Cons: One-off effort; new code can re-introduce issues.
  • Best for: Sites with compliance mandates or major product launches.
  • Cost: Several weeks, including external assessment.

Comparison of the Three Options

Dimension Style Baseline Component Standards Audit-Driven
Coverage Visual layer Component layer Entire site
One-time cost Low Medium High
Long-term cost Low (requires manual upkeep) Low Medium (needs periodic re-audits)
Development requirement Low
Medium Medium
Applicable Phase All Phases Refactoring Stage Compliance Stage

Recommended Combination

  1. Start with a style baseline (1–3 days).
  2. Then gradually embed the guidelines into components (progress via new pages).
  3. If compliance is required, conduct a dedicated audit once.

Audit-only without updating components will see issues resurface within six months.

How to Choose

  • New site launch → Style baseline + component guidelines.
  • Aging site without a design system → Start with a style baseline, then upgrade components incrementally.
  • Government/industry compliance → prioritize specialized audits.

Common waste

  • Accessibility plugins purchased, but code structure unchanged.
  • Audit reports produced, but no one implements fixes.
  • Component standards documented only; new code ignores them.

Verification methods

  • Test core flows with keyboard only.
  • Use screen readers to check first screen and forms.
  • Zoom to 200% and inspect layout.
  • Scan for contrast issues and missing labels.

Boundaries

These three approaches solve "accessibility and operability," not "whether content is useful." Accessibility is the baseline of experience, not a source of competitive advantage.

Related reading: