Why Is Sign Language Still Invisible in Accessibility?

Accessibility is becoming more visible.

Sign language often isn't.

Captions are increasingly common.

Addressing the invisibility of sign language in accessibility: advocating for its integration as a standard language option to ensure equal visibility, access, and communication for all.

• Speech-to-text is available on most smartphones.

• Text-to-speech is built into major operating systems.

• AI accessibility tools are appearing across websites, applications, and services.

  
  

  Yet sign language frequently remains absent from websites, accessibility menus, public information, procurement requirements, and user preference settings.

  
  

Why?

Accessibility Does Not Automatically Mean Sign Language Inclusion

Many organisations proudly describe themselves as accessible.

They may offer:

• Captions

• Alternative text

• Screen reader compatibility

• Colour contrast compliance

• Keyboard navigation

• Language translation tools

All of these are important.

All of these should continue to improve.

But there is a question we rarely ask:

Where is sign language?

A website may offer five spoken languages.

A streaming service may provide subtitles in multiple languages.

An accessibility menu may include dozens of settings.

Yet sign language is often nowhere to be found.

Accessibility and sign language inclusion are not always the same thing.

The Visibility Problem

For many Deaf sign language users, the challenge is not simply access.

The challenge is visibility.

Sign language is frequently treated as something separate.

Something additional.

Something that must be requested.

Something that arrives after the system has already been designed.

This creates an important difference.

Most users can immediately see whether their language is supported.

Sign language users often cannot.

The result is that sign language exists at the edges of many accessibility ecosystems rather than at the centre.

Not because organisations are intentionally excluding sign language.

But because sign language is often invisible during design, planning, procurement, and implementation.

The Language Problem

Part of the challenge comes from how sign language is viewed.

Too often, sign language is treated as an accessibility feature.

But sign language is not an accessibility feature.

It is a language.

Nobody would describe English as an accessibility feature.

Nobody would describe French as an accessibility feature.

Nobody would describe Spanish as an accessibility feature.

British Sign Language is a language.

American Sign Language is a language.

Auslan is a language.

Irish Sign Language is a language.

When sign language is viewed primarily through an accessibility lens, it becomes easier to position it as optional.

When sign language is recognised as a language, expectations change.

Visibility changes.

Inclusion changes.

Design decisions change.

The Measurement Gap

Accessibility is increasingly measured.

We measure:

• WCAG compliance

• Colour contrast

• Keyboard accessibility

• Screen reader compatibility

• Caption availability

• Accessibility errors

According to the WebAIM Million Report 2026, 95.9% of the world's top one million homepages contain detectable accessibility failures.

Yet there is no equivalent global benchmark tracking sign language visibility across websites and digital services.

We can measure accessibility errors.

But we struggle to measure whether sign language is present at all.

• How many websites provide sign language content?

• How many accessibility menus include sign language options?

• How many public services offer sign language through QR codes?

• How many digital platforms allow users to set sign language as a communication preference?

The answer is that we rarely know.

And if something is not measured, it becomes easier to overlook.

Where Sign Language Is Often Missing

Consider how many places we encounter information every day:

• Websites

• Government services

• Healthcare information

• Education platforms

• Public transport systems

• Banking services

• Customer support systems

• QR code information points

• Streaming services

• Video platforms

  
  

Now ask a simple question:

How often is sign language visible?

Not available upon request.

Not hidden three clicks deep.

Visible.

How often do we see:

• A BSL option alongside language choices?

• A QR code linking directly to sign language content?

• A sign language preference setting?

• Sign language versions of key public information?

• Sign language integrated into user journeys from the beginning?

The answer is often: not enough.

Visibility Creates Access

What people see influences what people prioritise.

What organisations measure influences what organisations improve.

What designers include influences what users experience.

Visibility creates awareness.

Awareness creates inclusion.

Inclusion creates access.

If sign language is invisible within accessibility ecosystems, sign language users risk remaining invisible within the experience.

What Good Could Look Like

Imagine a different approach.

A website language menu includes:

• English

• Welsh

• French

• German

• BSL

A hospital letter includes a QR code linking directly to a BSL explanation.

A government service remembers your communication preferences.

A streaming platform offers sign language alongside subtitles and audio description.

An accessibility menu includes sign language options as naturally as caption settings.

A communication profile allows users to choose:

• Spoken language

• Sign language

• Captions

• Easy Read

• Audio description

• Visual communication preferences

  
  

Not as a special adjustment.

Not as an afterthought.

As standard.

Beyond Technology

Technology can help.

AI may help create new ways to deliver sign language content.

Translation systems may improve.

Digital humans may become more realistic.

Accessibility tools will continue to evolve.

But visibility is not primarily a technology problem.

It is a design problem.

A policy problem.

A measurement problem.

A recognition problem.

Technology alone cannot solve invisibility.

People must first recognise that it exists.

Looking Ahead

The accessibility conversation is changing.

The next challenge may not be creating more tools.

The next challenge may be ensuring that sign language is visible throughout the entire accessibility ecosystem.

Not just at the point of delivery.

Not just when requested.

Not just as a reasonable adjustment.

But from the beginning.

Because accessibility without visibility is incomplete.

And if sign language remains invisible within our systems, sign language users will continue to encounter barriers before communication even begins.

The challenge is not only accessibility.

The challenge is visibility.

And visibility is where inclusion starts.

References & Further Reading

1. WebAIM Million Report 2026. Analysis of the accessibility of the top one million homepages. https://webaim.org/projects/million/

2. W3C Web Content Accessibility Guidelines (WCAG) 2.2. https://www.w3.org/TR/WCAG22/

3. W3C Media Accessibility User Requirements. https://www.w3.org/WAI/media/av/

4. United Nations Convention on the Rights of Persons with Disabilities (UNCRPD), Articles 9 and 21. https://www.un.org/development/desa/disabilities/convention-on-the-rights-of-persons-with-disabilities.html

5. Equality Act 2010 (United Kingdom). https://www.legislation.gov.uk/ukpga/2010/15/contents

6. Ofcom Accessibility Guidance on Subtitling, Audio Description and Signing. https://www.ofcom.org.uk

7. British Sign Language Act 2022. https://www.legislation.gov.uk/ukpga/2022/34/enacted

8. Author's Note: The concept of sign language visibility within accessibility ecosystems discussed in this article reflects observations from current accessibility practice and highlights the lack of established international benchmarks measuring sign language presence across websites, digital services, public information systems, and communication platforms.