Skip to content

Applying WCAG 2 to Non-web ICT

When we hear the term digital accessibility, many of us immediately think of web accessibility. And we wouldn’t be wrong. However, digital accessibility does not stop at the web. Many digital technologies operate outside of the web, and these non-web information and communication technologies also need to be accessible to people with disabilities. Some examples of these non-web technologies include desktop software and applications, email clients, native iOS and Android apps, as well as self-service ticketing kiosks and ATMs.

Fortunately, there’s guidance available for improving the accessibility of digital technologies beyond the web. The W3C’s Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) helps organizations understand how to apply web-based accessibility standards to non-web Information and Communications Technologies, ICT.

Before we get into some details of WCAG2ICT and how it can be applied, please note: 

WCAG2ICT is an informative W3C Group Note—it is not normative and does not set requirements. It provides guidance on applying WCAG 2 principles, guidelines, and success criteria to non-web documents and software. 

If your organization wants to use the information in WCAG2ICT to "help establish standards or regulations regarding accessibility" within your organization's ICTs, the W3C group has provided these notes to be of assistance. ~ WCAG2ICT Overview

What Is WCAG2ICT?

WCAG2ICT provides an authoritative interpretation of how WCAG2 can be applied in various contexts. It provides guidance on the application of the WCAG2 principles, guidelines, and success criteria to non-web ICTs. The latest version of WCAG2ICT was published on October 8, 2024.

Non-Web ICT Using WCAG2 Success Criteria

Native iOS app

By applying WCAG2ICT guidance:

The local ATM

By applying WCAG2ICT guidance:
  • The ATM includes tactile symbols next to card slots, headphone jacks, and keypads. Additionally, when a user plugs in headphones, the ATM automatically launches an audio interface that describes the available options, enabling blind users to access the same content that is visually displayed on the screen. SC 1.1.1: Non-text Content (Level A)

  • The on-screen text uses high-contrast color schemes (e.g., white text on a black background or black text on a yellow background) to ensure readability for users with low vision or color blindness. SC 1.4.3: Contrast (Minimum) (Level AA)

  • The ATM features a tactile numeric keypad and navigation keys (up, down, enter, and cancel) that enable users to complete tasks such as checking balances and withdrawing cash without needing to touch the screen. This functionality is crucial for users who are unable to use touch interfaces due to motor disabilities. SC 2.1.1: Keyboard (Level A)
  • The ATM allows users to extend session time or disable automatic timeouts when the audio interface is active, providing individuals with cognitive disabilities or those who read more slowly with extra time to complete transactions. SC 2.2.1: Timing Adjustable (Level A)

  • On-screen and audio prompts clearly state what is expected at each step. For example, “Please enter your 4-digit PIN, followed by the green Enter button.” These instructions are designed to support users with cognitive disabilities and those unfamiliar with the system.
    SC 3.3.2: Labels or Instructions (Level A)

The Benefits of WCAG2ICT Guidance

Applying WCAG 2 success criteria to your non-web ICT offers the same advantages as making your website accessible. By building accessibility into these technologies from the start, organizations can enhance their brand reputation and differentiation, reach a broader customer base, deliver a positive user experience, and foster creativity and innovation, the benefits of which extend across all digital experiences.

Why WCAG2ICT Matters for Accessibility

Non-web ICT must be accessible too. Under standards such as Section 508 (U.S.) and EN 301 549 (EU), accessibility requirements apply not only to web content but also to non-web ICT, ensuring equal access for people with disabilities in both digital and physical environments.

Resources

A human author creates the DubBlog posts. The AI tool Gemini is sometimes used to brainstorm subject ideas, generate blog post outlines, and rephrase certain portions of the content. Our marketing team carefully reviews all final drafts for accuracy and authenticity. The opinions and perspectives expressed remain the sole responsibility of the human author.

Maggie Vaughan, CPACC
Content Marketing Practitioner
DubBot