E-mail List Archives

Re: Video Transcript Question (Bump)

for

From: Ryan E. Benson
Date: Nov 23, 2014 7:00PM


I somewhat disagree with karl's approach. While headings will give it
structure, but if the answers are short, that could mean every other line
or so being a heading. This could lead them lose their value in some
people's eyes. What would you think if you opened up a 2-3 page doc with 20
headings?

Now if the interview had topic break-points or long answers (2+
paragraphs), I would recommend using headings.

I would agree with John with HTML vs PDF, unless you know that most of your
users will read the document when they don't have the internet. I haven't
done testing with Word 2013, but even though there is a way to create an
accessible PDF option in Word, there are false positives that can occur.

--
Ryan E. Benson

On Sun, Nov 23, 2014 at 4:19 PM, L Snider < <EMAIL REMOVED> > wrote:

> Hi John,
>
> Yes, good reminders and the link text example was a good one. The Word
> documents will be made into PDF documents, so people can download them. My
> feeling was always that if you create an accessible Word>PDF that it was
> better than an HTML page as one can download it and read it when they like
> (not having to be on the net).
>
> I would be curious to hear your view, and others, on PDF versus HTML (oh
> and for forms, HTML is the way to go, not the PDF in my view).
>
> Cheers
>
> Lisa
>
> On Sat, Nov 22, 2014 at 12:58 PM, John Foliot < <EMAIL REMOVED> > wrote:
>
> > Hi Lisa,
> >
> >
> >
> > Overall, I agree with Karl's recommendation, while at the same time
> > pointing
> > out a few things (that hopefully others might learn from too):
> >
> >
> >
> > 1) Providing a transcript is more than a "nice to have" (in case others
> > might start thinking that) - it is in fact often a requirement for WCAG
> AA
> > Compliance:
> >
> >
> >
> > 1.2.3 Audio Description or Media Alternative (Prerecorded): An
> > alternative for time-based media or audio description of the prerecorded
> > video content is provided for synchronized media, except when the media
> is
> > a
> > media alternative for text and is clearly labeled as such. (Level A)
> >
> >
> >
> > ...where the transcript is the 'alternative' to the audio-description.
> (The
> > audio description piece of course being a AA requirement:
> >
> > 1.2.5 Audio Description (Prerecorded): Audio description is
> provided
> > for all prerecorded video content in synchronized media. (Level AA))
> >
> >
> >
> >
> >
> >
> >
> > 2) You mentioned having a transcript in Word. While obviously we want to
> > avoid formats that may introduce their own issues (i.e. user does not
> have
> > MS Office), there are examples of .rtf and .pdf transcripts that are
> > provided for download, which technically meet the WCAG Requirement, so
> > providing the transcript in an alternative format is not forbidden.
> >
> >
> >
> > However, as always, HTML is the preferred format for interoperability.
> > Semantically structured HTML (aka POSH - Plain Old Semantic HTML) is
> still
> > the best :) Karl's suggestion of using <h>headings is one that I would
> > also
> > recommend, although depending on the content I might also look at the
> > viability of definition lists:
> >
> > <dl>
> > <dt>Question 1</dt>
> >
> > <dd>Response to question 1</dd>
> >
> > <dt>Question 2</dt>
> >
> > <dd>Response to question 2</dd>
> >
> > <dt>Question 3</dt>
> >
> > <dd>Response to question 3</dd>
> >
> > </dl>
> >
> >
> >
> > 3) Currently HTML5 lacks a programmatic way of *directly linking* a
> > transcript to a video, which can be problematic, especially if a web page
> > contains more than one video.
> >
> >
> >
> > While this is a known issue (and it is being worked on now), I highly
> > recommend that the link text for your transcript be well labeled; i.e.
> > avoid
> > this:
> >
> > <a href="">transcript</a>
> >
> >
> >
> > .in favor of either:
> >
> >
> >
> > <a href="">Transcript for the XYZ Video</a> [explicit, clear link text]
> >
> > or
> >
> > <a href="" aria-label="Transcript for the XYZ Video ">transcript</a>
> >
> >
> >
> > .although the second solution is only viable for users with Assistive
> > Technology.
> >
> >
> >
> >
> >
> > FWIW.
> >
> >
> >
> > JF
> >
> > ------------------------------
> >
> > John Foliot
> > Web Accessibility Specialist
> > W3C Invited Expert - Accessibility
> >
> > Co-Founder, Open Web Camp
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > -----Original Message-----
> >
> > > From: <EMAIL REMOVED> [mailto:webaim-forum-
> >
> > > <EMAIL REMOVED> ] On Behalf Of L Snider
> >
> > > Sent: Saturday, November 22, 2014 10:20 AM
> >
> > > To: WebAIM Discussion List
> >
> > > Subject: Re: [WebAIM] Video Transcript Question (Bump)
> >
> > >
> >
> > > Hi Karl,
> >
> > >
> >
> > > Thanks so much. That is how I was thinking of approaching it, with
> >
> > > headings, so that a screen reader user could list them and go to a
> >
> > > particular one. Oh and this transcript will be made accessible for
> >
> > > people with all disabilities, but it was the screen reader part that I
> >
> > > was trying to work out-and headings are great!
> >
> > >
> >
> > > Thanks again, appreciate it!
> >
> > >
> >
> > > Cheers
> >
> > >
> >
> > > Lisa
> >
> > >
> >
> > > On Fri, Nov 21, 2014 at 7:10 AM, Karl Groves <
> > <mailto: <EMAIL REMOVED> > <EMAIL REMOVED> >
> >
> > > wrote:
> >
> > >
> >
> > > > Lisa,
> >
> > > >
> >
> > > > You should treat the transcript like any other content, really.
> >
> > > > Without knowing the exact nature of the videos, it is hard to
> >
> > > > recommend an exact structure. For instance, you mention that the
> >
> > > text
> >
> > > > is "...just Q and A over and over again". Based on that description,
> >
> > > > it might make sense for each question to be a heading, under which is
> >
> > > > the answer, like so:
> >
> > > >
> >
> > > > <h2>Question: ______</h2>
> >
> > > > <p>text of answer</p>
> >
> > > >
> >
> > > > Another idea, especially if the interview is well structured, might
> >
> > > be
> >
> > > > something like:
> >
> > > >
> >
> > > > <h2>Topic: (time-start to time-end)</h2>
> >
> > > > <h3>Question: ______</h3>
> >
> > > > <p>text of answer</p>
> >
> > > >
> >
> > > >
> >
> > > > Keep in mind the audiences of a transcript: They may be people who
> >
> > > are
> >
> > > > hard of hearing, obviously, but might also be screen reader users or
> >
> > > > even users who have cognitive impairments. A well-structured
> >
> > > > transcript can help all of those users. For users who are not
> >
> > > visually
> >
> > > > impaired it might even make sense to include images, such as screen
> >
> > > > captures of the interview, especially if visual aids exist in the
> >
> > > > video.
> >
> > > >
> >
> > > >
> >
> > > > On Wed, Nov 19, 2014 at 1:58 PM, L Snider < <mailto:
> <EMAIL REMOVED> >
> > <EMAIL REMOVED> > wrote:
> >
> > > > > Hi All,
> >
> > > > >
> >
> > > > > I am trying this one again, as I was having some major email issues
> >
> > > > > when
> >
> > > > I
> >
> > > > > sent this the first time!
> >
> > > > >
> >
> > > > > For videos, I provide CC or open captioning, but I also like to
> >
> > > > > include a text transcript of the content as well. The content of
> >
> > > the
> >
> > > > > videos is usually interviews, so there are a lot of questions and
> >
> > > > > answers, and sometimes multiple people talking.
> >
> > > > >
> >
> > > > > I have done a lot of research and have not yet found a source that
> >
> > > > > talks about the best way to make that text transcript accessible
> >
> > > > > (other than to have one-which I have always done).
> >
> > > > >
> >
> > > > > For example, the documents would be created in Word and would
> >
> > > > > usually
> >
> > > > only
> >
> > > > > have a couple of headings at the top, but the rest of the text
> >
> > > would
> >
> > > > > just be Q and A over and over again...Does anyone have a good
> >
> > > > > example of an accessible text transcript or an online source that
> >
> > > > > talks about this
> >
> > > > aspect?
> >
> > > > >
> >
> > > > > Thanks in advance,
> >
> > > > >
> >
> > > > > Lisa
> >
> > > > > > >
> > > > > > > http://list.webaim.org/ Address
> >
> > > > > list messages to <mailto: <EMAIL REMOVED> >
> > <EMAIL REMOVED>
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > > --
> >
> > > >
> >
> > > > Karl Groves
> >
> > > > <http://www.karlgroves.com>; www.karlgroves.com
> >
> > > > @karlgroves
> >
> > > > <http://www.linkedin.com/in/karlgroves>;
> > http://www.linkedin.com/in/karlgroves
> >
> > > > Phone: +1 410.541.6829
> >
> > > >
> >
> > > > Modern Web Toolsets and Accessibility
> >
> > > > <https://www.youtube.com/watch?v=_uq6Db47-Ks>
> > https://www.youtube.com/watch?v=_uq6Db47-Ks
> >
> > > >
> >
> > > > <http://www.tenon.io>; www.tenon.io
> >
> > > > > >
> > > > > > http://list.webaim.org/ Address
> >
> > > > list messages to <mailto: <EMAIL REMOVED> >
> > <EMAIL REMOVED>
> >
> > > >
> >
> > > > >
> > > > > http://list.webaim.org/ > >
> > > messages to <mailto: <EMAIL REMOVED> >
> > <EMAIL REMOVED>
> >
> > > > > > > >
> > > >