Back to reviews and guides

Website ADA Compliance in Utah: Key Website Accessibility Requirements

This guide explains how federal accessibility laws apply to websites used in Utah, practical steps to reach WCAG 2.1 AA, common barriers and a clear remediation plan. It recommends audits, combined automated and manual testing, user testing, procurement clauses and ongoing monitoring.

Website ADA Compliance in Utah: quick answer

Yes. Websites used by Utah public entities or by businesses that serve the public should be accessible to people with disabilities. The legal rules that most often apply are federal: the Americans with Disabilities Act (ADA) and Section 504 when federal funding is involved. In practice, most organisations follow the Web Content Accessibility Guidelines (WCAG) as the technical standard, typically WCAG 2.1 at level AA.

Which laws apply and who is covered

Two federal provisions are most relevant.

  • Title II of the ADA covers state and local government services, so Utah state and local agency websites generally fall here.
  • Title III of the ADA covers places of public accommodation, which courts often interpret to include many business websites that offer goods or services to the public.

If your organisation receives federal funds, Section 504 adds requirements for accessibility. For private businesses in Utah, Title III will usually be the key law to review. For a binding legal opinion about a specific site or claim, consult a lawyer who specialises in accessibility law.

Which technical standard should you use

WCAG provides testable rules for accessibility. WCAG 2.1 level AA is the widely accepted baseline for web accessibility. WCAG covers content, navigation, forms, contrast, keyboard access and more. WAI-ARIA is a suite of attributes that helps assistive technologies interact with dynamic content.

How to assess your site: a practical step-by-step plan

1. Start with a scoping audit

Decide which pages, templates and web applications are in scope. Include customer-facing pages, login flows and transactional pages. Record content types, frameworks, CMS and third-party plugins.

2. Run automated scans

Use an automated scanner to find obvious problems quickly. Automated tools are fast but do not find everything. Treat these results as a prioritised starting list, not a final verdict.

3. Perform manual expert testing

Have an accessibility specialist test keyboard navigation, semantic HTML, forms, labels and ARIA usage. Manual checks find issues automated tools miss, like incorrect focus order and ambiguous link text.

4. Include real user testing

Test with people who use screen readers, switch devices and assistive input. Their feedback will expose real barriers and give concrete fixes that improve usability for everyone.

5. Prioritise fixes

Fix items that block transactions or critical user journeys first. Then address recurring template issues so fixes scale. Record each fix so you can show progress to stakeholders.

6. Publish an accessibility statement and contact route

Post a short accessibility statement that states your standard, what you are doing, and a clear way for users to report problems. Include a timeline for responses. Keep the language plain and the contact method accessible.

Common accessibility barriers and how to fix them

  • Missing alt text — Add descriptive alt text to informative images. Mark purely decorative images with null alt attributes.
  • Poor heading structure — Use semantic headings in order. Do not skip heading levels.
  • Keyboard traps — Ensure all interactive controls are focusable and usable by keyboard only.
  • Form controls without labels — Use label elements or aria-label for every input. Provide clear error messages.
  • Insufficient colour contrast — Meet WCAG AA contrast: 4.5:1 for normal text and 3:1 for large text.
  • Non-descriptive link text — Use link text that explains destination or action, not only “click here”.

Developer and content checklist for immediate changes

  • Ensure semantic HTML (nav, main, header, footer, h2-h6, p, ul, ol)
  • Make every control reachable and operable with keyboard alone
  • Add ARIA only where native HTML cannot provide the semantics
  • Provide captions or transcripts for pre-recorded audio and video
  • Validate colour contrast against WCAG AA ratios
  • Deliver meaningful alt text for images and aria-hidden for decorative items

Testing tools and techniques to use

  • Automated scanners to catch obvious errors
  • Browser accessibility inspectors to review semantics and focus
  • Screen reader testing with NVDA or VoiceOver
  • Manual keyboard navigation checks
  • Real-user testing sessions with people who have disabilities

Procurement and contracts: include accessibility from day one

When buying a new CMS, theme or third-party service, include accessibility requirements in the procurement documents. Ask vendors for evidence of WCAG conformance and for an accessibility remediation plan for preexisting barriers. Require accessibility testing as part of acceptance criteria.

Why automated scans are not enough (common mistake)

Automated tools detect 20 to 40 percent of accessibility issues at best. They miss context, user flow problems and many ARIA mistakes. Organisations that rely only on automation leave serious barriers in place. Combine automated checks with manual review and user testing.

Real-world prioritisation framework (information gain)

Focus on the tasks that affect revenue and duty of care. Prioritise login, checkout, account management and government forms. Fix template-level problems next so the change covers many pages. Finally, tidy low-traffic pages and legacy documents.

Ongoing maintenance

Accessibility is not a one-off project. Add accessibility checks to your release pipeline. Train content authors on simple rules such as writing useful alt text and using headings correctly. Re-run audits after major updates and after adding new third-party components.

If you receive an accessibility complaint or a demand letter, get legal advice. A trained accessibility lawyer can help evaluate the claim, advise on remediation timelines and work on settlement or defence options. Keep all remediation records and test results; they are useful during any dispute.

Where to find authoritative guidance

For technical rules, consult the WCAG documents and WAI-ARIA guidance from W3C. For the legal framework, review the ADA and Section 504 resources from official federal sites. Use trusted accessibility organisations for training and test methods.

Next practical steps for Utah organisations

  1. Run a quick site scan to find high-impact errors.
  2. Fix blocking issues on critical journeys.
  3. Create an accessibility statement and a reporting channel.
  4. Plan a full audit and schedule user testing.

If you want, I can list common automated tools, sample policy language for procurement documents, or a short template accessibility statement you can adapt for a Utah public agency or a private business.