Apple TV is adding sign language interpretation to selected films and programmes. On supported titles, it is switched on within the usual player, much like captions or audio description.
That sounds simple. It is also the bit that matters.
Too often, accessibility is treated as a separate version of the service. The main product goes one way, while the accessible experience sits behind another link, in another player, or on a page you only find if you already know it exists.
Apple’s approach is more useful. The title remains the title. The viewer chooses how they want to experience it.
The separate version problem
I have spent enough time looking at accessibility features to know that availability and usability are not the same thing.
A service can proudly claim that it has captions, audio description, a keyboard-friendly journey or an alternative format. Yet the person who needs it may still have to hunt for it, work out whether it applies to the item they want, and take a different route through the product.
That creates friction before the experience has even begun.
It also sends an unhelpful message. The default journey was designed for everyone else. Yours has been added later.
Accessibility should offer choice, not a detour.
Apple’s new feature starts with Being Heumann on 13 November, with American Sign Language and British Sign Language also available for F1. More titles, including Way of the Warrior Kid and Greyhound, are due to follow later in the year.
The early catalogue is limited, as it will be for any feature that needs proper planning and skilled people behind it. But the product decision is the interesting part. The interpreter appears within the same viewing experience instead of being packaged as a separate film for a separate audience.
That is a better baseline.
Make accessibility discoverable
There is another good detail in Apple’s announcement. It is not only adding the feature to playback. It is labelling supported titles, listing available sign languages alongside the usual language information, and making those titles searchable.
This is where a lot of accessibility work goes wrong.
A feature can be well built and still be effectively invisible. If someone cannot discover it in search, filters, title information or settings, it may as well not exist. You should not need insider knowledge to find out whether a product will work for you.
Think about the questions your customers have before they buy, subscribe or start a task:
- Can I tell whether this will work for me?
- Can I find the feature without asking customer support?
- Is it described in language I understand?
- Will the same information be available when I move between devices?
- Can I make the choice independently?
Those questions apply far beyond streaming.
If your organisation has invested in accessible content, an accessible website or assistive technology support, make it visible. Put it where people make decisions. Make it work with a screen reader. Use clear labels rather than internal jargon.
The experience around an accessibility feature is part of the feature.
Sign language is not just another subtitle
It would be easy to describe this as another captioning option. It is not.
Captions, subtitles and sign language interpretation each meet different needs. They can work well together, but one is not a replacement for the others.
British Sign Language and American Sign Language are languages in their own right. They are not simply English rendered as hand movements. That is why Apple’s decision to work with Directors of Artistic Sign Language matters. It has said it is not using AI-generated interpreters, reflecting what it has heard from the Deaf community.
There is a useful lesson here for anyone building accessibility features during the current rush towards generative AI.
The question should not be whether a tool can produce something that looks convincing in a demonstration. The question is whether it works for the people who will rely on it in real life.
That means involving people with disabilities early, paying for their expertise, and being prepared to hear that the clever technical shortcut is not the best solution.
Technology can help. It does not remove the need for judgement.
Build it into the operating model
Accessibility announcements are easy. Consistency is the harder part.
A feature like sign language interpretation does not appear by accident. It needs to be considered when content is commissioned or acquired, included in the production workflow, labelled correctly, tested properly and supported after launch.
The same is true in every digital product.
An accessible service cannot depend on a designer spotting a problem at the last minute. It cannot rely on a supplier’s reassuring statement in a procurement questionnaire. It certainly cannot be held together by one enthusiastic accessibility champion chasing fixes after everything else has been signed off.
Accessibility has to be part of the way the organisation works.
For streaming, that includes content requirements, metadata, player controls, search, customer support and quality assurance. For a website or app, it includes research, requirements, design, development, content, testing and governance.
Standards such as the Web Content Accessibility Guidelines give us an essential common language and a solid baseline. They do not guarantee that somebody can find a feature, understand it and complete the thing they came to do independently.
That distinction matters.
Conformance is valuable. Real outcomes are the point.
Inclusion is visible in the product
There is a commercial argument here too, although it should not be difficult to understand.
Entertainment services compete for subscriptions, attention and loyalty. If someone cannot reliably find content that works for them, they have been given a reason to spend their time and money elsewhere. Families notice when one person is excluded from something that is supposed to be shared.
When accessibility is thoughtfully built into the main experience, customers see that their needs were anticipated. That builds trust.
It also reduces rework. Clear requirements, consistent metadata and properly designed controls make future releases easier than trying to retrofit an answer to every new product or piece of content.
Apple TV’s sign language interpretation feature will not solve every access problem in streaming. The catalogue is small at launch and the important test will be whether support grows in a sustained, predictable way.
But it gets the central idea right.
Do not build a side door for accessibility if the main entrance can work for everyone.

/Passle/60211dc9e5416a0c14bc63d4/SearchServiceImages/2026-11-02-15-42-49-331-6ae8af793614ac951d548b49.jpg)
/Passle/60211dc9e5416a0c14bc63d4/SearchServiceImages/2026-10-29-14-42-40-536-6ae35b60633ad0fc412c84f5.jpg)
/Passle/60211dc9e5416a0c14bc63d4/SearchServiceImages/2026-11-03-11-40-24-233-6ae9c828e23a6a6f7b5c9f37.jpg)




