Cognitive Accessibility Task Force

01 Jun 2015


lisa, michael, mike, EA, chaohai, john_mike_tony, janina_and_niel, Janina, ayelet
Lisa Seeman


<Lisa_Seeman> scribe: EA

Lisa to start with time lines and action items

<Lisa_Seeman> next item

Holidays and missed calls have delayed some items

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Current_schedules

June 7th release a second editors draft - Lisa to re-structure document, Neil and EA to complete numbers

Lisa has worked on ARIA techniques

<Lisa_Seeman> https://github.com/w3c/coga/commit/35603ddb3fa03c839953f0f29f9f4ee8f69f92ae

<Tony_Doran> I have some experience here also.

Neil and EA have started the process of completing the document but have lots of problems developing techniques

<Tony_Doran> Google translate will move date formats in some cases too!

<Tony_Doran> Phone numbers are a nasty one - and region dependent.

<Tony_Doran> Mapping is now in the voices - for the high end voices

<Tony_Doran> they have extensive XML mappings

Janina mentioned screen reader issues as well with numbers - using Linux

<Tony_Doran> They do a surprisingly good job compared to a few years back

<Tony_Doran> Overlap is an issue - yes.

Speak-up and Orca but controlled by the TTS engine

<Tony_Doran> Voices have difficulty with context interpretation.....

TTS needs to support not confuse esp for coga individuals

<Tony_Doran> unit of brightness

<Tony_Doran> Don't forget postcodes and zip codes!

Yes, measurement, money and temperature

Tony has also mentioned changes as voices improve and how mapping needs to be included to improve the output

Tony commented that new versions of TTS voices have vastly improved but expensive.

Lisa suggested author techniques and way the browser deals with issues need to be addressed

Lisa suggested Three sections - overall issue paper - roadmap - clear instructions as how number or whatever should be read, author techniques - then need future techniques - write numbers according to the TTS

Then need to think what this means in terms of 'pass' and 'fail' - can't say it is going to work immediately - make a recommendation

<Tony_Doran> perhaps there is room for a "say like" tag?

Neil said this makes sense but there is an additional step that formatting can be made to be correct - do if you follow ISO conventions etc May read correctly but still not work for the locale or the way people are working with numbers

Lisa said that we do not want people to have to learn something new and John has said we need to check ISO really fits with our recommendations.

Need to present the issues and reference why there may need to be a change.

<neilmilliken> ARIA no numbers

Lisa to suggest a call if there is a time and will be happy to add ARIA tags etc.

Lisa discussed how she has included the use of semantics - ARIA tags with explanations and standard HTML tags such as h2 to aid users

Lisa said this can be found under 11.3 in the main document but needs to re-structure

<ayelet_s> is anyone else having problems with audio quality?

Lisa is suggesting another issue paper to discuss calculations that are presented in one way but said in different ways allowing for personalisation - JSON

Lisa - User experience - what does the User Agent need to do - make sense via different settings in JSON - semantics have to work with it - ARIA - math tag etc.

<Lisa_Seeman> https://github.com/w3c/coga/blob/943ee0510a5ed91eb012492e45412b9d4f860e6b/issue-papers/links-buttons.html

<Lisa_Seeman> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2015May/0090.html

Lisa posted examples of ARIA functions such as number - cell phone, zip, credit card etc.

Lisa said use JSON to say how things should be read - example user experience

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Current_schedules

back to reviewing action items

August 2015 for draft of road map

Lis has said Gap analysis needs to now have content - from open actions.

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Gap_Analysis

Lisa asked if the available techniques could be placed in Gap Anaysis document on the wiki - recommendations for new success criteria, possible edits to WCAG and new requirements

Lisa asked for hands up for actions - level 2 headings under general

Lisa stressed that there will be slippage if the Gap Analysis is not completed.

<Tony_Doran> I have a draft of the distractions issue paper almost ready to circulate, but I think it needs restructured.

Lisa will send round an email for volunteers to work on the Gap Analysis

<neilmilliken> IAAP?

<Tony_Doran> Sorry my audio is bad - who and where?

Lisa mentined that IAAP would host the next face to face meeting in USA

<Lisa_Seeman> las vages

<Lisa_Seeman> TPAC

TPAC http://www.w3.org/2015/11/TPAC/

<Tony_Doran> Las Vegas will be cheaper than Japan budget wise.

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Gap_Analysis

IAAP in Las Vegas http://www.accessibilityassociation.org/access2015 October 21-23, 2015

TPAC 26-30 October 2015 - rather close to IAAP

<Tony_Doran> Sorry - need to drop off.

<ayelet_s> Lisa, when does this need to be done by?

Lisa went on to explain where each of the success technigues link to WCAG criteria - may be missing or does not cover the needs of coga users. - author needs to jot it down in the wiki as a success criteria - if not handled in WCAG and how it can be changed.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2015/06/01 17:08:46 $