W3C

- DRAFT -

Mobile Accessibility Task Force Teleconference

02 May 2014

Agenda

See also: IRC log

Attendees

Present
Gavin, Jeanne, Kathy_Wahlbin, Kim, kathleen, wuwei
Regrets
Alan, Jan
Chair
Kathy
Scribe
Kathy

Contents


<trackbot> Date: 02 May 2014

regrets Jan, Jonathan, Alan

<scribe> meeting: Mobile A11Y TF

http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Mobile_Resources

<scribe> Scribe: Kathy

Kathy: Review resources to see if there is anything else we should add

Kathleen: New Windows8 browser - Surfie

Kathy: What areas should we add to?

Kathleen: Blackberry, Firefox OS resources are limited
... Couldn't find any more information on that

http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Mobile_Resources

Gavin: Windows8 narrator - there is good blog posts

Kathy: Does anyone have time to help enter resources?

Kathleen: I can help

Kathy: Anything else we should do to get this ready for publication

Jeanne: Nothing else to change at this time

Kathy: Review of the WAI Mobile Accessibility

http://www.w3.org/WAI/mobile/Overview.html

Kathy: Review the page, let's discuss if there should be any updates to this page
... WCAG section does not address native applications

Jeanne: Mobile Taskforce work bullet was not easy to find

Kathy: WCAG statement should talk about native apps and hybrids apps

Kathleen: yes, should have a new sentence about native apps

<kathleen> This includes web content delivered on mobile devices through a browser and mobile applications.

Jeanne: under WAI is working to enhance technologies for mobile accessibility, mention WCAG and UAAG best practices and examples

<jeanne> jeanne drafts the material and says that it is still too soon to list them since we don't have any in draft mode.

Gavin: native applications and hybrid apps are not included
... web views on Android in native applications does not get read
... Would be good to have a list of known issues

Kathy: Things are changing fast so these issues would need to be updated regularly

Gavin: also dependant on device, OS etc

Jeanne: We should include the mobile resources
... where should it be on the page?

Kathy: Maybe in the WCAG section

WCAG (Web Content Accessibility Guidelines) covers web pages, web applications, native applications and hybrid applications, including content used on mobile devices.

WCAG (Web Content Accessibility Guidelines) covers web pages, web applications, native applications and hybrid applications. This includes web content delivered on mobile devices through a browser and mobile applications.

Jeanne - Make the list of options a bulleted list

Kathleen: like option 2

WCAG (Web Content Accessibility Guidelines) covers:

• web pages

• web applications

• native applications

• hybrid applications

This includes web content delivered on mobile devices through a browser and mobile applications.

<gavinevans> i like number 2

Kathy: How to incorporate the link about the resources

Kathleen: List under W3C addresses mobile accessibility

Kathy: Put a bullet about the mobile accessibility taskforce and link to the resources

Mobile Accessibility Resources and Best Practices summarizes the resources available about mobile accessibility pertaining to mobile design and development across different platforms and devices.

Kathleen: Under WAI-ARIA in the section WAI is working to enhance technologies for mobile accessibility we should note that it is not just web applications

<kathleen> It applies to web applications and to accessing websites with mobile devices and mobile applications.

Kathy: Three changes WCAG, adding list resources and the WAI-ARIA section
... I will send the list of changes to Jeanne
... Next week we will continue the discussion on mobile techniques

thanks!

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2014/05/02 15:01:22 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/zakim, +44 is really Gavin//
Succeeded: s/regrets?//
Found Scribe: Kathy
Inferring ScribeNick: Kathy

WARNING: No "Topic:" lines found.

Default Present: Kathy_Wahlbin, kathleen, Jeanne, wuwei, +44.179.281.aaaa, +1.617.435.aabb
Present: Gavin Jeanne Kathy_Wahlbin Kim kathleen wuwei
Regrets: Alan Jan
Agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Apr/0021.html
Found Date: 02 May 2014
Guessing minutes URL: http://www.w3.org/2014/05/02-mobile-a11y-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]