RE: Agenda Oct 27

Ø  Perhaps we can discuss this one today...

I’d like to remind the group that people in the community are expecting us to address mobile accessibility issues in WCAG 2.1.  I believe this task force should focus on mobile issues as we have promised.

Jonathan

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Thursday, October 27, 2016 10:07 AM
To: alands289@gmail.com
Cc: Kathy Wahlbin; public-mobile-a11y-tf@w3.org; Shadi Abou-Zahra; Andrew Kirkpatrick; Joshue O Connor; jimallan@tsbvi.edu
Subject: Re: Agenda Oct 27

Perhaps we can discuss this one today...

https://github.com/w3c/wcag21/issues/3




Cheers,
David MacDonald



CanAdapt Solutions Inc.
Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd<http://twitter.com/davidmacd>

GitHub<https://github.com/DavidMacDonald>

www.Can-Adapt.com<http://www.can-adapt.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>

On Thu, Oct 27, 2016 at 8:11 AM, <alands289@gmail.com<mailto:alands289@gmail.com>> wrote:
Regrets for today.
I’m calling in to the Low Vision Task Force today to discuss an update I requested for one of their SCs.

For the Mobile Orientation SC I had one note:

Can we state that there is no “lose of content or functionality”? I’m not sure if the word “content” alone conveys that need. I have seen where the content is changed to accommodate a different display orientation with functions missing.

Thank you.

Alan

Sent from Mail for Windows 10

From: Kathy Wahlbin<mailto:kathyw@ia11y.com>
Sent: Monday, October 24, 2016 9:42 AM
To: Kathy Wahlbin<mailto:kathyw@ia11y.com>; public-mobile-a11y-tf@w3.org<mailto:public-mobile-a11y-tf@w3.org>
Cc: Shadi Abou-Zahra<mailto:shadi@w3.org>; Andrew Kirkpatrick<mailto:akirkpat@adobe.com>; Joshue O Connor<mailto:joshue.oconnor@cfit.ie>; jimallan@tsbvi.edu<mailto:jimallan@tsbvi.edu>
Subject: Agenda Oct 27


The next Mobile A11y Taskforce meeting will be this Thursday, Oct 27 at 11 AM Eastern (Length: 1 hour). For your local time, please use World Clock: http://tinyurl.com/lloxd6p<http://tinyurl.com/mobile-a11y-time>.

Please review the success criteria<https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/WCAG_2.1_Success_Criteria_Submission_Requirements> that is marked as reviewed by the taskforce.  If anyone has any concerns with any of these, please let us know.  These will be submitted to the WCAG working group the second week in November.

WebEx

·          JOIN WEBEX MEETING
https://mit.webex.com/mit/j.php?MTID=m523c9f623a4979f4952a9bb93531b909

Meeting number: 646 316 248

·          JOIN BY PHONE
+1-617-324-0000<tel:%2B1-617-324-0000> US Toll Number
Access code: 646 316 248

·          CCP:+16173240000x646316248#
Mobile Auto Dial:+1-617-324-0000<tel:%2B1-617-324-0000>,,,646316248#

IRC:

·          Channel: #mobile-a11y

·          Server: irc.w3.org<http://irc.w3.org>

·          Port: 6665

Agenda:

1.       Continuation of SC review - https://github.com/w3c/Mobile-A11y-Extension/tree/gh-pages/SCs , https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/WCAG_2.1_Success_Criteria_Submission_Requirements


-          M13 Orientation – https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Orientation


-          M7 No Focus Trap - https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m7.md


2.       Next steps and schedule

Kathy
CEO & Founder
Interactive Accessibility

T (978) 443-0798<tel:%28978%29%C2%A0443-0798>  F (978) 560-1251<tel:%28978%29%C2%A0560-1251>  C (978) 760-0682<tel:%28978%29%C2%A0760-0682>
E kathyw@ia11y.com<mailto:kathyw@ia11y.com>
www.InteractiveAccessibility.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.interactiveaccessibility.com_&d=CwMGaQ&c=jxhwBfk-KSV6FFIot0PGng&r=UK__SX18Mp9Fb6tIJfzgjkhM1qTux9WksegD3zR-Bss&m=Kyx2xjSikKdohzK4YYjpf6lkpNeSYzbcW2-3BWkmRfM&s=QvEa6SOOfiPYi3edgtQBne9UjZFUHulJz3xqkGwAu7o&e=>

NOTICE: This communication may contain privileged or other confidential information. If you are not the intended recipient, please reply to the sender indicating that fact and delete the copy you received. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.