- Podcasts are exploding in popularity. And for good reason. People are getting great content in an audio format that they can take with them and listen to on their commute, on longer trips, or even just while doing things around the house. They're a great format unless you can't hear them. In that case, you need an alternative format for the audio. If you can't hear, the audio file is of no use to you. You need the transcript of the podcast. If you're watching videos, you need captions to get all the details of the video that are contained in the audio portion of the video.
Dialogue, narration, and even sound effects that are important to the video's meaning. What's the functional need here? A person that is deaf or hard of hearing, needs to have a text representation of all the things that are contained in the audio format. When we provide captions on a video, we almost always provide a transcript as well. Why? The reality is that providing captions means that the person has to watch the video in real time to get all the details of the content. But with a transcript, the person can get at all the content without being time-bound to watching the video.
They can skim the content of a transcript to know whether or not the video will solve their problem. They can read the transcript quicker than watching the video's captions in real time. This functional need for flexibility in terms of how content is consumed is useful not only to people that are deaf or hard of hearing, but it's actually kind of good for everyone. It's just good design.
- What is accessibility?
- Managing flow
- Ensuring proximity in your design
- Understanding how screen readers and voice recognition programs work
- Designing for hearing, vision, mobility, and cognitive issues
- Considering accessibility in layout
- Integrating accessibility into your content strategy