Back to reviews and guides

Website ADA Compliance in Maryland: What Does ADA Compliance Mean for Websites?

This article explains what Website ADA Compliance in Maryland means, with practical steps, WCAG 2.1 AA guidance, common barriers, testing methods, and an action plan. It includes a remediation roadmap, a short accessibility-statement template, and a checklist for quick fixes.

Website ADA Compliance in Maryland means that businesses and public services operating in Maryland should make their websites accessible to people with disabilities. The federal Americans with Disabilities Act applies nationwide, and courts and enforcement agencies have treated websites as subject to the ADA. This article explains practical steps, technical standards, testing methods, and what Maryland organisations should do first.

What ADA compliance means for websites in Maryland

The ADA is a federal civil-rights law. It protects people with disabilities from discrimination by public accommodations and state entities. A website that provides services or information to the public can trigger ADA obligations. That applies to sites hosted or operated from Maryland just as it does elsewhere in the United States.

Practical effect: make content perceivable, operable, understandable and robust for assistive technologies. Use recognised standards and keep records of efforts to improve access.

Which accessibility standard should you follow?

The web community and most enforcement guidance point to WCAG. Aim for WCAG 2.1 Level AA as the baseline. WCAG is organised into levels A, AA and AAA. Level AA combines basic and mid-range requirements many organisations use as a target.

Key numeric rules to know from WCAG 2.1:

  • Colour contrast for normal text: at least 4.5:1.
  • Colour contrast for large text: at least 3:1.
  • Provide text alternatives for meaningful images and captions for prerecorded video.

Common website accessibility barriers

  • Images without alt text or decorative images labelled unexpectedly.
  • Interactive controls and forms missing labels or instructions.
  • Navigation that cannot be used with a keyboard alone.
  • Poor colour contrast and low font sizes.
  • Video content without captions or transcripts.
  • Complex or incorrect heading structure that breaks screen reader flow.
  • PDFs and other documents uploaded without accessible structure.
  • Overuse of ARIA attributes or incorrect ARIA roles that confuse assistive tech.

Practical step-by-step remediation plan for Maryland organisations

1. Inventory and quick risk check

List all domains, subdomains and major sections. Note high-traffic pages and any pages used to buy, apply or register. These deserve priority.

2. Automated scan

Run an automated tool across the site to find obvious failures. Automated tools catch about 20 to 50 percent of issues but they are fast. The scan helps prioritise fixes.

3. Manual verification

Check keyboard only operation, try common screen readers, and inspect forms and ARIA. Manual checks find problems tools miss.

4. Prioritise fixes

Start with high-impact pages and easy wins. Examples of easy wins: add missing alt text, fix form labels, add page landmark elements, correct heading order, and add captions to short videos.

5. Implement code and content fixes

Use semantic HTML, proper form labels, ARIA when needed, accessible widgets, and CSS that preserves focus outlines. Update CMS templates so new content is published accessibly.

6. Test and validate

Combine automated scans and manual testing. Include a user test with at least one person who uses assistive technology where possible.

7. Publish an accessibility statement and contact path

State what level of conformance you aim for, list major exclusions if any, and provide an easy way for users to report barriers. Keep the statement accurate and update it after remediation.

8. Maintain and train

Integrate accessibility into content workflows. Train developers, designers and content editors. Schedule periodic audits and pre-launch checks for major changes.

Testing tools and methods

Combine tools and human review. No single tool or test is enough.

  • Automated tools: use one or more for broad coverage.
  • Browser audits: run a Lighthouse or similar audit during development.
  • Keyboard testing: navigate every page using only the keyboard.
  • Screen reader testing: test key pages with NVDA on Windows and VoiceOver on macOS or iOS.
  • Colour contrast checkers: verify contrast ratios for text and UI elements.
  • Document checks: convert PDFs to accessible formats or provide an accessible HTML alternative.

This is general guidance, not legal advice. If you receive a complaint or a demand letter, do the following quickly.

  1. Document receipt: save all communications and dates.
  2. Run an immediate audit of the cited pages and related areas.
  3. Share a clear remediation plan with timelines and milestones.
  4. Keep records of fixes and testing results.
  5. Consult an attorney experienced in accessibility law before making statements that involve legal positions.

Costs and timelines

Costs and schedules vary by site size and technology. Expect a small brochure site to take a few days to a few weeks of focused work. An ecommerce site or a complex web app can take several weeks to months. Ongoing maintenance reduces future costs.

Factors that drive time and cost: number of templates, third-party widgets, legacy code, and the volume of uploaded documents and media.

Accessibility statement template

Use this short template and adapt it to your organisation.

Our organisation is committed to accessibility and follows WCAG 2.1 Level AA as a goal. We are working to improve accessibility across our website. If you find a barrier, please contact us at [email or phone]. We will respond within [timeframe] and provide help or an alternative format where possible.

Maryland-specific resources to check

Start with federal guidance from the Department of Justice and with state agencies that handle disability rights or consumer issues. The Maryland Attorney General and any state accessibility office may publish guidance and contact points. If you need to resolve a legal dispute, consult a lawyer licensed in Maryland who specialises in accessibility law.

Quick accessibility checklist

  • All meaningful images have alt text.
  • Forms have labels and clear error messages.
  • Navigation works with keyboard only.
  • Colour contrast meets WCAG ratios.
  • Videos have captions and transcripts.
  • Heading structure is semantic and linear.
  • PDFs either converted to accessible HTML or provided in accessible form.
  • An up-to-date accessibility statement and contact method are published.

Website ADA Compliance in Maryland is a practical process. Start with an inventory and a short audit. Prioritise high-value pages and publish an honest accessibility statement. Keep testing, train staff, and consult a Maryland lawyer if you face a complaint. Those steps will reduce legal risk and make your site usable for more people.