ICANN Accessibility Taskforce Meeting 

Date: Friday, 03 October 2014

Time: 13:00 - 14:00 local time (for the time in various timezones click here)

Meeting Number: AL./1014/01

How do I participate in this meeting?  

Recording:    EN

Transcript: EN

Action Items:  None 

AC Chat Transcript :  EN 

Adobe Connect Meeting Room: https://icann.adobeconnect.com/accessibilitywg/

Participants: Glenn McKnight, Cheryl Langdon-Orr, Olivier Crepin Leblond  Yasuichi Kitamura, Siranush Vardanyan,  Gunela Astbrink, Dev Anand Teelucksingh

Apologies:

Staff: Heidi Ullrich, Gisella Gruber, Laura Bengford, Terri Agnew

Call Management: Terri Agnew

AGENDA: 

Chair: Cheryl Langdon-Orr

0.   Some  Matters arising from our last meeting will NOT be discussed in today's call but will be addressed in our next F2F  meeting scheduled on: Tuesday 14 October 2014 -  At-Large Accessibility Working Group - Los Angeles and that there we will be discussing and work-shopping our Classification and Prioritisation from the Primary Objectives for the Task  Force – Including an Identification of the Key  Short,  Medium and Long Term opportunities, from our original set as follows:

Building a culture of accessibility
•       Disability awareness toolkit be developed
•       Disability awareness training be provided
•       Keynote speakers at ICANN meetings to include representatives from disability community
•       Offer disability showcase events at ICANN meetings demonstrating various innovative ways people with disability use the Internet
•       “Accessibility Champions” amongst ICANN staff be identified
•       ICANN encourage employment of staff with disability
•       Incorporate an accessibility trigger in policy development as well as ICANN processes and practices Increasing web accessibility
•       ICANN websites meet internationally recognised W3C Web Content Accessibility Guidelines (WCAG) v2.0 Level AA. This includes captioning of videos
•       Development of ICANN policy on web accessibility
•       Encouragement of ccTLDs to develop a best practice guide on web accessibility
•       Encouragement of registries to use the best practice guide in relation to registrars - in particular to alert registrants to use WCAG v2.0 when developing websites.
  

1. Welcome, Attendance and Apologies.  (2 mins)
   
   
2. Review of Action Items from the last meeting  see At-Large Technology Taskforce 2014-09-08 Action Items  (5 mins)
    

   Action Items :

    

   Dev to create a table evaluating group chat applications and come up with a feature set and key differences.

    

    

    

   Ongoing Action Items

    

   AI (ongoing):GC to test wiki translate plugins on Android platfoms

    

   AI (partially completed): Reminder to be sent by Dev to TTF members to look at contents of the Ideas for Improving the Organisation of the At Large content wiki page: Ideas for improving the organisation of At-Large content and leave comments. Upon approval by TTF members, notice for comments to be sent out to ALAC members, RALOs and staff.

    

   AI: (ongoing): Send to RALOs list of webconferencing features

    

   AI Glenn and Judith to liaise with differently abled members of VIBUG and ISOC Disability Chapter to help with evaluating group chat once a group chat has been selected and Adobe Connect room as a whole.

    

   Seun and Nathalie to test Jappix before the next TTF call on the 25th August. (call tbc)

   
   
   
3. Discussion of our role in Implementation planning for Recommendation 11 out of the recent ATLAS II held in London June 2014. (20-30 mins)
   
    
   Recommendation 11 states:
   "ICANN must implement a range of services to facilitate access according to various criteria (gender; cultural diversity) and user needs (disabilities, etc…)."
   In addition to some questions raised by Glenn and Judith, the Chair of both the Outreach Sub Committee and the Technology Taskforce, (TTF) being two of the other groups tasked with dealing with this recommendation  Dev Anand Teelucksingh asks  "Can you please clarify the "various criteria such as gender or cultural diversity" aspect?" noting "The "user needs" aspect was understood to mean access for the differently-abled or for those that don't have high speed internet or for those with no reliable internet access." as a result of deliberations at a recent TTF Meeting.