[Building Sakai] Accessibility Statement Introduction / For Review

Silverio, Gonzalo gsilver at umich.edu
Wed Mar 10 11:41:53 PST 2010


Great statement of intent that lays a good foundation and has specific,
clear and measurable targets without going into too much detail.

+1

    -Gonzalo

On 3/3/10 12:18 PM, "Richwine, Brian L" <brichwin at indiana.edu> wrote:

> Hello,
>  
> The Sakai Accessibility Working Group would like your feedback.
>  
> As a first step towards developing accessibility goals, guidelines, and
> documentation for Sakai 3 development, the Accessibility Working Group has
> written a draft Sakai Accessibility Statement.
>  
> Please take a moment to review the following statement, and let us know if
> this statement meets your expectations for Sakai 3.
>  
> <statement>
> Consistent with the goal to make Sakai the most innovative and powerful
> Collaboration and Learning Environment, the Sakai community with the support
> and encouragement of Sakai Foundation will ensure that all of the features of
> Sakai 3 (the next generation of Sakai) are accessible and usable by the
> greatest number of potential users, including users with disabilities.
>  
> To ensure this high level of accessibility for the greatest number of users,
> our goal is to design Sakai 3 to meet or exceed the accessibility design
> principals found in recognized international standards. Our goal is to meet
> all of the W3C Web Content Accessibility Guidelines (WCAG) 2.0 Level A and AA
> Success Criteria and the Authoring Tool Accessibility Guidelines (ATAG).
>  
> To ensure Sakai 3 has as few accessibility barriers as possible and to provide
> a rich and enjoyable user experience for all users, Sakai will be developed
> using emerging standards and best practice design techniques (such as the
> WAI-ARIA Suite), and support existing and emerging adaptive technologies.
>  
> Leveraging accessibility experts in the Sakai Community, all future
> development in Sakai 3 will undergo usability and accessibility evaluations
> throughout the design and development process to ensure that it meets these
> goals.
> </statement>
>  
> Note: Current accessibility documentation, end-user accessibility help
> documentation, contact information for reporting accessibility issues, and the
> methods and technical details used to achieve the accessibility goals are left
> to supporting documents and will be linked to from the page hosting the
> accessibility statement.
>  
> Does the statement show the appropriate commitment to accessibility for Sakai?
> Do the goals stated seem credible and reachable? Is the statement missing
> something that you expected?
>  
> Don't feel limited by these questions, any and all comments are welcome!
>  
> We are excited to hear your feedback.
>  
> Thank you,
>   The Accessibility Working Group
>   http://confluence.sakaiproject.org/display/2ACC/Accessibility+Working+Group
>  
> Brian Richwine
> Adaptive Technology Support Specialist
> Adaptive Technology and Accessibility Centers
> Indiana University - Bloomington/Indianapolis
> http://iuadapts.indiana.edu <http://iuadapts.indiana.edu>
> (812) 856-4112
>  



More information about the sakai-dev mailing list