Accessibility - State Information Technology Services

Digital Accessibility Resource Center

Welcome to Montana’s Digital Accessibility Resource Center, a practical hub to help state agencies create and maintain accessible digital services for everyone. Here you can explore guidance on ADA Title II, WCAG 2.1 Level AA compliance and key accessibility policies and legislation that apply to websites, applications, and electronic content. You’ll also find tools, testing resources, training opportunities, and best practices for making websites, applications, and documents easier to use for people with disabilities and the communities you serve.

What is ADA Title II?

ADA Title II is a federal civil rights law that prohibits disability-based discrimination by state and local governments. It requires that people with disabilities have an equal opportunity to participate in and benefit from government services, programs, and activities, whether those are offered in person, by phone, online through websites, or via mobile applications.

For digital services, ADA Title II now explicitly requires that most government web content and mobile apps meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, with only limited exceptions. This means accessibility is a core requirement, not a "nice to have," for how the State of Montana designs, builds, and maintains its digital services.


Key Features of ADA Title II Conformance (Digital)

At a high level, conformance with ADA Title II for websites and applications means:

  • Equal access to programs and services
    • People with disabilities can find information, complete tasks, and use online services in ways that are as effective as for people without disabilities, in terms of independence, timeliness, and privacy.
  • WCAG 2.1 Level AA as the technical standard
    • Web pages and mobile apps follow established accessibility guidelines for things like headings, color contrast, keyboard navigation, alternative text, forms, error messages, and multimedia, so they are perceivable, operable, understandable, and robust for users with disabilities.
  • Coverage of content “provided by or on behalf of” government
    • Digital services managed directly by the State and those operated by vendors on the State’s behalf (such as hosted portals or applications) must meet accessibility requirements, not just content on the main state website.
  • Ongoing effective communication
    • Information provided online must be communicated as effectively to people with disabilities as to others, using accessible formats, compatible technology, and reasonable modifications where needed.
  • Limited exceptions and equivalent access
    • Certain legacy or specialized content may fall under narrow exceptions, but agencies still must provide equally effective alternative access (for example, assistance or alternate formats) when a person with a disability needs that information.
  • Integration into the full ICT lifecycle
    • Accessibility is addressed from planning and procurement through design, development, testing, content authoring, and ongoing maintenance—not only as a one‑time project.

What This Means for Montana Websites and Applications

For staff and contractors who create or manage digital services for the State of Montana, ADA Title II conformance generally requires that you:

  • Design and develop sites and applications so they meet WCAG 2.1 Level AA.
  • Ensure editors follow accessible content practices (headings, links, alt text, documents, media). 
  • Test key user journeys with both automated tools and assistive technologies. 
  • Work with vendors so products delivered "for" the State meet these requirements. 

Understanding accessibility policies and legislation is key to ensuring equitable access to digital content and services. Federal laws like Title II fo the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act set essential standards for making websites, applications, and electronic resources accessible to individuals with disabilities. The U.S. Department of Justice (DOJ) further clarifies these requirements, emphasizing compliance with Web Content Accessibility Guidelines (WCAG). The resource below provide additional information related to these policies and legislation.

We strive to adhere to these standards to ensure our web content is accessible, inclusive, and user-friendly:

  • Web Content Accessibility Guidelines (WCAG) 2.1: This globally recognized standard ensures that web content is accessible to people with a wide range of disabilities, including visual, auditory, cognitive, and motor impairments. WCAG 2.1 builds on WCAG 2.0 and focuses on making content perceivable, operable, understandable, and robust across all devices, from desktops to mobile phones.
  • Level AA Compliance: This level strikes the right balance between accessibility and practicality. It includes key requirements like providing text alternatives for non-text content, maintaining a minimum color contrast ratio for text, and ensuring captions for multimedia content.
  • Accessible Rich Internet Applications (WAI-ARIA) Suite 1.2: This framework enhances accessibility for dynamic web content and applications by enabling assistive technologies to interpret complex user interfaces effectively.

Regular testing is crucial to maintain compliance. Here are some tools we’ve found helpful. This list does not constitute endorsement of any particular product or service. Please note, IT Procurement Requests (ITPRs) are still required to be submitted for agencies to use the tools below, unless they are part of the Approved Software List.

When using these tools, be sure to carefully note what standards a particular product follows such as WCAG 1.0 instead of 2.1.

Whether you're looking to understand the basics or seeking advanced techniques, there are numerous training resources available to help you build and maintain accessible digital services that comply with ADA Title II and WCAG 2.1 Level AA. Explore the options below to find the right tools and expertise for making your websites, applications, and digital content accessible.

These trainings are provided by recognized accessibility leaders and federal partners. Some content references Section 508 because it is aimed at federal agencies, but the underlying concepts, like WCAG, assistive technology support, and accessible documents, also apply to Montana's ADA Title II digital accessibility obligations.

This section helps Montana agencies, editors, and developers apply ADA Title II and WCAG 2.1 Level AA specifically to websites and applications. It focuses on practical steps you can take in your CMS, code, and design process to make your sites and applications accessible.

What You Need To Do

For Web Content Editors:

  • If you edit web content (text, images, links, basic pages): Focus on these WCAG 2.1 Level AA practices every time you publish.
  • Use proper headings (H1 once per page, H2/H3 in order)
  • Write clear, descriptive link text (no "click here")
  • Add meaningful alternative text to images that convey information; mark decorative images as decorative.
  • Ensure lists, tables, and labels are real structures, not just visual formatting.
  • Avoid using color alone to convey meaning; check color contrast before publishing.
  • Provide captions for all videos you publish; add transcripts for audio.

For Developers:

If you develop or configure applications and templates: Your work must ensure the templates and components editors user can meet WCAG 2.1 Level AA.

  • Ensure everything is keyboard accessible and visible (logical tab order, clear focus indicator).
  • Associate form fields with labels and error messages programmatically.
  • Use ARIA roles/states only when necessary and correctly.
  • Support reflow and zoom without loss of content or functionality.
  • Verify your app works with screen readers and magnification tools for key workflows.

Website and Application Accessibility Checklist

Use these resources to review pages and applications for WCAG 2.1 Level AA conformance and ADA Title II digital accessibility requirements. These checklists supplement, but do not replace, thorough testing with real users and assistive technologies. 

Key Accessibility Considerations for Documents

To ensure your documents are accessible, focus on these elements:

  • Headings and Structure: Use proper heading levels (e.g. Heading 1, Heading 2) to create a logical reading in order for screen readers.
  • Fonts and Contrast: Choose clear, readable fonts with sufficient size and color contrast to enhance visibility.
  • Alternative Text: Add descriptive alt text to images, charts, and other non-text elements so they are understandable to users relying on assistive technologies.
  • Tables: Use simple table structures with clear headers to ensure data is easy to navigate.
  • Links: Write descriptive link text (e.g. "View the report" instead of "Click here") to provide context.
  • White Space: Use adequate spacing between elements to avoid visual clutter and improve readability.

Tools for Creating Accessible Documents