public-mobile-a11y-tf@w3.org from July 2016 by subject

1100% may be physically impossible and still not achieve the results on smaller monitors

[regrets] Re: Mobile Accessibility Taskforce Agenda

[WebAIM] Color of link text

ACTION-55: Update github version http://w3c.github.io/mobile-a11y-extension/ to include pointer, add definition of coarse/fine etc as per mq lvl 4 etc (Mobile Accessibility Task Force)

Conforming alternative for mobile should not be Desktop

Jonathan's concern: Zoom in responsive drops content

MATF Minutes 21 July 2016

MATF Minutes 28 July 2016

MATF Minutes 7 July 2016

Minor tweak/correction to 2.5.1

Mobile Accessibility Taskforce Agenda

Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT

Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation

Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface"

Regrets for this week's call

Should we drop any WCAG 2 SCs in 2.1?

Should we require all functionality to be operable with pointer?

Small PR on Mobile-A11y-TF-Note

Summary of 2.1 discussion an attempt at consensus

Last message date: Thursday, 28 July 2016 19:52:27 UTC