[OpenCast] Accessibility requirements for user facing applications

[Adam Hochman]

Thanks John.  This was an attempt to gain a perspective from a broader 
community, but I agree with you. Fortunately we have some folks 
associated with Fluid on the project.

~Adam

John Norman wrote:
> Adam
>
> My advice, if you are thinking of using Flex for UI, would be to post  
> also on the Fluid list. They have the right expertise to advise on  
> such a fundamental decision. I would be uncomfortable adopting Flex  
> based on current accessibility policies as I would expect those  
> policies to evolve over time (to be more stringent). The capacity of a  
> technology to take anticipated changes into account will be important  
> as well as current requirements. Currently, Fluid are the best experts  
> I know for what requirements might become mainstream on what  
> timescale. Not that they can predict the future of course...
>
> John
>
> On 14 Apr 2009, at 21:52, Adam Hochman wrote:
>
>   
>> This original question really derives from Matterhorn's desire to  
>> better
>> understand disabled users' needs around sophisticated media  
>> interaction
>> tools.
>>
>> We may use Flex as a UI technology for Matterhorn's media interaction
>> tools and would like to know how some of the existing Flex media tools
>> hold up.  My understanding is that Flex does not provide adequate
>> accessibility support.  Is anyone interested in having your campus
>> "disability liaison unit" review some of these tools already developed
>> by our colleagues at Osnabruck?
>>
>> I am particularly interested in understanding the needs around
>> bookmarking, annotation, and "in media navigation" for users with  
>> sight
>> and hearing disabilities.  Would this type of functionality apply to
>> individuals with hearing disabilities?  Does your institution
>> expect/require that these media interaction tools provide  
>> functionality
>> for users these disabilities?  Are you aware of any baseline
>> requirements for adequate functionality?
>>
>> Adam Hochman wrote:
>>     
>>> UC Berkeley, in accordance with California law, requires that "user
>>> facing applications" provide adequate functionality for users with
>>> disabilities.   Do most other states share this requirement?
>>>
>>> To community member from universities outside of the U.S., do you  
>>> share
>>> similar requirements?  I am particularly interested in how these
>>> requirements translate into best practices for media focused
>>> applications (i.e. audio and video).
>>>
>>> I am also curious about university policies around captioning  
>>> media.  At
>>> Berkeley, in short, we provide captions upon request through our  
>>> DSP office.
>>>
>>> ~Adam
>>>
>>>
>>> ----------------
>>> A community centered around open, scalable, and sustainable podcast/ 
>>> webcast solutions and best practices for higher education.
>>>
>>> To unsubscribe from our list, simply go the following address,  
>>> enter your email address, and hit the unsubscribe button.
>>>
>>> https://calmail.berkeley.edu/manage/list/reminder/podcast@lists.berkeley.edu
>>>
>>>
>>>       
>> ----------------
>> A community centered around open, scalable, and sustainable podcast/ 
>> webcast solutions and best practices for higher education.
>>
>> To unsubscribe from our list, simply go the following address, enter  
>> your email address, and hit the unsubscribe button.
>>
>> https://calmail.berkeley.edu/manage/list/reminder/podcast@lists.berkeley.edu
>>     
>
>
> ----------------
> A community centered around open, scalable, and sustainable podcast/webcast solutions and best practices for higher education.
>
> To unsubscribe from our list, simply go the following address, enter your email address, and hit the unsubscribe button. 
>
> https://calmail.berkeley.edu/manage/list/reminder/podcast@lists.berkeley.edu
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090414/bf1ee058/attachment.html>