E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 10 (In chronological order)

From: wendy constantine
Date: Thu, Dec 14 2006 12:16PM
Subject: multimedia accessibility a specialist skillset?
No previous message | Next message →

Is the development of accessible rich media including flash, video
and audio appropriately considered a specialist skillset? I've been
conducting research for a thesis in multimedia accessibility for
online museum education, and I am increasingly frustrated by the
reasons developers give for not making an accessible digital product.

The reason I expected to hear is that clients don't require it. Cost,
time, tools and knowledge are the other common barriers, in that order.

If one approaches accessibility from a universal design perspective,
meaning conceiving of the design of the product to meet the needs of
various audiences, the time and cost of accessibility can be
minimized, in my perspective. I have yet to find a developer that
will second that notion, however.

As for tools, captioning tools for video and even flash video are
freely available. The availability of a transcript (audio/video
descriptions aside) would be the main barrier to producing captions
cost effectively. And there are tools to help with just that.
Captioning long segments of video can be time-consuming, yet I would
have to question the reasoning behind delivering long segments of
video over the web.

If anyone has examples of tools and/or services for captioning,
please do suggest them. I would very much like to present some
solutions to these common barriers.

Flash has also come a long way in providing accessibility built into
the development process. It won't think for you, but Flash can enable
accessibility today in ways most developers do not realize. As Bob
Reagan has so eloquently said, it is more a failure of the
imagination than of the tools.

Can anyone foresee a time when accessibility, even for rich media,
will be considered standards based design and not a specialist activity?

Thanks for your input!
Wendy Constantine

From: Austin, Darrel
Date: Thu, Dec 14 2006 12:16PM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | Next message →

> I have yet
> to find a developer that will second that notion, however.

I'll second it, as I'm sure most folks on this list would. ;o)

The main barrier is that developers are just lazy. They don't care about
accessibiliy or even universal design.

It's not always malicious...a lot of web sites are still being built by
ad agencies where 99% of their mindset is still firmly planted in the
world of print and it's a real struggle for them to comprehend concepts
like universal design.

> Can anyone foresee a time when accessibility, even for rich
> media, will be considered standards based design and not a
> specialist activity?

Media production, in general, is very much a collection of specialties.
I imagine it will always be a specialty skill set just as photography,
copywriting, and the like are all specialties.

The question to ask is perhaps: when will accessibility issues be
brought into the design process early on rather than as the typical last
minute add-on?

I don't have an answer for that, unfortunately. ;0)

-Darrel

From: Al Sparber
Date: Thu, Dec 14 2006 12:16PM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | Next message →

> It's not always malicious...a lot of web sites are still being built
> by
> ad agencies where 99% of their mindset is still firmly planted in
> the
> world of print and it's a real struggle for them to comprehend
> concepts
> like universal design.

I had a funny dream once that Macy's Cellar, in the 40th century,
specialized in selling cocktail coasters made from unearthed CDs and
DVDs, while the NY Times #1 bestseller was a book speculating on what
21st century people were really like, since there was no written
record to be found :-)

From: John E. Brandt
Date: Thu, Dec 14 2006 12:16PM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | Next message →

I just attended a statewide IT conference and sat in on three sessions
related to "Usability" and Web 2.0. In nearly all the cases presented,
accessibility was not even mentioned other than to note it was a subset of
Usability. I was frankly a bit horrified when two women presenters talked
about all the new gadgets out there to soup-up your website...and then they
mumbled something about needing to create an HTML option for accessibility
purposes. When I called them to task on this, they danced around and gave
all of those "stupid" answers like, "You need to know your clientele..."
Then they basically admitted they knew next to nothing about making this
"stuff" accessible, but "we have a colleague who will be here later..."

Throughout the day in several presentations from different people, including
Eric Miller who led the Semantic Web Initiative at W3C, folks kept saying
things like "bad programming," or "lazy coding" causes this or that to
happen. The implication was that "usability" means "good coding" and "hard
work."

Clearly, human nature is to find the path to least resistance, and
accessibility presents challenges and the "hard work" that many developers
avoid. Some are even adamant that we shouldn't even bother with this
marginal community (Actual Quote: "How many blind people are there
anyway?"). It helps me to understand why the community of people with
disabilities and advocates for this community have had to work hard to
create laws and rules.

In all my workshops, I always warn people about what has happened elsewhere
and it is "just a matter of time" before this will be the law of the land
(e.g., "the Target.com case"). With their heads in the sand and deadlines to
meet, they continue to cut corners.

So, I guess my answer to your question: "Can anyone foresee a time when
accessibility, even for rich media, will be considered standards based
design and not a specialist activity?" - not unless it becomes law. If it is
left to be optional. It will always be optional.

Just my opinion...

~j


John E. Brandt
Augusta, Maine USA
www.jebswebs.com

From: Emma Duke-Williams
Date: Thu, Dec 14 2006 12:17PM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | Next message →

On 12/13/06, John E. Brandt < = EMAIL ADDRESS REMOVED = > wrote:
> I just attended a statewide IT conference and sat in on three sessions
> related to "Usability" and Web 2.0.

Accessibility and Web 2.0 is something I've been thinking about quite
a lot. We get students to keep blogs - last year I had one student who
was dyslexic, and she chose to keep a number of her posts as audio
podcasts, rather than writing them, as it was easier for her. We've
not got any hearing impaired students, but had we, what would have
been the best option? Should we have stopped her doing something that
was easier for her (writing wasn't impossible, just more difficult) -
if that would have caused problems for one person on the course? Or,
should someone have transcribed it for her?

Clearly there is a difference (or I think there is) between getting
the students to use Web 2.0 tools for their own reflection - I think
that it's more important that they are happy with the tool, than that
the rest of the group can easily access it. For the blog that I write,
as they have access to that if they want, then it's a bit different. I
say "bit", as there is no requirement that they access it. It's my
research blog, which is open to them should they choose. However, as I
offer it, I figure I ought to ensure that the students that I have can
access it.

Course materials, should they go into a blog, are clearly yet another
step up, but we've not started doing that, yet...

As the unit that requires them to blog is a second year unit, I think
that were we to get any visually impaired students, I'd get them to
test the tool I intended using, and, if that wasn't suitable, find
some others - clearly that would put more initial stress on that
particular student, but at least it would be the platform with which
that particular student was the most happy.

Emma

From: Spruill Kevin
Date: Thu, Dec 14 2006 12:17PM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | Next message →

Wendy et al,

First, I second that motion (and emotion) - but also recognize that I'm
in the minority among developers and designers. Not because all are
"lazy" (easy w/ the blanket statements out there folks), but more often
because no one has taught them how, let alone why.

This reality will not change until that fundamental shift is made in the
education/creation/empowerment of new developers and designers... Come
on, think about it - it's taken how long for Usability to become a
consideration... And even now a lot of times it is lacking in scope and
consideration (as noted by the other commentors seminar experience).

'Course, the flip side is that the resulting specialization can be an
economic boon for developers such as myself at times. I'd much rather be
out of work because there was no need for "specialists" though.

Just my rambling $.02 - Good thesis topic by the way.


Kevin Spruill
IT Specialist
Information Resources Accessibility Program
OS:CIO:ES:BI:CS:IRAP:IT

From: Tim Harshbarger
Date: Thu, Dec 14 2006 12:17PM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | Next message →

I am not so certain that the most important issue with developing
accessible technology has to do with gaining the knowledge or skills
necessary to develop accessible technology.

There are plenty of good resources (like WebAIM) for learning how to
create accessible sites or applications. Most of the techniques are not
even that difficult to do once one knows the technique. There are some
very challenging accessibility issues, but with some creativity, access
to users with disabilities, and a desire to create an interface that
really works for the users, most can be resolved satisfactorily.

I think most of the time the issue that still creates the most problems
is the perception that "we don't have any users with disabilities" or
"people using screen readers don't use our site." I find if I can get
people beyond this point to understand the real impact of accessibility,
the accessibility issues are not any more challenging than any other
technical issues that need to be resolved in order to create a good
quality site or application.

One thing to remember about professional developers is that they do not
create applications or sites in a vacuum. Developers create
applications and sites at the request of others. While it is helpful if
the developers embrace accessibility, I think it might be more important
that the people requesting the application or site want the product to
be accessible.

Tim

From: John Foliot - Stanford Online Accessibility Program
Date: Thu, Dec 14 2006 12:18PM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | Next message →

Tim Harshbarger wrote:
>
> I think most of the time the issue that still creates the most
> problems is the perception that "we don't have any users with
> disabilities" or "people using screen readers don't use our site." I
> find if I can get people beyond this point to understand the real
> impact of accessibility, the accessibility issues are not any more
> challenging than any other technical issues that need to be resolved
> in order to create a good quality site or application.

I would have to agree with Tim here whole-heartedly. In my current position
roughly half my time is spent in "outreach and education", helping people
understand the entire ramifications of what "accessible web design" really
means, and why it should matter to them. Having been involved in the web
accessibility field for quite some time now, I am happy to see that the
over-all awareness and general understanding of many of the issues has grown
exponentially - people "get it" now, although they sometimes don't
understand how it can benefit them entirely. To echo John Brandt, for some
it is simply a legal requirement, but even then, I am seeing an
understanding and agreement as to *why* it is a legal requirement. Then
when I layer on the social, business and technological reasons why
accessible design is important, most people are sold. (Disclaimer - in my
former life I *was* a salesman <grin>)

However, at the same time, there still exists a need to help developers
beyond the initial awareness phase. Tim is right, once you learn and
understand, continuing in that track is relatively easy. But oft time
getting into that track requires additional experience and expertise, which
currently is still in short supply. So to bring this back to one of the
initial questions in the thread: Wendy asked, "Is the development of
accessible rich media including flash, video
and audio appropriately considered a specialist skillset?" I would have to
say that in December, 2006, yes, the numbers would suggest that it is still
a specialist skillset, and that it may remain that way for a fair time
still.

I believe that at some levels, enterprise class web-development will always
remain a specialist skillset, as is the writing of screen plays, working in
the field of microbiology, or being a Class "A" auto-mechanic. I think a
better question to be asking is: "Will non-specialist tools for general
on-line content creation evolve to incorporate features to address
accessibility requirements?" coupled with "Will non-specialist creators
adopt these tools and practices?". Many of the tools have, or are, getting
much more sophisticated in this regard, and I would single out Adobe (as
well as the tools from the former macromedia) as one company who have
embraced these goals from both the legal requirement *and* desire to "do the
right thing" perspective. (And in fairness, there are others - IBM is
another company who are "in") But as these tools evolve, Tim's point of
making people aware of the issues, coupled with teaching them how the
emerging tools facilitate these goals will remain our biggest challenge.

Just another $0.02

JF

From: js ba
Date: Thu, Dec 14 2006 6:20PM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | Next message →

As an Art & Technology 'specialist' when I design any website or any sound or sight (video or music) that are being put into the website it only takes minimal time to make sure all options of accessing that media is on the site. For instance all video gets a voice over and transcript directly on the page where video would be 'viewed' so audio is an option as well as text options for the differing degrees of eyesight. For sound media-text is written on that same page as well as any other way that can be descriptive to convey and serve as many people as possible. I also try to take into account the assistive technology that is in use today as well as tomorrows concepts, but I only can rely on what I can do and I haven't given clients that 'option' of only this or that accessibilty. It should be accessible to all not just those a 'client' thinks of or knows. I still have much to learn and ask many questions. Hopefully this will let my work serve people much better in the
longrun.
Thanks,
js

John Foliot - Stanford Online Accessibility Program < = EMAIL ADDRESS REMOVED = > wrote:
Tim Harshbarger wrote:
>
> I think most of the time the issue that still creates the most
> problems is the perception that "we don't have any users with
> disabilities" or "people using screen readers don't use our site." I
> find if I can get people beyond this point to understand the real
> impact of accessibility, the accessibility issues are not any more
> challenging than any other technical issues that need to be resolved
> in order to create a good quality site or application.

I would have to agree with Tim here whole-heartedly. In my current position
roughly half my time is spent in "outreach and education", helping people
understand the entire ramifications of what "accessible web design" really
means, and why it should matter to them. Having been involved in the web
accessibility field for quite some time now, I am happy to see that the
over-all awareness and general understanding of many of the issues has grown
exponentially - people "get it" now, although they sometimes don't
understand how it can benefit them entirely. To echo John Brandt, for some
it is simply a legal requirement, but even then, I am seeing an
understanding and agreement as to *why* it is a legal requirement. Then
when I layer on the social, business and technological reasons why
accessible design is important, most people are sold. (Disclaimer - in my
former life I *was* a salesman )

However, at the same time, there still exists a need to help developers
beyond the initial awareness phase. Tim is right, once you learn and
understand, continuing in that track is relatively easy. But oft time
getting into that track requires additional experience and expertise, which
currently is still in short supply. So to bring this back to one of the
initial questions in the thread: Wendy asked, "Is the development of
accessible rich media including flash, video
and audio appropriately considered a specialist skillset?" I would have to
say that in December, 2006, yes, the numbers would suggest that it is still
a specialist skillset, and that it may remain that way for a fair time
still.

I believe that at some levels, enterprise class web-development will always
remain a specialist skillset, as is the writing of screen plays, working in
the field of microbiology, or being a Class "A" auto-mechanic. I think a
better question to be asking is: "Will non-specialist tools for general
on-line content creation evolve to incorporate features to address
accessibility requirements?" coupled with "Will non-specialist creators
adopt these tools and practices?". Many of the tools have, or are, getting
much more sophisticated in this regard, and I would single out Adobe (as
well as the tools from the former macromedia) as one company who have
embraced these goals from both the legal requirement *and* desire to "do the
right thing" perspective. (And in fairness, there are others - IBM is
another company who are "in") But as these tools evolve, Tim's point of
making people aware of the issues, coupled with teaching them how the
emerging tools facilitate these goals will remain our biggest challenge.

Just another $0.02

JF

From: wendy constantine
Date: Sat, Dec 16 2006 10:30AM
Subject: Re: multimedia accessibility a specialist skillset?
← Previous message | No next message

Thank you all for your very thoughtful responses. Within the museum
community, I am finding that very few institutions have an internal
policy to mandate accessibility in multimedia, and only some require
HTML-based accessibility (as it is easy to verify automatically).
Half of the museums I surveyed receive federal funding for multimedia
development. Yet, captions and transcripts for video are infrequently
available and Flash is becoming the most popular tool for educational
media in this industry. At the advice of their developers, text-only
versions are built to accommodate legal accessibility requirements,
and the Flash/video/audio components are rarely altered to comply.

As a flash developer, I can see the tremendous opportunity (and
responsibility) Flash provides if directed appropriately. Very few
developers have been willing to embrace this creative challenge. As
for video and audio formats, providing open (or closed) captions for
web media is not particularly difficult, and aids viewers for whom
English is not their first language, do not have headphones or
speakers, as well as those with hearing loss.

I do realize that my vision for multimedia accessibility is perhaps
idealist and academic, somewhat removed from the realities that
museums (and other industries) face. Yet I would have to argue that
technology in the future will increasingly be driven by user needs
and desires. The ability to provide content in any modality and
format of presentation, for use on multiple device types, will
largely become the users' choice and not the developer/publisher of
the content. In essence, does this shift from fixed to flexible
content ring true to any of you, particularly in regards to
accessibility?

Wendy Constantine



On Dec 14, 2006, at 2:00 PM, = EMAIL ADDRESS REMOVED = wrote:

> Send WebAIM-Forum mailing list submissions to
> = EMAIL ADDRESS REMOVED =
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://list.webaim.org/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> = EMAIL ADDRESS REMOVED =
>
> You can reach the person managing the list at
> = EMAIL ADDRESS REMOVED =
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
> Today's Topics:
>
> 1. Re: multimedia accessibility a specialist skillset?
> (Spruill Kevin)
> 2. Re: multimedia accessibility a specialist skillset?
> (Tim Harshbarger)
> 3. President of NFB says don't change currency (Karl Groves)
> 4. Re: multimedia accessibility a specialist skillset?
> (John Foliot - Stanford Online Accessibility Program)
>
> From: "Spruill Kevin" < = EMAIL ADDRESS REMOVED = >
> Date: December 13, 2006 4:11:58 PM EST
> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> Subject: Re: [WebAIM] multimedia accessibility a specialist skillset?
> Reply-To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>
>
> Wendy et al,
>
> First, I second that motion (and emotion) - but also recognize that
> I'm
> in the minority among developers and designers. Not because all are
> "lazy" (easy w/ the blanket statements out there folks), but more
> often
> because no one has taught them how, let alone why.
>
> This reality will not change until that fundamental shift is made
> in the
> education/creation/empowerment of new developers and designers... Come
> on, think about it - it's taken how long for Usability to become a
> consideration... And even now a lot of times it is lacking in scope
> and
> consideration (as noted by the other commentors seminar experience).
>
> 'Course, the flip side is that the resulting specialization can be an
> economic boon for developers such as myself at times. I'd much
> rather be
> out of work because there was no need for "specialists" though.
>
> Just my rambling $.02 - Good thesis topic by the way.
>
>
> Kevin Spruill
> IT Specialist
> Information Resources Accessibility Program
> OS:CIO:ES:BI:CS:IRAP:IT
>
>
>