Accessible Watching with Ales Player: Subtitles, Audio Description and Access Settings
We explain with practical examples how to enable subtitles, audio description, screen reader and access settings based on user profile in Ales Player, as well as packaging and testing steps for content providers.
Introduction
Providing a viewing experience that is accessible to everyone is important not only for compliance but also for user satisfaction and legal requirements. In this guide, you will find concrete steps, preferred file formats, platform-specific settings and testing checklist to meet the accessibility needs of Ales Player users and content providers.
Priorities in accessibility — what should you implement and why?
- Selectable captions/closed captions — for hard-of-hearing viewers.
- Audio description — conveying important visual elements with sound for the visually impaired.
- Screen reader and remote control navigation — voice/button control instead of visual interface
- Persistent user preferences — storing preferences (subtitle, audio, font size) in each user's profile.
Ales Player manages many subtitles and audio tracks thanks to its powerful player component; You can make these preferences permanent with the interface and user profiles (Powerful Player, Profiles and Kids Mode).
Packaging for content providers: which assets should you include?
Adding the following assets to every content increases accessibility:
Which format should you use and why? (Short table)
| Format | Advantages | Disadvantages |
|---|---|---|
| WebVTT | Style support, HTML-like markup, HLS/DASH compatibility | Limited support on very old platforms |
| TTML (IMSC) | Rich style and positioning, preferred in professional publications | Complex, limited on some clients |
| SRT | Simple, broad support, easy edit | No style, exact time synchronization may be required |
| In-band CEA-608/708 | Broadcast compatible; True in HLS/DVB scenarios | Segment packaging complexity can be difficult to migrate |
Note: Ales Player supports sidecar formats such as WebVTT/TTML/SRT, allowing the user to select subtitles from the interface.
User side in Ales Player: how to set preferences?
The following steps are generally valid for both mobile and TV/desktop; Platform-specific short notes come later.
Platform-specific accessibility tips
Mobile (iOS/Android)
- Enable system screen readers (VoiceOver / TalkBack). Ales Player is designed to deliver basic focus and tag information; navigation elements should be marked with accessible tags (Mobile App (iOS/Android)).
- Provide the option to increase subtitle size within the app; Readability on mobile screens is critical.
Android TV & webOS
- Provide large, focusable buttons for remote control navigation. For webOS users, compatibility with LG's system features such as 'Voice Guidance' should be tested (LG webOS TV App).
- Make subtitles and description information visible via EPG in live broadcasts; Closed captioning automation becomes important in live scenarios (Live TV and EPG).
Windows & Desktop
- Support keyboard shortcuts and high contrast mode; Check out focus management for screen reader users.
- For non-mouse use, make sure the menus are accessible logically and in order.
Practical advice for application developers and publishers
- Serve the audio description as a separate AAC/AC-3 track and clearly mark it with metadata (e.g. "en - Audio Description").
- If you are using WebVTT, add styling (contrast, font-width) suggestions; thus providing better visibility based on player user settings.
- Specify accessibility metadata in MPD/manifest (language and role tags via DASH/HLS manifests).
- Automated tests: add an accessibility check step to your content pipeline (subtitle timing, missing description, language tags).
Test and verification checklist (short)
- Are the subtitles timed correctly (±250 ms tolerance)?
- Is the subtitle visual contrast close to WCAG recommendations (>=4.5:1 recommended)?
- Does the audio description adequately cover the available and visual information?
- Can the player be controlled with a screen reader (play/pause, subtitle selection, audio track)?
- Does preference saving and restoring work in different profiles (Profiles and Kids Mode, Continue Where You Left Off).
Sample scenario: VOD packaging steps
Performance notes for publisher
Serving subtitles and audio tracks as side files imposes little bandwidth overhead; however, in-band embedded subtitles (CEA) can increase packet size and require segment processing. Monitor Ales Player's playback/scrolling performance and memory usage while testing.
Conclusion and recommendations
Accessibility is an integral part of content quality. Thanks to its powerful playback capabilities, Ales Player supports subtitles, audio description and user preferences; Packaging content providers with the correct format and metadata significantly improves the experience. In summary:
- Preferred subtitle format: WebVTT/TTML (SRT fallback).
- Present the audio description as a separate, clearly labeled audio track.
- Store access preferences in user profiles and map to 'pick up where you left off' (Pick up where you left off).
- Run platform tests (mobile, webOS, Android TV, Windows) with screen readers and remote control and verify interface focus management.
Suggestion for getting started: first select a pilot piece of content in your existing VOD catalogue, add WebVTT subtitles and an audio description track; Test in Ales Player, collect feedback, and scale your packaging process based on that feedback. For more technical information, see the player features section: Powerful Player.
Useful links
- Profiles and preference storage: Profiles and Kids Mode
- Continue watching where you left off: Continue where you left off
- Mobile app access settings: Mobile App (iOS/Android)
- Compatibility for LG webOS platform: LG webOS TV App
Frequently Asked Questions
How do I make subtitle default permanent in Ales Player?
You can save subtitle preferences for each profile. Once you choose your preferred language and font size in your profile settings, Ales Player stores these preferences between sessions.
How should audio description be presented?
The audio description should be packaged as a separate audio channel from the main audio track and clearly marked as 'audio description' in the manifest or metadata. Users should be able to select this track from the player.
Which subtitle format should I choose?
For professional broadcasts, WebVTT or TTML is recommended; Provides styling and positioning support. SRT can be used as a backup due to simplicity.
How do subtitles and descriptions work in live broadcasts?
Live broadcasts can use in-band captioning (e.g. CEA-608/708) or low-latency WebVTT segments. Displaying subtitle presence information via EPG improves user experience.
How can I test the Ales Player interface with a screen reader?
Enable the platform's screen reader and test basic flow controls (play/pause, subtitle selection, audio track) with the keyboard or remote control. Make sure the focus order is logical and consistent.