Page Comparison

Section

Column width 60% Supported by Raising the Floor Supported by UNESCO Invitation to Second Meeting You are invited to the second Open Source Accessibility Forum to take place in Toronto in conjunction with Toronto Open Source Week and FSOSS . The dates for the Open Source Accessibility Forum will be October 28th and 29th.  Logistics for the meetings are at: http://fsoss.senecac.on.ca/2009/location and will be posted on this Wiki. Thanks to the discussions and work done during the first forum in Vancouver, we will have 5 focused discussions (in addition to advancing discussions regarding critical gaps and shared resources). These encompass the major priorities we identified and synthesized during the Vancouver meeting.  The 5 areas are: Column with 40% solid Panel borderStyle borderColor #566b30 bgColor #fff titleBGColor #D3E3C4 borderStyle solid title On this Page Table of Contents toc maxLevel 5 minLevel 2 maxLevel 5

1. Accessible collaboration tools
The communication systems, bug-tracking systems, planning wikis, text chats, teleconference systems, and other means whereby open source communities plan, design, develop, evaluate, refine and distribute open source systems must be accessible. This will enable participation by community members with disabilities. It will mean that the needs of people with disabilities are represented in the community and it will enable the participation of individuals knowledgeable and personally interested in accessibility requirements.  These systems must also address multiple languages.

...

On August 11, 2009 a number of open source accessibility experts met in Vancouver to talk about how to make the most of what is being invested in accessibility in open source communities and projects. This is to address the following issues and challenges:

• we want to make sure that open source applications, systems and assistive technologies are a viable, affordable and sustainable means for people with disabilities around the word to participate in all that information and communication technologies make possible
• there are limited resources available to address accessibility
• we don't want to do work redundantly
• we want to share work wherever possible, keep each other informed about what is being done and find a way to address the less attractive but important tasks
• we want to make sure that our approaches provide people with disabilities with relatively consistent or compatible options across domains
• we want to leverage the unique advantages of open source development and communities to provide innovative accessibility.

Also, through a number of grants and awards, we have the opportunity to address gaps not addressed through existing or planned efforts.

...