Technical Accessibility Standards

Principle 1: Information and user interface components must be presentable to users in ways they can perceive.

1. Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
2. Time-based Media: Provide alternatives for time-based media.
3. Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
4. Distinguishable: Make it easier for users to see and hear content including separating foreground from background.

Principle 2: User interface components and navigation must be operable.

1. Keyboard Accessible: Make all functionality available from a keyboard.
2. Enough Time: Provide users enough time to read and use content.
3. Seizures and Physical Reactions: Do not design content in a way that is known to cause seizures.
4. Navigable: Provide ways to help users navigate, find content, and determine where they are.

Principle 3: Information and the operation of user interface must be understandable.

1. Readable: Make text content readable and understandable.
2. Predictable: Make web pages appear and operate in predictable ways.
3. Input Assistance: Help users avoid and correct mistakes.

Principle 4: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

1. Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

There are a lot! If you are new to digital accessibility or want to learn more, there are great free resources available to start you off:

• Accessibility Fundamentals – A helpful overview from the W3C Web Accessibility Initiative (WAI)
• Digital Accessibility Foundations Course on edX – A free, self-paced course that takes about four-to-five (4-5) hours per week for four (4) weeks. You can return to it anytime.

These resources are a great way to build your understanding and help make digital spaces more inclusive for everyone.

Many accessibility consulting companies also provide free webinars to help you brush up on old and new topics.

You do not need to be perfect today. What matters is that you are aware of the requirements and are taking steps toward meeting them.

Focus on progress, not perfection

Federal and state agencies understand that accessibility improvements take time. What they are looking for is:

• A clear plan for how you will address accessibility issues
• Documentation of what you have already done
• A realistic timeline for fixing what is left

You have time

The federal deadline for WCAG 2.1 Level A and AA compliance is April 24, 2026. That gives you time to:

• Prioritize the most critical issues
• Build accessibility into your regular update cycles
• Get training and support for your team

Disabilities are not always visible

Many people have disabilities that are not obvious—such as vision or hearing loss, cognitive differences, or temporary conditions like a broken arm or eye strain. Just because no one has reported an issue does not mean no one is affected.

Your audience can change

Even if your current users do not report accessibility needs, future users might. Illnesses, injuries, or aging can also affect your current users. Accessibility helps ensure your product works for everyone—not just today's users.

It improves usability for everyone

Features such as clear navigation, readable text, and keyboard shortcuts benefit all users, not just those with disabilities. Accessibility often leads to a better overall user experience.

It shows you care

Making your product accessible shows that you value equity and quality. It reflects positively on your brand and can help your product stand out in the marketplace.

And yes—it is the law

If your product is used by public institutions such as ours, we are legally required to use accessible tools. That means your product must meet accessibility standards for us to continue using or purchasing it. Inaccessible digital resources create legal and reputational risks for both your organization and ours.

Accessibility has real-life impact

If people with disabilities cannot use your product, they may lose access to education or employment. In some cases, they may seek compensation for the barriers they have faced such as loss of their paycheck or tuition and fees.

Disability can affect anyone at any time

They may attempt to use assistive technology with your product and face access barriers. To learn more, please explore the Assistive Technology Guide to see how these tools work—and how your efforts help make them more effective.

Note: You may already use assistive technologies without realizing it—such as voice dictation, screen magnifiers, or closed captions. Digital accessibility makes these tools work better for everyone.

No. When people hear about the Web Content Accessibility Guidelines (WCAG), they often think it only applies to websites. But WCAG actually covers a wide range of digital experiences—including desktop software and mobile apps.

Even though "web" is in the name, many of the WCAG success criteria apply to things like:

• Keyboard navigation for users who cannot use a mouse
• Screen reader compatibility for users who are blind or have low vision
• Clear visual design and color contrast for readability
• Text alternatives for icons, images, and other non-text elements

If your product includes a desktop component, it should be evaluated against WCAG criteria just like a website or mobile app. Including this in your Accessibility Conformance Report (ACR) helps us understand how your product supports users with disabilities and ensures we meet federal and state accessibility requirements.

Which criteria are applicable to desktop software? In the International (INT) edition of the VPAT, check out the Criteria column under the WCAG 2.x tables. It will list out the different digital resources that are relevant.

Is your software also an authoring tool? Review your product from the author's perspective on relevant criteria as well.

It is a common belief that if your software runs on an accessible operating system—like Windows or macOS—or if it works with third-party assistive technologies, then it is automatically accessible. Unfortunately, that is not always the case.

While operating systems and assistive technologies provide a strong foundation, your software still needs to meet specific accessibility standards on its own. That is where the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA come in.

Even though WCAG was originally designed for the web, many of its success criteria apply directly to desktop software. For example:

• Can users navigate your software using only a keyboard?
• Are screen readers able to read all the content and controls?
• Is the text readable with good color contrast?
• Are error messages clear and helpful?

These are just a few of the things WCAG covers—and they apply whether your product is a website, a mobile app, or a desktop application.

So, even if your software "works" on an accessible platform, it still needs to be reviewed against WCAG criteria to ensure it is truly usable for everyone.

Which criteria are applicable to desktop software? In the International (INT) edition of the VPAT, check out the Criteria column under the WCAG 2.x tables. It will list out the different digital resources that are relevant.

Is your software also an authoring tool? Review your product from the author's perspective on relevant criteria as well.

Even if you are not building software or websites, digital documents and online training materials are still considered digital content—and they need to be accessible, too.

For example:

• PDFs, Word docs, and PowerPoint presentations should have proper heading structure, readable text, proper reading order, and alternative text for images.
• Online training modules should be navigable by keyboard, have captions for videos, and work with screen readers.
• Quizzes or interactive content should be usable by people with different abilities, including those using assistive technologies.

These are all covered under WCAG 2.1 Level A and AA, and they help ensure that everyone—including people with disabilities—can access and benefit from your content.

If your product includes documentation, e-learning, or support materials, it is still subject to accessibility requirements. Reviewing your content against WCAG success criteria helps ensure it is usable by all learners and users—and helps your organization stay compliant with federal and state laws.

Which criteria are applicable to documentation? In the International (INT) edition of the VPAT, check out the Criteria column under the WCAG 2.x tables. It will list out the different digital resources that are relevant.