Website ADA Compliance in New Hampshire: Website Accessibility Explained

Website ADA Compliance in New Hampshire: what it means and why it matters

Website ADA Compliance in New Hampshire covers how websites and web apps meet accessibility rules so people with disabilities can use them. Federal law, case law, and best practice standards guide what to do. This article explains the legal context, the technical standards you should follow, a practical remediation roadmap, contract and procurement pointers, and a short accessibility statement you can adapt.

Does the ADA apply to New Hampshire websites?

The Americans with Disabilities Act is federal. Businesses and public entities operating in New Hampshire remain subject to it. Title III covers places of public accommodation and courts and settlements often treat websites the same way as physical places when they serve the public. That means many New Hampshire businesses are expected to make their online content accessible.

Which technical standard should I use?

Use the Web Content Accessibility Guidelines, commonly WCAG 2.1 at level AA, as your primary technical target. WCAG defines success criteria for text alternatives, keyboard access, colour contrast, semantic markup, and more. Vendors, courts, and government contracts frequently reference WCAG 2.1 AA when judging compliance.

Common accessibility problems to check first

• Missing or poor alternative text on images
• Interactive elements not keyboard accessible
• Insufficient colour contrast for text and controls
• Unlabelled form fields and dropdowns
• PDFs and documents that are not tagged or readable by screen readers
• Reliance only on automated tests and not doing manual checks
• No clear accessibility statement or process for requests

How to test a website for ADA compliance

Combine automated tools, manual review, and user testing. Each method finds different problems.

Automated testing

• Run tools like axe, Lighthouse, or WAVE to get an initial list of technical failures.
• Automated tools cover about 20–40% of WCAG success criteria, so treat results as a starting point.

Manual review

• Keyboard check: try to complete common tasks using only Tab, Enter and Esc.
• Screen reader check: test main pages with NVDA, VoiceOver, or JAWS to verify reading order and labels.
• Contrast check: verify text and UI contrast using a color contrast analyser against WCAG AA ratios.
• Document review: open PDFs and Word docs to confirm they are tagged and searchable.

People testing

Invite users who have disabilities to test real tasks. Their feedback reveals barriers automation misses. Compensate participants and keep sessions task-focused.

A practical remediation roadmap (step by step)

1. Scope: list pages, templates, documents, and third-party tools. Focus on high-traffic and transactional pages first.
2. Audit: run automated scans, manual checks, and one or two screen reader walkthroughs for critical pages.
3. Prioritise: fix issues that block access first, such as keyboard traps, missing labels, and unreadable PDFs.
4. Remediate: assign fixes to developers, content editors and vendors. Use WCAG techniques for each issue.
5. Test: re-run automated and manual tests, then do a small user-test cycle for the remediated pages.
6. Document: keep a log of issues, decisions, and test results. Record dates and owners for each fix.
7. Maintain: add accessibility checks to release tests, content publishing workflows, and procurement requirements.

Typical approach: triage in weeks, remediation in months, and continuous monitoring thereafter. Timelines depend on site size and complexity.

Accessibility for PDFs and downloadable documents

Many accessibility complaints involve PDFs. Make documents accessible by using real text, proper headings, tagged PDF structure, and descriptive alt text for images. Where possible, publish HTML versions of important documents because HTML is faster to make accessible and easier for assistive tech to parse.

Contract and procurement checklist for New Hampshire organisations

When you buy software or hire developers, protect your organisation with clear accessibility requirements.

• Require conformance level: state WCAG 2.1 AA (or better) as the target.
• Ask for a VPAT or Accessibility Conformance Report from vendors describing what they support.
• Include remediation timelines and service credits for critical accessibility failures.
• Require accessibility testing before final acceptance and on major updates.
• Specify training and documentation deliverables, such as authoring checklists for content editors.
• Reserve the right to independent accessibility audits.

Accessibility statement: a short template you can adapt

Use an accessibility statement to show intent and provide a way for people to request help.

Sample accessibility statement

We aim to make our website accessible to everyone. We follow WCAG 2.1 AA standards and test regularly using automated tools and manual checks. If you have trouble using this site, contact us at [email or phone] and we will provide the content you need in an accessible format.

Common mistakes New Hampshire organisations make

• Relying only on automated tools and ignoring manual and user testing.
• Treating accessibility as a one-time project instead of ongoing work.
• Publishing untagged PDFs without offering HTML alternatives.
• Not training content authors, which leads to repeated errors in headings, links and images.
• Using overlays or widgets as a substitute for fixing the underlying accessibility issues.

What to do if you receive a complaint or legal notice

If you get a complaint, take it seriously. A prompt, documented response and a remediation plan reduce risk. Consult legal counsel experienced in accessibility law for advice tailored to your situation. Keep records of audits, remediation steps and communications related to the issue.

Where to find help

Work with an accessibility specialist for audits and remediation. Hire developers familiar with semantic HTML, ARIA roles, keyboard focus management and accessible forms. For internal teams, provide training on WCAG techniques and add accessibility checks to QA and content workflows.

Quick checklist: first actions for New Hampshire websites

• Publish a short accessibility statement and contact method.
• Run an automated scan of key pages and fix top-priority failures.
• Do keyboard and screen reader checks on transactions like forms and carts.
• Make PDFs accessible or provide HTML alternatives.
• Add accessibility requirements to vendor contracts and procurement.

Final notes

Website accessibility is technical and legal. Use WCAG 2.1 AA as your working standard, combine automated tools with manual checks, and keep remediation and documentation ongoing. For legal questions about obligations in New Hampshire, ask an attorney familiar with accessibility law.