See also: IRC log
Jason: Open to both quick urgent
issues and longer term considerations to communicate the to APA
WG
... EO may be able to coordinateto dessimante findings of
RQTF
<yatil> Work Plan: https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Work_Plan
Jason: Several major topic on the
WP, including authentication on the web and how to make it
accessible.
... most raise accessibility issues.
... Authentication of great interest to us as well as other WG
and TF. Third was the issue of CAPTCHA will update the
previously written doc.
... RQTF will help with that. Fial piece was the work item from
previous research group was developing guidance for
accessibility aware research. How to integrate accessibility
into their own research projects. Write some guidance for other
researchers.
... these are current issues and ready to accept topics from
other working groups and TFs who need accessibility
considerations.
Sharron: Reveiw of other research, such as COGA research?
Jason: More likely to connect the
work to the right reviewers.
... connect to those with specialized cognitive knowledge.
Mark: Doing outreach for WCAG and ARIA daily. Developers, smart developers often do very dumb things in applying accessibility. Makes me wonder, what is the problem, why do developers have so much trouble understanding and applying accessibility techniques?
Sharron: Have you seen the tutorials?
Mark: Yes, and they are OK but not enough, inadequate to help developers understand where along the route they need to consider accessibility - the concept of "born accessible"
https://www.w3.org/blog/wai-components-gallery/
Mark: Developing internal
training materials geared toward how we need to address
accessibility internal.
... many forms tutorials are geared toward commercial kinds of
form interactions. We build test and assessment questions, need
more information about the user.
... math and complex science questions have very specific
requirements to ensure they can demonstrate knowledge of
subject not the ability of the AT or the use of complex
computer interface.
... have been advocating for standard implementations of common
formats like multiple choice, etc faciliatate ease of use and
common expectations so that they operate in the same way and
the AT learner does not have to relearn each time. Have
prototyped a common best practice for multiple choice that
announces itself in that way with a unified keyboard
behavior.
... one of the things important to assessment is pronunciation,
ensuring that speech synthizer says words in same way as a
teacher would. SSML could solve this problem, takes care of all
of it if it is supported by AT vendors.
... more recently SSML is being supported. Increasing vendor
support woould be very useful.
... would like support for exisiting standards that could help
improve user experience. CSS3 spoken word module would do the
same if more widely supported.
Eric: With Siri and others supporting SSML it should become easier.
<yatil> SSML: http://www.w3.org/TR/speech-synthesis/
Mark: Defining the different roles and how they can contribute to accessibility
http://w3c.github.io/wai-quick-start/
Shadi: Accessibility self-assessment?
Mark: we are developing a
learning tool with built in assessment cabability for
developers. Write some code and use of a built in checker to
assess how complete is the solution and give experience and
feedback to developers trying to meet accessibility
requirements.
... totally commited to standards based solutions but can't
always wait - for example descriptions of images
... when back home in a week and a half will talk ot a staffer
who may be interested.
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/ablet o coordinae /able to coordinate/ Succeeded: s/present +Jason White// Succeeded: s/present +Sharron// Succeeded: s/present +Gustavo// Succeeded: s/Seri/Siri/ Succeeded: s/accessiiblity/accessibility/ Succeeded: s/accessiiblity/accessibility/ Succeeded: s/(although intention doesn't always provide results :-)/ / Succeeded: s/I like your idea that if have specific focus easier to recruit people to do it/ / Succeeded: s/Sharron, Brent, eric, shadi -- want to get on the phone after this for a debrief?/ / Succeeded: s/is there a phone in the EOWG room... or I guess can use webex on someone's laptop// Succeeded: s/There is a phone in the EO room/ / Succeeded: s/ummmm// Succeeded: s/thanks!// No ScribeNick specified. Guessing ScribeNick: Sharron Inferring Scribes: Sharron Present: Sharron Jason_White Gustavo EricE Markku_Häkkinen WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 20 Sep 2016 Guessing minutes URL: http://www.w3.org/2016/09/20-eo-minutes.html People with action items:[End of scribe.perl diagnostic output]