[Athen] Inaccessible emails

White, Phillip Burton WHITEPH15 at ECU.EDU
Thu May 4 12:44:08 PDT 2017


Anyone have any examples they can email me. Campus events are usually good places to start.

I'm putting together a presentation about the importance of accessible emails. Not a prime topic this late in the era, but still important.

Please email me an good examples of inaccessible emails. It's always best to have the real thing from the university, and not something from the internet. I'll be displaying these as examples in my discussion of how to build accessible campus email communications.

Thanks

Phillip White
ITCS Accessibility Consultant
Whiteph15 at ecu.edu

-----Original Message-----
From: athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] On Behalf Of athen-list-request at mailman13.u.washington.edu
Sent: Thursday, May 04, 2017 3:00 PM
To: athen-list at u.washington.edu
Subject: [BULK] athen-list Digest, Vol 136, Issue 4

Send athen-list mailing list submissions to
athen-list at u.washington.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman13.u.washington.edu/mailman/listinfo/athen-list
or, via email, send a message with subject or body 'help' to
athen-list-request at mailman13.u.washington.edu

You can reach the person managing the list at
athen-list-owner at mailman13.u.washington.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of athen-list digest..."


Today's Topics:

1. Re: correct terminology -- audio description or video
description (Leyna Bencomo)
2. Re: correct terminology -- audio description or video
description (E.A. Draffan)
3. Re: correct terminology -- audio description or video
description (Terrill Thompson)
4. Re: Distilling WCAG Guidelines and 508 Criteria by Role
(Zirkle, Kara)
5. FW: athen-list Digest, Vol 136, Issue 1 (Zach)
6. Re: correct terminology -- audio description or video
description (Jennifer Sutton)
7. Re: correct terminology -- audio description or video
description (Sheryl E. Burgstahler)


----------------------------------------------------------------------

Message: 1
Date: Wed, 3 May 2017 19:31:31 +0000
From: Leyna Bencomo <lbencomo at uccs.edu>
To: Access Technology Higher Education Network
<athen-list at u.washington.edu>
Subject: Re: [Athen] correct terminology -- audio description or video
description
Message-ID:
<BN3PR0501MB1170F4609541DF77913F5E7FAD160 at BN3PR0501MB1170.namprd05.prod.outlook.com>

Content-Type: text/plain; charset="us-ascii"

My vote is for video description...unless we used the adjectives aural and visual in which case I would vote for aural description! :) Semantics!


Leyna Bencomo
Assistive Technology Specialist
Information Technology
University of Colorado Colorado Springs
1420 Austin Bluffs Parkway, EPC 215
Colorado Springs, CO 80918
(719) 255-4202 / lbencomo at uccs.edu<mailto:lbencomo at uccs.edu>
http://www.uccs.edu/~it/
[uccs-signature-email]



From: athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] On Behalf Of steve.noble at louisville.edu
Sent: Wednesday, May 3, 2017 10:07 AM
To: Access Technology Higher Education Network <athen-list at u.washington.edu>
Subject: Re: [Athen] correct terminology -- audio description or video description


My recollection of the history is that "audio description" was indeed the original terminology, but it was initially used only at live in-person events, like a play where the description was broadcast over headphones provided to blind patrons attending the event. When the same concept was later applied to TV programming, the term for that usage was changed to "video description" to make a distinction. Thus, both terms have stuck with us over the years.




--Steve Noble
steve.noble at louisville.edu<mailto:steve.noble at louisville.edu>
502-969-3088
http://louisville.academia.edu/SteveNoble



________________________________
From: athen-list [athen-list-bounces at mailman13.u.washington.edu] on behalf of Sheryl E. Burgstahler [sherylb at uw.edu]
Sent: Wednesday, May 03, 2017 10:54 AM
To: Access Technology Higher Education Network
Subject: Re: [Athen] correct terminology -- audio description or video description
Is "video description" completely accurate?

First of all, what we are talking about is audio; the purpose of the audio is to describe content presented visually in a video presentation. This description leads me to prefer "audio description."

(grin) However, I can argue pros and cons for each terminology!!! As you can tell I have given this topic way to much attention...I know, get a life, Sheryl.

Sheryl

On May 3, 2017, at 7:02 AM, Bourne, Sarah (MASSIT) <sarah.bourne at mass.gov<mailto:sarah.bourne at mass.gov>> wrote:


Besides liking to align with the federal government terminology, I prefer "video description" because it refers to *what* is being described. "Audio description" refers to the format that description is being provided in, which leaves hanging the question of what I should call a text version of that description when needed by, for instance, someone who is deaf/blind.

Sarah E. Bourne
Director of IT Accessibility, MassIT
Commonwealth of Massachusetts
1 Ashburton Pl. rm 811 Boston MA 02108
617-626-4502
sarah.bourne at mass.gov<mailto:sarah.bourne at mass.gov>
http://www.mass.gov/MassIT<https://secure-web.cisco.com/16IiWQm0ujAG5jUkzUPmtYqIFjAbpavnMFU9HcvDCFF2dcT7s2bV2JbF6hwPmCvdefE6L40OMQhyg1uLMiLnRk7I8S_-KjuM3vTRLrPU2IFGRl4OkbEV1qldN5ci6uJc3X7ay_ake8G-u9W1eQoNp5ICDNRigsTMjv8M0qfJaRZLxhBb_pPpCuRGHacD8D1wgEz04IMiG7q3zhJItfUVHMXsQslpDSiuDE27I4rWGFqrW2pSiPJC3C4-uv_mO_NH7uW53wC1LKlWrwKhc9HDunDw9ufMzG2RZaYv6y_HS7rr-x1cA1t5WmicmXew56pJq54y3hPy09Ey7KV70_NVpm5uBkrycf-c3AqjeSi5xAyZ-BCae6qMs0U6r-wiR0JG9cXOd0veKsJHB5tDt6aFU2fG6yXNM-Gzol2tuLeylIvBCNqx5lvYmcMhi3qhqvXzJnUOJ_4uHUjU-PqazQyou9XWQFedMnMZ7znPrARgtgtc/https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__www.mass.gov_MassIT%26d%3DAwMF-g%26c%3DSgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk%26r%3D4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE%26m%3DxQ2Ye-KjGvdQVysc_D-JQ0Jqv__ePn8h5Tq1w1hz3vg%26s%3DO7WOslwAZVePK0ee6gAKYTo4QueeZi6s3ptQ0xNUDPY%26e%3D>

_______________________________________________
athen-list mailing list
athen-list at mailman13.u.washington.edu<mailto:athen-list at mailman13.u.washington.edu>
http://mailman13.u.washington.edu/mailman/listinfo/athen-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/athen-list/attachments/20170503/63a9bab3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 3598 bytes
Desc: image001.gif
URL: <http://mailman13.u.washington.edu/pipermail/athen-list/attachments/20170503/63a9bab3/attachment-0001.gif>

------------------------------

Message: 2
Date: Wed, 3 May 2017 22:14:56 +0100
From: "E.A. Draffan" <ea at emptech.info>
To: "'Access Technology Higher Education Network'"
<athen-list at u.washington.edu>
Subject: Re: [Athen] correct terminology -- audio description or video
description
Message-ID: <00cd01d2c452$50e31f30$f2a95d90$@emptech.info>
Content-Type: text/plain; charset="iso-8859-1"

I have some fears about having to have two terms as 'audio description' has
been accepted in many countries as being a way to describe what is happening
on the screen by using a sound track
http://secure-web.cisco.com/1xthWJCTk2ADxwCf3frPNd7o8o9OUORcyA2SOaZr27o__fBJyJtYEdZIAoDOc-ad3zryNNqgOkjoCEyYPIdXmr9vycOgF0VL9fNl_CoOdjHTAecVXwBNNQ0BYRi1hV1N7DdAHWwY-tah13gWBwC9lhDfdC7OOga5AG9TCbgn8h0_3UFljvocgPWKOzFLZsmnpKwvPIeMLC8-PhZJ153-txanb48OF4Tz3X6x8-gLW97yQ1ZXWCr2Dr92uvXMxhbfMdahH0T1MKkofsfWEAIOAVpFq8dJ2EqFukBuc8amcS8fZA7UhkIzpJp7aMulxQUQSXiDxL8UhRxQfR1OTqpnuSjbR0NHkKrMLtDEUWJSGpPii4SrrCWgS2N8SBDcRxhSj6uOSw8sy5I5JLexmwEctSes2n9hlBYKmeenAVfSYtsOCLXoQggiXdRwVk9p6fuFKW2o2pmELnu3iWBEn9L5WyxmSlBFYuvfcKTr5faA4jyo/http%3A%2F%2Fhub.eaccessplus.eu%2Fwiki%2FAudio_description

When I am asked for video description by YouTube it is a piece of text to
describe the video for marketing purposes.

Feb 2016 3PlayMedia talk about video descriptions being available in text
for screen reader users or as audio recordings.
http://secure-web.cisco.com/1C86CQ8qHL3n5D27SfdVURWutQL24-YIlJRGOcmr2tqzSyxVdiM7516mcqeVKofCkXwA777mveoSO5KbpRseZS5sBDu8yxdMyE1OYpnK0GOyy7vZIiZwyw3Q2A1O8d68qWZEa9z6tbSrPkUw79-LGka6jqefTJXtjgPAWVyZuzyMQ0wnTPB-FhGg1NfTiPfJcaYs0fzVbQzIDrysVxVnu2HnceKw0mgBTL17M4aTJXk0AW7TLQbaUsTV74FiaLiUZpo8PGzDB7IAOqbKtfuICo64c1kGjI9VwLZOM7Fxg4Wj_oSSqfhyLD_G9q38mKrSKFf441awnhJrp6_eIbi7gCeKofUWIxPrwBMe0dC47qSwTOiJuoXUAoqQyFv2L29NtfMhEoZQY7Bxhwr7L05KQY1ppIAf0KeKRStXwpqFm-c6ZFk1jGMu5eHBFH6Yh3RD5EFDDXZEhMznsyKQzFgzOSUdWnDqf1i1NWN3Ogo9RcFo/http%3A%2F%2Fwww.3playmedia.com%2F2016%2F02%2F01%2Fwhy-a-transcript-is-not-enough-to-make-
your-videos-compliant-with-accessibility-law/

But yes.... several US organisations supporting those who have visual
impairments and wikipedia say video descriptions are the same as audio
descriptions, although the CVAA description does not appear to be very
explicit
https://www.fcc.gov/consumers/guides/21st-century-communications-and-video-a
ccessibility-act-cvaa and in 3PlayMedia's brief about the CVAA - they do
not touch on the subject. However, go to neospeech TTS suppliers
http://secure-web.cisco.com/1BI-6OHxufXkJvwp_T3VVSeKj5y7zLfB1XjvVM_AWqpbGsKoHmbn3hgcQt6aetnFdp7LtVWK5qCd--IWhKWip0gt2wqlHWc3nkQpPODIaCo7V7YWbkyNOk2lVcM2WY_NdYKfEn0nSDssubW0PThG3kq8dq8zH8VqhPsRWRmK6RVHs8v7t01TOgzMQjLejlIJqo9KUqzH2i0H7fASFCZkvv1738IFG1k4F8q8viHdJTSE5RalTn9K3fyX44d73TScJdA_ksd_GlIH7QF05HhRXFAEYaekeIup4cck0NGfu5SMq7R8w-6-rXihzyWmqochKl89ReYVeZylBOZ516GGmJCYVRoLAQp8KJEfD3I5ApyuTbORn4UdO-_AwVmoDRdHSoOjlNFthtQ_8QdbooWk_ZNsa4h4MH3w7yhVe8atuCw-II1oAEx7-RAJfkYdhWINNPHDdiT7GveXrGzg2OdzvSCJMHhAZWIkP-kE28UAP6vc/http%3A%2F%2Fblog.neospeech.com%2Ftitle-2-of-cvaa-video-programming%2F and yes text
to speech can be used! So can one assume that a text version for video
descriptions is allowed as long as it is accessible to AT?

Best wishes
E.A.

Mrs E.A. Draffan
WAIS, ECS , University of Southampton
Mobile +44 (0)7976 289103
http://access.ecs.soton.ac.uk
UK AAATE rep?http://secure-web.cisco.com/1ndCtVe-H-SNcPsrlCZVU7OO0BF-41VGSKUHn327YM-4Eb8Uy1sZjcu9Ly_bRKVGpF9IuppSMr6ycDgPUudumJ3OLbVCG8wOn81xTg5vSG4Axijnrn7G-qukAZ2Vfs811wvMrFr3cgPbo0ELf8ofgXuwD0JzBXCRxFUtgmPpsECgcnFp6zvMKe_fV6AOKiCXzyG0mhWjhn_hBcPmAeFYmneirwDEYDmOjI7xyjLZykHZBJ9GEV0z1SPTzIH45ddonFGUfrkD_1OKFtRV50MtYqsfFf6gfJsKaipIXjZyelRl8CI_82CCcYHYw-aGCl9DGDoHlJIo1u-i1f9aTdBQh3JhD8KiSTSHiETgKSogpXuToJg0luuT79teHLWrg2BbbrErf17nLm6DCX7FhTr22J45Y1iMMDlUxSGehiYNtm0SFtn41AUGwn2pmW8zwH9pgI9xjqipqXFf9DdtxH8rW0TtBRsK4H1OYgDI4IIHzCNc/http%3A%2F%2Fwww.aaate.net%2F




-----Original Message-----
From: athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] On
Behalf Of Jennifer Sutton
Sent: 03 May 2017 15:01
To: Access Technology Higher Education Network <athen-list at u.washington.edu>
Subject: Re: [Athen] correct terminology -- audio description or video
description

Oh, certainly. I'm very aware of audience considerations while
simultaneously assuring accuracy, such as in legal contexts.


Jennifer



On 5/3/2017 6:57 AM, Sheryl E. Burgstahler wrote:

> Jennifer,

> I agree that either term works. Having said that, those of us speaking to

newbies on the topic need to make sure to explain what we mean and share the
alternative wording in order to minimize confusion.

> Sheryl

>

> On May 3, 2017, at 6:47 AM, Jennifer Sutton <jsuttondc at gmail.com> wrote:

>

>> Thanks, all, for your responses.

>>

>> I did reach out to someone who used to be at WGBH, and that response

dovetails with what you say here, Steve.

>>

>>

>> My ultimate take-away, as in so many things accessibility-related is that

which term one uses will depend on context.

>>

>>

>> I don't think it is a matter of personal preference, at least in some

cases.

>>

>>

>> As I understand it (and suspected when I asked the question), there's a

lot of history and politics behind why there are two terms (and I don't just
mean U.S. government politics).

>>

>>

>> As I understand it, when referring to CVAA, I think "video description"

may be the preferred term.

>>

>>

>> My concern with relying on the W3C is that they may be less aware of the

U.S. situation, and in the context of some of what I am doing, that will
matter.

>>

>>

>> As in so many things, language does matter, and I'm glad I understand the

ramifications of the two terms.

>>

>>

>> Again, thanks to all for your input.

>>

>>

>> Best,

>>

>> Jennifer

>>

>>

>>

>> On 5/3/2017 5:51 AM, steve.noble at louisville.edu wrote:

>>> Hi Jennifer,

>>>

>>> The terms are now interchangeable, but the federal government prefers

the term "video description" and that is the term typically used by Congress
and the FCC. For instance, in 47 CFR 79.3 "Video description of video
programming," the definition is given:

>>> "(3) Video description. The insertion of audio narrated descriptions of

a television program?s key visual elements into natural pauses between the
program?s dialogue." [see
https://www.gpo.gov/fdsys/pkg/CFR-2011-title47-vol4/pdf/CFR-2011-title47-vol
4-sec79-3.pdf]

>>> The federal government's use of the term "video description" dates back

to the early 1990s, and perhaps before. You may want to reach out to Barry
Cronin for the real scoop, as he was one of the original developers at WGBH.
If you need his contact information, just let me know. In the mean time,
here's a nice history for you:
http://files.eric.ed.gov/fulltext/EJ1114571.pdf

>>>

>>> Hope that helps,

>>> --Steve Noble

>>> steve.noble at louisville.edu

>>> 502-969-3088

>>> http://louisville.academia.edu/SteveNoble

>>>

>>>

>>> ________________________________________

>>> From: athen-list [athen-list-bounces at mailman13.u.washington.edu] on

behalf of Jennifer Sutton [jsuttondc at gmail.com]

>>> Sent: Tuesday, May 02, 2017 10:14 PM

>>> To: Access Technology Higher Education Network

>>> Subject: [Athen] correct terminology -- audio description or video

description

>>>

>>> Greetings, ATHEN list folks (along with a few others I've bcc-ed):

>>>

>>>

>>> I'm sorting through my resources, and I'm confused about what the

>>> correct term is for adding audio to videos to help explain visual

>>> elements for blind people.

>>>

>>>

>>> I know that we initially called it "audio description," but I had in

>>> mind that the term was shifting to "video description" since that

>>> describes better what it is, at least to a degree.

>>>

>>>

>>> At the same time, I still see current articles and sites calling it

>>> "audio description."

>>>

>>>

>>> Does anyone have the definitive "scoop?"

>>>

>>>

>>> I'd welcome links/citations in support of responses.

>>>

>>>

>>> Is this, perhaps, one of these situations where we might *like* the term

>>> to change, but the term "audio description" is so prevalent that

>>> progress is slow?

>>>

>>>

>>> Are there legal ramifications, i.e. maybe some state laws refer to it in

>>> different ways?

>>>

>>>

>>> Thanks in advance. I'm updating some things, and I'd like to get it

right.

>>>

>>>

>>> If it doesn't matter/they're now considered simply synonymous, I'd like

>>> to know that, too.

>>>

>>>

>>> Best,

>>>

>>> Jennifer

>>>

>>> _______________________________________________

>>> athen-list mailing list

>>> athen-list at mailman13.u.washington.edu

>>>

https://secure-web.cisco.com/16VxT7W4GKKDS9gajkWOB-EhN9FAg_Sp64adePxQT9BFueG_WNdL-34ltLiqmehz3fPNH84cnRzA4hJ8KGYgC9X0o37v92Q1xXjpUXiGVgLM-TDX0JF1Ofgl78tIzDPGhujs_1-Ey6cUF0TYYeyeHEWUgl7p-Yrg5Q2Ni6R-Df-6SnxzWZ9GgPzJz2zfwW0jTdHsozMkcD1trgg80h-qWl7UF-WZAihd2RrYhOFzBoyWkZ6s6kOKQIzd-vSj99GP4fOf_14W5uSDh0zMHFWVXhnS_lbnFMwzgqKjUCIDHJoiWD5F56WbcdQ1MjYwtoo1hI7_j_bO0Vn6Osr5qMRleotulTO9faThxyPlhItkG9rapdHVupMg_3fJAEMMpD6DvnoB3lHbULhIKLvctSfYy2ISM7dBK2Hf5FDXBIpMCFqf8AjFgws74z9eej-JixehDI8jjIv9jKFWskwYLK_vDf_n0RS44kAxuZAX_HRmMSmE/https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__mailman13.u.washington.e
du_mailman_listinfo_athen-2Dlist&d=AwICAg&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1S
O3AJ2bNrHlk&r=4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE&m=JW7m48F06P_3qz8y
hj_qyefoBPL6u7prODM_zYMvl60&s=eJLpz-kupRMcVVm1md89p-6zyP_nKtvrmQNSmNc1Jo0&e=

>>> _______________________________________________

>>> athen-list mailing list

>>> athen-list at mailman13.u.washington.edu

>>> http://mailman13.u.washington.edu/mailman/listinfo/athen-list

>> _______________________________________________

>> athen-list mailing list

>> athen-list at mailman13.u.washington.edu

>> http://mailman13.u.washington.edu/mailman/listinfo/athen-list

> _______________________________________________

> athen-list mailing list

> athen-list at mailman13.u.washington.edu

> http://mailman13.u.washington.edu/mailman/listinfo/athen-list


_______________________________________________
athen-list mailing list
athen-list at mailman13.u.washington.edu
http://mailman13.u.washington.edu/mailman/listinfo/athen-list



------------------------------

Message: 3
Date: Thu, 4 May 2017 06:16:21 -0700
From: Terrill Thompson <tft at uw.edu>
To: Access Technology Higher Education Network
<athen-list at u.washington.edu>
Subject: Re: [Athen] correct terminology -- audio description or video
description
Message-ID:
<CAC7M+wr28KMUMnuxGp5EPWfW3+QVLgEjP6rSGDnzbWfsOMMnxA at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

To the the extent that large corporations influence our society and
language, Netflix uses "audio description":
https://help.netflix.com/en/node/25079

Also, WCAG 2.0 uses "audio description":
https://secure-web.cisco.com/1JXDE-cjfJSYeff029Xob-lnvCcd9rCo9UZvJj0U24016YDeg3FxgkRGSc_fqSYm6f88zZSEuSqpAYbNGHvPTxPwfTKQYWJ6EMKq5N9jl3lNOjP8Nlg4smbGtLH1MNC6wLAFtbvht29af7fm5IfZABLV9vuYZjlIGaDKPMWj3ZKvXHD84oSHoarYCMxJQJcobXCadEQolByJSzgVQUVflz06XJA8bv12VCroR1lyUjEua7RSGKnMLnvVP9jNQfNZTVyDWXjUJgVYGgX-PIl5c1WSeGrvnTIsAN-Fi9N86ZA1YVkN5ObT5_2x5WMqJIizDrOqxmLqIwLUxDpYoSYKyGbwyDlf8Ofn2MzLJW3di7oom-t7ZXqgo7ahBFHrQ4RH3tiaSnSLMYF4_4_L1QodgkfjSSyAK_Y7c0wBLicPlsWNGE8eVF4DDA1eVEEnTTfNcORIRGrZldY83c8QNnxpOzQ/https%3A%2F%2Fwww.w3.org%2FTR%2FWCAG20%2F

Specific relevant WCAG 2.0 success criteria are:

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)

1.2.5 Audio Description (Prerecorded): Audio description is provided for
all prerecorded video content in synchronized media. (Level AA)

1.2.7 Extended Audio Description (Prerecorded): Where pauses in foreground
audio are insufficient to allow audio descriptions to convey the sense of
the video, extended audio description is provided for all prerecorded video
content in synchronized media. (Level AAA)

Personally, I prefer "descriptive narration" as it avoids the confusion
over "audio" vs "video". Unfortunately "descriptive narration" doesn't seem
to be used in any official capacity, so I only use that term if I'm
referring to it casually. Otherwise I use "audio description", mostly to be
consistent with WCAG. Also, once I've established and defined what exactly
I'm talking about, I will often drop the adjective and refer to it simply
as "description" in subsequent uses.

Regards,
Terrill






---
Terrill Thompson
Technology Accessibility Specialist
DO-IT, Accessible Technology Services
UW Information Technology
University of Washington
tft at uw.edu

On Wed, May 3, 2017 at 2:14 PM, E.A. Draffan <ea at emptech.info> wrote:


> I have some fears about having to have two terms as 'audio description' has

> been accepted in many countries as being a way to describe what is

> happening

> on the screen by using a sound track

> http://secure-web.cisco.com/1xthWJCTk2ADxwCf3frPNd7o8o9OUORcyA2SOaZr27o__fBJyJtYEdZIAoDOc-ad3zryNNqgOkjoCEyYPIdXmr9vycOgF0VL9fNl_CoOdjHTAecVXwBNNQ0BYRi1hV1N7DdAHWwY-tah13gWBwC9lhDfdC7OOga5AG9TCbgn8h0_3UFljvocgPWKOzFLZsmnpKwvPIeMLC8-PhZJ153-txanb48OF4Tz3X6x8-gLW97yQ1ZXWCr2Dr92uvXMxhbfMdahH0T1MKkofsfWEAIOAVpFq8dJ2EqFukBuc8amcS8fZA7UhkIzpJp7aMulxQUQSXiDxL8UhRxQfR1OTqpnuSjbR0NHkKrMLtDEUWJSGpPii4SrrCWgS2N8SBDcRxhSj6uOSw8sy5I5JLexmwEctSes2n9hlBYKmeenAVfSYtsOCLXoQggiXdRwVk9p6fuFKW2o2pmELnu3iWBEn9L5WyxmSlBFYuvfcKTr5faA4jyo/http%3A%2F%2Fhub.eaccessplus.eu%2Fwiki%2FAudio_description

>

> When I am asked for video description by YouTube it is a piece of text to

> describe the video for marketing purposes.

>

> Feb 2016 3PlayMedia talk about video descriptions being available in text

> for screen reader users or as audio recordings.

> http://secure-web.cisco.com/1kTIiKSsnH2CUXkMzY4v7ejt8u2GwSx_E_-7X-x4hN1Fj8_IriXmMcs9oqsl9It0j7xpkKIN4JqnE4kX7QkFNOfwGNTiemlTtpAMSI3nPc1_Hci4nmp39Ex7LfSFpbw8HUnqS8jNdajvY9JNJylLj56Xe1Ivg5kFnUfK6uEp0aOXG9fD05AocPeLBZNGXNt8G2TfndWLLZA5gN6XFgj5aqBdSU5fLhV2BsSrLfBqTCeuiO1VhpZx7f1i4ToUeI1QX4JTdBfwvdpdbqwzoVgzgDzzHl1qO1YzcycsMF6-fe2B37zXKvn3YSTEmVu-D_OoVJs18Xzt981szG6YWjrYO9W6ZyWW6zaAwuBq8FzCcv-XzAegcRTksn9Wrb57elqEd5OidtHXfMGkxx8xka2rmqKXe0HyuvjTM-etKePKp5F_Qvhwr-N3GUM6SKHOU7ON69tAmdtk6eNOSNCBVvBc_zbAHrTQeBc3vO-bXcMJ7OYM/http%3A%2F%2Fwww.3playmedia.com%2F2016%2F02%2F01%2Fwhy-a-transcript-

> is-not-enough-to-make-

> your-videos-compliant-with-accessibility-law/

>

> But yes.... several US organisations supporting those who have visual

> impairments and wikipedia say video descriptions are the same as audio

> descriptions, although the CVAA description does not appear to be very

> explicit

> https://www.fcc.gov/consumers/guides/21st-century-

> communications-and-video-a

> ccessibility-act-cvaa and in 3PlayMedia's brief about the CVAA - they do

> not touch on the subject. However, go to neospeech TTS suppliers

> http://secure-web.cisco.com/1BI-6OHxufXkJvwp_T3VVSeKj5y7zLfB1XjvVM_AWqpbGsKoHmbn3hgcQt6aetnFdp7LtVWK5qCd--IWhKWip0gt2wqlHWc3nkQpPODIaCo7V7YWbkyNOk2lVcM2WY_NdYKfEn0nSDssubW0PThG3kq8dq8zH8VqhPsRWRmK6RVHs8v7t01TOgzMQjLejlIJqo9KUqzH2i0H7fASFCZkvv1738IFG1k4F8q8viHdJTSE5RalTn9K3fyX44d73TScJdA_ksd_GlIH7QF05HhRXFAEYaekeIup4cck0NGfu5SMq7R8w-6-rXihzyWmqochKl89ReYVeZylBOZ516GGmJCYVRoLAQp8KJEfD3I5ApyuTbORn4UdO-_AwVmoDRdHSoOjlNFthtQ_8QdbooWk_ZNsa4h4MH3w7yhVe8atuCw-II1oAEx7-RAJfkYdhWINNPHDdiT7GveXrGzg2OdzvSCJMHhAZWIkP-kE28UAP6vc/http%3A%2F%2Fblog.neospeech.com%2Ftitle-2-of-cvaa-video-programming%2F and yes text

> to speech can be used! So can one assume that a text version for video

> descriptions is allowed as long as it is accessible to AT?

>

> Best wishes

> E.A.

>

> Mrs E.A. Draffan

> WAIS, ECS , University of Southampton

> Mobile +44 (0)7976 289103

> http://access.ecs.soton.ac.uk

> UK AAATE rep http://secure-web.cisco.com/1ndCtVe-H-SNcPsrlCZVU7OO0BF-41VGSKUHn327YM-4Eb8Uy1sZjcu9Ly_bRKVGpF9IuppSMr6ycDgPUudumJ3OLbVCG8wOn81xTg5vSG4Axijnrn7G-qukAZ2Vfs811wvMrFr3cgPbo0ELf8ofgXuwD0JzBXCRxFUtgmPpsECgcnFp6zvMKe_fV6AOKiCXzyG0mhWjhn_hBcPmAeFYmneirwDEYDmOjI7xyjLZykHZBJ9GEV0z1SPTzIH45ddonFGUfrkD_1OKFtRV50MtYqsfFf6gfJsKaipIXjZyelRl8CI_82CCcYHYw-aGCl9DGDoHlJIo1u-i1f9aTdBQh3JhD8KiSTSHiETgKSogpXuToJg0luuT79teHLWrg2BbbrErf17nLm6DCX7FhTr22J45Y1iMMDlUxSGehiYNtm0SFtn41AUGwn2pmW8zwH9pgI9xjqipqXFf9DdtxH8rW0TtBRsK4H1OYgDI4IIHzCNc/http%3A%2F%2Fwww.aaate.net%2F

>

>

>

>

> -----Original Message-----

> From: athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] On

> Behalf Of Jennifer Sutton

> Sent: 03 May 2017 15:01

> To: Access Technology Higher Education Network <

> athen-list at u.washington.edu>

> Subject: Re: [Athen] correct terminology -- audio description or video

> description

>

> Oh, certainly. I'm very aware of audience considerations while

> simultaneously assuring accuracy, such as in legal contexts.

>

>

> Jennifer

>

>

>

> On 5/3/2017 6:57 AM, Sheryl E. Burgstahler wrote:

> > Jennifer,

> > I agree that either term works. Having said that, those of us speaking to

> newbies on the topic need to make sure to explain what we mean and share

> the

> alternative wording in order to minimize confusion.

> > Sheryl

> >

> > On May 3, 2017, at 6:47 AM, Jennifer Sutton <jsuttondc at gmail.com> wrote:

> >

> >> Thanks, all, for your responses.

> >>

> >> I did reach out to someone who used to be at WGBH, and that response

> dovetails with what you say here, Steve.

> >>

> >>

> >> My ultimate take-away, as in so many things accessibility-related is

> that

> which term one uses will depend on context.

> >>

> >>

> >> I don't think it is a matter of personal preference, at least in some

> cases.

> >>

> >>

> >> As I understand it (and suspected when I asked the question), there's a

> lot of history and politics behind why there are two terms (and I don't

> just

> mean U.S. government politics).

> >>

> >>

> >> As I understand it, when referring to CVAA, I think "video description"

> may be the preferred term.

> >>

> >>

> >> My concern with relying on the W3C is that they may be less aware of the

> U.S. situation, and in the context of some of what I am doing, that will

> matter.

> >>

> >>

> >> As in so many things, language does matter, and I'm glad I understand

> the

> ramifications of the two terms.

> >>

> >>

> >> Again, thanks to all for your input.

> >>

> >>

> >> Best,

> >>

> >> Jennifer

> >>

> >>

> >>

> >> On 5/3/2017 5:51 AM, steve.noble at louisville.edu wrote:

> >>> Hi Jennifer,

> >>>

> >>> The terms are now interchangeable, but the federal government prefers

> the term "video description" and that is the term typically used by

> Congress

> and the FCC. For instance, in 47 CFR 79.3 "Video description of video

> programming," the definition is given:

> >>> "(3) Video description. The insertion of audio narrated descriptions of

> a television program?s key visual elements into natural pauses between the

> program?s dialogue." [see

> https://www.gpo.gov/fdsys/pkg/CFR-2011-title47-vol4/pdf/CFR-

> 2011-title47-vol

> 4-sec79-3.pdf]

> >>> The federal government's use of the term "video description" dates back

> to the early 1990s, and perhaps before. You may want to reach out to Barry

> Cronin for the real scoop, as he was one of the original developers at

> WGBH.

> If you need his contact information, just let me know. In the mean time,

> here's a nice history for you:

> http://files.eric.ed.gov/fulltext/EJ1114571.pdf

> >>>

> >>> Hope that helps,

> >>> --Steve Noble

> >>> steve.noble at louisville.edu

> >>> 502-969-3088

> >>> http://louisville.academia.edu/SteveNoble

> >>>

> >>>

> >>> ________________________________________

> >>> From: athen-list [athen-list-bounces at mailman13.u.washington.edu] on

> behalf of Jennifer Sutton [jsuttondc at gmail.com]

> >>> Sent: Tuesday, May 02, 2017 10:14 PM

> >>> To: Access Technology Higher Education Network

> >>> Subject: [Athen] correct terminology -- audio description or video

> description

> >>>

> >>> Greetings, ATHEN list folks (along with a few others I've bcc-ed):

> >>>

> >>>

> >>> I'm sorting through my resources, and I'm confused about what the

> >>> correct term is for adding audio to videos to help explain visual

> >>> elements for blind people.

> >>>

> >>>

> >>> I know that we initially called it "audio description," but I had in

> >>> mind that the term was shifting to "video description" since that

> >>> describes better what it is, at least to a degree.

> >>>

> >>>

> >>> At the same time, I still see current articles and sites calling it

> >>> "audio description."

> >>>

> >>>

> >>> Does anyone have the definitive "scoop?"

> >>>

> >>>

> >>> I'd welcome links/citations in support of responses.

> >>>

> >>>

> >>> Is this, perhaps, one of these situations where we might *like* the

> term

> >>> to change, but the term "audio description" is so prevalent that

> >>> progress is slow?

> >>>

> >>>

> >>> Are there legal ramifications, i.e. maybe some state laws refer to it

> in

> >>> different ways?

> >>>

> >>>

> >>> Thanks in advance. I'm updating some things, and I'd like to get it

> right.

> >>>

> >>>

> >>> If it doesn't matter/they're now considered simply synonymous, I'd like

> >>> to know that, too.

> >>>

> >>>

> >>> Best,

> >>>

> >>> Jennifer

> >>>

> >>> _______________________________________________

> >>> athen-list mailing list

> >>> athen-list at mailman13.u.washington.edu

> >>>

> https://secure-web.cisco.com/1mkxmOn6sbBB14Hc1A3saII0xfvTpav2K5K4Lal7u-hOJ1x7QZ_YsIfAKSPkNi_Wf4xkIPiDQ1xM8heFqRBzv9u10g406aV2xV_X7ioruHF3OLB7yMVembJOwGfLG2NbtDzwXVO-SUt2kr3bC141ju5-3H7w1XGeGPCVU9ZiHaanno8pW36dvuvBWtV8E8saRzq7f-b0TkEKhiRWhSfOo9-Au2-s8WSAaAahB7XizdTHuAHw8SN64x5zXuUKrg5IVKh4psy7KwAm6_ueHrwh4NB9rY-1zotncQFrtMmDpT9UAC8Dd5feBAGmRWDEwFKuTCehUiWZHlEMjGPULKHZGHzXU2NSL_RGqMg_vk4zuNLXR7XSrTs3KjWWGPYA1RJZSmaglOGYKVr_0FAXb7cH97LnkSPa7DLdw3Zwhova-Jx9HGicbfBKzUTTbICnzyvdddQiSrOTvromLWFufMI56UKkyImjcJBb_91bUZqT-2q4/https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__

> mailman13.u.washington.e

> du_mailman_listinfo_athen-2Dlist&d=AwICAg&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf

> 1S

> O3AJ2bNrHlk&r=4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE&m=JW7m48F06P_

> 3qz8y

> hj_qyefoBPL6u7prODM_zYMvl60&s=eJLpz-kupRMcVVm1md89p-6zyP_

> nKtvrmQNSmNc1Jo0&e=

> >>> _______________________________________________

> >>> athen-list mailing list

> >>> athen-list at mailman13.u.washington.edu

> >>> http://mailman13.u.washington.edu/mailman/listinfo/athen-list

> >> _______________________________________________

> >> athen-list mailing list

> >> athen-list at mailman13.u.washington.edu

> >> http://mailman13.u.washington.edu/mailman/listinfo/athen-list

> > _______________________________________________

> > athen-list mailing list

> > athen-list at mailman13.u.washington.edu

> > http://mailman13.u.washington.edu/mailman/listinfo/athen-list

>

> _______________________________________________

> athen-list mailing list

> athen-list at mailman13.u.washington.edu

> http://mailman13.u.washington.edu/mailman/listinfo/athen-list

>

> _______________________________________________

> athen-list mailing list

> athen-list at mailman13.u.washington.edu

> http://mailman13.u.washington.edu/mailman/listinfo/athen-list

>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/athen-list/attachments/20170504/aba2773a/attachment-0001.html>

------------------------------

Message: 4
Date: Thu, 4 May 2017 10:26:10 -0400
From: "Zirkle, Kara" <zirklek at miamioh.edu>
To: Access Technology Higher Education Network
<athen-list at u.washington.edu>
Subject: Re: [Athen] Distilling WCAG Guidelines and 508 Criteria by
Role
Message-ID:
<CAM7d+tVyCPEV0sxwkW-PqOZMuzqtQt0Sh34_fFewuNrgf4SueQ at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I've found it very receptive of individuals when accessibility is broken
down by role and responsibility. That way its easily seen how everyone
plays a part in it and how it could easily fall apart if not everyone is on
board. Its puzzle pieces that you're putting together hoping not to lose
one along the way.

As for the procedures around procurement, this is a huge struggle due to
all of the various ways to purchase. The roles and responsibilities can be
broken down even further within this area.

Are you an individual who submits items to procurement, do you know to ask
the vendor up front for a VPAT?

Are you a P-Card user, do you know the responsibilities you have allowing
use of that card and is accessibility a part of that training?

Do you have contract language, a set of questions for RFPs, etc. Are you
working with legal counsel and procurement offices to get these things
standardized?

If you're a reviewer of purchase requests, do you have your own internal
procedure written out? Is there a risk or priority matrix? It is helpful
to create this when having various and sometimes overwhelming requests come
in. That way you can run it through your rubric to determine the risk and
priority and determine whether it gets pushed to the front or the back of
the review line. Reality is we can't do it all, we will never catch
everything and we can simply do the best we can with the resource we have.
So training, education and standard procedures are your best tools to use.

Would be happy to chat in more detail, since accessibility procurement is
about 75% of what I do.

Regards,

Kara

Kara Zirkle
Accessible Technology Specialist
Information Technology Services
Hoyt Hall, 312V
Oxford, OH 45056
Phone: 513-529-9006
Email: zirklek at miamioh.edu
Twitter: @AccessMU

On Thu, Apr 20, 2017 at 2:23 PM, Mary Heid <mheid at unr.edu> wrote:


> As our Information and Communication Technology (ICT) and Procurement

> policies are taking hold here at the University, I?m finding I need to

> develop a process to distribute the responsibility for accessibility

> assurance.

>

>

>

> We have a small team (me and a graduate assistant) who ?review software

> for accessibility.? Since we haven?t empowered anyone else to evaluate ICT

> for accessibility, we get requests to review all sorts of things including

> an enterprise document management system, a web-based survey someone has

> created to send to our residential students, an email blast to faculty in

> the form of a flyer with no alt text, to streaming our commencement

> ceremony. Obviously this is not sustainable.

>

>

>

> I was just reading the WAI Easy Checks ? A First Review of Web

> Accessibility <https://secure-web.cisco.com/1BHEtgL65_Dt8SAsDWpZSteRL-I_xpx36kYoNbtErQRhhOFitmW4jgUPyqnXipB-rat1XndN8ExYjTWhZ3mCKErVUPOkaplzr21nNcMQlYPntkmhg9Cyj0QoGltvp051yztznymQIicqhh5HxH_bCKMxvuBJGwP_KiItTxXcSFcLGbUaC-v-UdDlWcqmvb9cibLHy2cLxujmr3070oXSTwLVSDFgs6-TjVIbrfbmneq6XqX0aV6gyleeuE4my-8tt6jORiKnpKyvxQHP36PyGA5CGU5cZSzrzIgW8lr6BIShng-yOCagyCmdVQStbrfrz-fFO3ueNF1Mk3KK4UdxwN_fLY5y5NW-TNEcjuQ2d_2DJNCn-7ex5hiGP_egoEpWkZegTnexr4xKESaLhFgGhY9oChCCd1qyakPEYQQu7nXTkViQyj4lr_YtF7KAXvO_9xr8-arAu9FMaeLWFLid2zQ/https%3A%2F%2Fwww.w3.org%2FWAI%2Feval%2Fpreliminary> page and am

> considering publishing some more targeted form of it for my internal

> University colleagues so they can run a preliminary check of web content

> and functionality or require the same of their prospective vendors. This

> would ideally leave the resources of my small team to concentrate on high

> impact products, training others to evaluate for their departments or

> divisions, and conducting random audits.

>

>

>

> I?m open to others? suggestions about how you have successfully

> distributed this responsibility for accessibility ?compliance? at the

> procurement stage.

>

>

>

> Thanks!

>

>

>

> Mary Heid

>

> Enrollment Services

>

> System Administrator and Coordinator of Assistive Technology

>

> University of Nevada, Reno

>

> (775) 682-8038

>

> http://www.unr.edu/general-information/accessibility

>

>

>

> *From:* athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] *On

> Behalf Of *Sean Keegan

> *Sent:* Thursday, April 20, 2017 9:26 AM

> *To:* Access Technology Higher Education Network <

> athen-list at u.washington.edu>

> *Subject:* Re: [Athen] essential criteria across all products

>

>

>

> > Have you identified accessibility criteria that is essential across all

> products?

>

> > Something like ?accessible via keyboard alone? or ?images have alt

> text?. I?m trying to find items in 508/WCAG AA

>

> > that are absolutely essential across the board. We?d like to mandate

> these criteria in RFP.

>

>

>

> I understand why you are attempting to do this, but I urge caution. Both

> the refreshed 508 standards and WCAG 2.0, Level AA has done exactly what

> you ask in identifying accessibility criteria that is essential across

> information and communication technology products. These are technology

> standards and as a whole define the requirements that are essential. They

> are not intended to provide a menu where you choose something from column

> A, something from column B, etc.

>

>

>

> Viewing this in a different light, this would be like having informations

> security standards, but then only choosing to select specific information

> security requirements to meet. Does this make your IT environment more or

> less secure? What would you define as essential for information security

> (e.g., products must protect against viruses, but spyware is okay?)?

>

>

>

> I completely understand a desire to reword some of these accessibility

> criteria such that they make sense to someone who may not have a background

> or expertise in accessibility standards. And I fully comprehend a need to

> refine these accessibility criteria in such a way that make the most sense

> for different higher education audiences (e.g., faculty, administration,

> etc.) depending on their institutional roles and responsibilities. Crafting

> language and organizing information in such a manner that people can

> achieve accessibility expectations appropriate to their role makes complete

> sense.

>

>

>

> However, for RFP situations, I think you are putting yourself at greater

> risk by not insisting that vendors meet established and recognized

> accessibility standards. WCAG 2.0, Level AA (or the refreshed 508 standard)

> defines the essential accessibility criteria and that should be the

> expectation as part of any RFP. By deciding what does or does not

> constitute "essential" results in creating yet another accessibility

> standard that is only relevant and specific to your institution only AND

> runs a greater risk of

>

>

>

> Now, there may be situations in which there is no commercially available

> product that meets that standard or that in order to meet that

> accessibility standard the product would require a fundamental alteration.

> That is a legitimate argument and can be best addressed by defining a

> procurement/acquisition process in which such issues are addressed. There

> is a need to resolve the imbalance between an organization's functional

> business requirements, the products that exist currently in the

> marketplace, and accessibility. That needs to be addressed at a process

> level and not by creating a separate set of accessibility criteria.

>

>

>

> Lastly, I want to mention that a presenter at CSUN (who is highly literate

> in both WCAG and 508) identified four "show-stoppers" as it related to

> accessibility such that if these are failures, then very few individuals

> with disabilities would be able to participate. They are not what most

> people first think (these are all WCAG 2.0 success criteria):

>

> - 1.4.2: Audio Control on web page (must NOT allow automatic playing of

> sounds as this can over-ride a screen-reader)

>

> - 2.1.2: No Keyboard Trap (a keyboard user can't interact)

>

> - 2.2.2: Pause, Stop, Hide for moving, blinking, etc., content (this

> provides user control over content, for example if seizures are concern)

>

> - 2.3.1: Three Flashes or Below Threshold (to prevent seizures)

>

>

>

> While the above may have broad impact on individuals with disabilities,

> does this mean that these are the essential criteria? What about captions?

> What about image descriptions? etc.

>

>

>

> My point is that we already do have accessibility standard with criteria

> that has been established and we must be cautious if we attempt to distill

> such content down into something "easier." I understand why you may be

> pursuing this approach, but I urge caution, particularly as the original

> question indicated mandates related to RFP processes.

>

>

>

>

>

> Take care,

> Sean

>

>

>

> _______________________________________________

> athen-list mailing list

> athen-list at mailman13.u.washington.edu

> http://mailman13.u.washington.edu/mailman/listinfo/athen-list

>

>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/athen-list/attachments/20170504/7d6ef1c8/attachment-0001.html>

------------------------------

Message: 5
Date: Thu, 4 May 2017 09:46:09 -0500
From: "Zach" <zm290 at msstate.edu>
To: "'Access Technology Higher Education Network'"
<athen-list at u.washington.edu>
Subject: [Athen] FW: athen-list Digest, Vol 136, Issue 1
Message-ID: <00ee01d2c4e5$2bb32000$83196000$@msstate.edu>
Content-Type: text/plain; charset="us-ascii"

In regards to online laboratory products that are inaccessible to the blind,
I said I would write back with responses from blind chemists in my network.
The following message is from Henry Wedler-a UC Davis doctoral student in
organic chemistry.


-----Original Message-----
From: Henry Wedler [mailto:hobywedler at gmail.com]
Sent: Wednesday, May 03, 2017 7:32 AM
To: 'Zach' <zm290 at msstate.edu>
Subject: RE: [Athen] athen-list Digest, Vol 136, Issue 1


Hi Zac,

Thanks for your note and it's nice to hear from you.

I am unfamiliar with MacMillans.
However, UC Davis used an in-house rather inaccessible software and I
actually did find it to be easiest to have my lab assistant work through
post-lab exercises with me. They acted as a reader.

Hope this helps.

Best,
--Hoby




Zachary Mason
M.S. Student
Animal and Dairy Sciences
Mississippi State University



------------------------------

Message: 6
Date: Thu, 4 May 2017 09:18:37 -0700
From: Jennifer Sutton <jsuttondc at gmail.com>
To: Access Technology Higher Education Network
<athen-list at u.washington.edu>
Subject: Re: [Athen] correct terminology -- audio description or video
description
Message-ID: <5e8de4e8-821d-9394-6c3c-eccbfc0e7c59 at gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed

ATHENites:


I never dreamed my question would generate so much traffic or controversy.


But so that everyone has even more of the picture (since I do, due to
the people I bcc-ed who have even more history in the field than I
suspect most on this list do) . . .


This has been basically a political issue in the U.S. for decades, and
when I use the word "political," I mean in terms of debates, rather than
Federal government. To a degree, it's become an issue of branding --
somewhat dependent upon the source(s) of the product(s) you choose.


As I see it, the U.S. Federal government has been pretty clear in its
preference for video description.

If I were folks who received Federal funding for projects, I might want
to consider whether that might matter in whatever work you're doing,
even beyond the legal context when, I believe, using the correct term
would matter for legal accuracy.


In my particular case, when I am writing about laws, I will say "video
description" when they do, otherwise sometimes called audio
description," etc. But most other references will be left as they are,
i.e. "audio description," since not only is that my employer's
preference, but also because there are restrictions in the system that
would make it difficult to change.


I would also suggest that reliance on WCAG to guide one, in this
particular matter, might not actually be ideal. While it is only a note,
and as I understand it, there may be a version 2 of it at some point,
the reference that demonstrates a close focus in this area by WAI is
this one:


Media Accessibility User Requirements

http://secure-web.cisco.com/1u4J3uhexv91S_VrNVKvwAa49IkeOyaYJ3ZsGS8FLyJygccCKLQ1FQSoUh7wgOOKmDH0ugrep_mte18YAsJMNuLgQCrifXmlFG2FDMNR_hvclcDw6r34NKXQ0NjkQqmVRTL0XNYepv3DA_mRY2CfPTGFGdrx9GPifGoXq7t7NlY3i3xQ-44wYa7aZWksP0e4oWnv8ahgnoNlqeyH0ZjUgG9MkrPXEoPYzx5KITBBM8AvsgXwGbigf1mPhxfaAE0dvLmqZQWmH_3TCx2e1zcPhamnaRGtDkfxM0a7TIAxYCVpRmil5lzVIlA1ZQKYkdAqol0wQvMsDlrbGJCCS2VJF8c1bXyyzJZR7cNHFrpbjgiKGKHA8EC0-K9ALdBJEJLJr4imQ4vAZWF1-rr6yAU-fJFdqdsthOrskhGizckz3vmwsEkHfkXwJ99NaIrsUdr03RVCuHZ32kkQi57QLm-KLJA/http%3A%2F%2Fwww.w3.org%2FTR%2Fmedia-accessibility-reqs%2F


This group definitely wrestled with terminology, as I understand it.


Hope this reference proves helpful. I specifically asked someone who'd
worked on it for their thoughts as I suspect they focused a lot more
closely on it than those working on WCAG have had time to do. As a side
note, it will also be interesting to see whether this might be revisited
in WCAG 2.1, since it is well underway. As a result of my extensive
education on this subject, I will sure be on the lookout for both
further work on the "MAUR" and potential updates to WCAG 2.1.


I certainly got far more info and opinions than I imagined I would.
Thanks to all of you for your passion and knowledge.


Not that my personal opinion ever mattered because I was seeking
official guidance, but I would say that audio description sounds very
old-fashioned to me and only makes sense in the context of live
performances.


I think it all depends on who you listen to (in person, or where your
videos with the technology come from), how long you've been around (or
how long your "go to" references have been), in what contexts you've
been working (advocacy, legislation, not to mention Internationally), etc.


Descriptive narration was, indeed, floated at one time, but it never
caught on.


In terms of Netflix or iTunes . . . I guess I wouldn't consider them
particular authorities/informed by all the history I sure now have.
Somehow, I doubt they gave much thought to what they chose to call what
they offered; I suspect they were mostly concerned with getting the
content since there was such an outcry for it. But that's simply my
personal opinion. I'm not planning to check with them. :)


From an individual perspective, as someone who actually needs this
content, I wish folks would spend less time debating the term and more
time advocating for and creating the content itself. On this list, we
have seen only a micro-representation of the hours and hours of
meetings/discussions, over the decades.


Now, much to my pleasure, I'm moving on to other topics, and I wish you
all a pleasant day. Thanks again to everyone for their time and thoughts.


Best,

Jennifer







------------------------------

Message: 7
Date: Thu, 4 May 2017 10:36:48 -0700
From: "Sheryl E. Burgstahler" <sherylb at uw.edu>
To: Access Technology Higher Education Network
<athen-list at u.washington.edu>
Subject: Re: [Athen] correct terminology -- audio description or video
description
Message-ID: <423E3098-8B77-4561-A155-D28371E0D171 at uw.edu>
Content-Type: text/plain; charset="us-ascii"

Another factor to consider is being consistent with standards you have adopted for IT accessibility at your institution. Our state has adopted WCAG 2.0 level AA. The WCAG terminology and definition for this is:

audio description
narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone

Note 1: Audio descriptions of video provide information about actions, characters, scene changes, and on-screen text.

Note 2: In standard audio description, narration is added during existing pauses in dialogue.

Sheryl

On May 4, 2017, at 9:18 AM, Jennifer Sutton <jsuttondc at gmail.com> wrote:


> ATHENites:

>

>

> I never dreamed my question would generate so much traffic or controversy.

>

>

> But so that everyone has even more of the picture (since I do, due to the people I bcc-ed who have even more history in the field than I suspect most on this list do) . . .

>

>

> This has been basically a political issue in the U.S. for decades, and when I use the word "political," I mean in terms of debates, rather than Federal government. To a degree, it's become an issue of branding -- somewhat dependent upon the source(s) of the product(s) you choose.

>

>

> As I see it, the U.S. Federal government has been pretty clear in its preference for video description.

>

> If I were folks who received Federal funding for projects, I might want to consider whether that might matter in whatever work you're doing, even beyond the legal context when, I believe, using the correct term would matter for legal accuracy.

>

>

> In my particular case, when I am writing about laws, I will say "video description" when they do, otherwise sometimes called audio description," etc. But most other references will be left as they are, i.e. "audio description," since not only is that my employer's preference, but also because there are restrictions in the system that would make it difficult to change.

>

>

> I would also suggest that reliance on WCAG to guide one, in this particular matter, might not actually be ideal. While it is only a note, and as I understand it, there may be a version 2 of it at some point, the reference that demonstrates a close focus in this area by WAI is this one:

>

>

> Media Accessibility User Requirements

>

> http://secure-web.cisco.com/1q_Z4YxTrrMGNdQUuWKaNn5d1Sz1Es_c4RBFG2WNtc-1Gw5iQul61zhLBkFpBYg56cDqQFctfpdcMf5WFaxhIiMIdFzSPSxeOfMGltVrWfCd950Y0svlhnp2TnEQZBfuxRx7diWkqLdC6YwvMGslRIfaLqXjTFBUkrykyBKIlUOSSKgW4zJ-bZUlfI1bf42WBbrB_fHapoeqsvANJMP9s182FSMVknreBPN4_dxebKlNgfilm2DK4WpZxho3BFP6Ji8TVRGjHbIseBFCqbSQXm5d7b9uUhr5haV62smGzT1OjlqkpETHXkFi4bRfsadpcZhvoDaBs5fR0GJsq4-hnOTzoLhdBRPRGc4hm6IykU6ltz3KvX8-J5QOT9ndPbtTviz7jsIoWE8RBwou2LsU3qKx-4NzmfSNxUCG13TCflUEkAqZECVV6WpasZw7DGRZQ9BL5vKCHjz78SzpIcAf-gQ/http%3A%2F%2Fwww.w3.org%2FTR%2Fmedia-accessibility-reqs%2F

>

>

> This group definitely wrestled with terminology, as I understand it.

>

>

> Hope this reference proves helpful. I specifically asked someone who'd worked on it for their thoughts as I suspect they focused a lot more closely on it than those working on WCAG have had time to do. As a side note, it will also be interesting to see whether this might be revisited in WCAG 2.1, since it is well underway. As a result of my extensive education on this subject, I will sure be on the lookout for both further work on the "MAUR" and potential updates to WCAG 2.1.

>

>

> I certainly got far more info and opinions than I imagined I would. Thanks to all of you for your passion and knowledge.

>

>

> Not that my personal opinion ever mattered because I was seeking official guidance, but I would say that audio description sounds very old-fashioned to me and only makes sense in the context of live performances.

>

>

> I think it all depends on who you listen to (in person, or where your videos with the technology come from), how long you've been around (or how long your "go to" references have been), in what contexts you've been working (advocacy, legislation, not to mention Internationally), etc.

>

>

> Descriptive narration was, indeed, floated at one time, but it never caught on.

>

>

> In terms of Netflix or iTunes . . . I guess I wouldn't consider them particular authorities/informed by all the history I sure now have. Somehow, I doubt they gave much thought to what they chose to call what they offered; I suspect they were mostly concerned with getting the content since there was such an outcry for it. But that's simply my personal opinion. I'm not planning to check with them. :)

>

>

> From an individual perspective, as someone who actually needs this content, I wish folks would spend less time debating the term and more time advocating for and creating the content itself. On this list, we have seen only a micro-representation of the hours and hours of meetings/discussions, over the decades.

>

>

> Now, much to my pleasure, I'm moving on to other topics, and I wish you all a pleasant day. Thanks again to everyone for their time and thoughts.

>

>

> Best,

>

> Jennifer

>

>

>

>

>

> _______________________________________________

> athen-list mailing list

> athen-list at mailman13.u.washington.edu

> http://mailman13.u.washington.edu/mailman/listinfo/athen-list


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/athen-list/attachments/20170504/1e098723/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
athen-list mailing list
athen-list at mailman13.u.washington.edu
http://mailman13.u.washington.edu/mailman/listinfo/athen-list


------------------------------

End of athen-list Digest, Vol 136, Issue 4
******************************************




More information about the athen-list mailing list