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

ALAN SMITH

• RE: 1100% may be physically impossible and still not achieve the results on smaller monitors (Wednesday, 6 July)
• 1100% may be physically impossible and still not achieve the results on smaller monitors (Wednesday, 6 July)
• RE: Mobile Accessibility Taskforce Agenda (Tuesday, 5 July)

Alastair Campbell

• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 18 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Tuesday, 12 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Tuesday, 12 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 8 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 8 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Friday, 8 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Friday, 8 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Thursday, 7 July)
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Thursday, 7 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Wednesday, 6 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Wednesday, 6 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Wednesday, 6 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Tuesday, 5 July)

Alistair Garrison

• Re: Mobile Accessibility Taskforce Agenda (Thursday, 21 July)
• Re: Regrets for this week's call (Thursday, 14 July)

David MacDonald

• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 28 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Sunday, 24 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Re: Mobile Accessibility Taskforce Agenda (Tuesday, 19 July)
• Summary of 2.1 discussion an attempt at consensus (Saturday, 16 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Minor tweak/correction to 2.5.1 (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Should we drop any WCAG 2 SCs in 2.1? (Thursday, 14 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Thursday, 14 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Thursday, 14 July)
• Re: [WebAIM] Color of link text (Monday, 11 July)
• Re: [WebAIM] Color of link text (Monday, 11 July)
• Re: [WebAIM] Color of link text (Monday, 11 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 8 July)
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Wednesday, 6 July)
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Wednesday, 6 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Wednesday, 6 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Conforming alternative for mobile should not be Desktop (Friday, 1 July)
• Re: Conforming alternative for mobile should not be Desktop (Friday, 1 July)
• Re: Conforming alternative for mobile should not be Desktop (Friday, 1 July)

Detlev Fischer

• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Regrets for this week's call (Thursday, 14 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 8 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Friday, 8 July)
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" (Friday, 1 July)

Gregg Vanderheiden

• Re: Summary of 2.1 discussion an attempt at consensus (Sunday, 17 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Tuesday, 12 July)
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Monday, 11 July)
• Re: [WebAIM] Color of link text (Sunday, 10 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Thursday, 7 July)
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Wednesday, 6 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Tuesday, 5 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)

Gregg Vanderheiden RTF

• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Wednesday, 13 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Tuesday, 5 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Tuesday, 5 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" (Friday, 1 July)
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" (Friday, 1 July)
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" (Friday, 1 July)

Henny Swan

• Re: Mobile Accessibility Taskforce Agenda (Thursday, 7 July)

Jeanne Spellman

• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 28 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 28 July)
• Re: Mobile Accessibility Taskforce Agenda (Thursday, 7 July)

John Foliot

• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 28 July)

Jonathan Avila

• RE: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• RE: 1100% may be physically impossible and still not achieve the results on smaller monitors (Monday, 11 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 11 July)
• FW: [WebAIM] Color of link text (Sunday, 10 July)
• RE: Jonathan's concern: Zoom in responsive drops content (Tuesday, 5 July)
• RE: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• RE: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• RE: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• RE: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• RE: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• RE: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)

Kathy Wahlbin

• Mobile Accessibility Taskforce Agenda (Tuesday, 26 July)
• Mobile Accessibility Taskforce Agenda (Monday, 18 July)
• RE: Regrets for this week's call (Thursday, 14 July)
• RE: Mobile Accessibility Taskforce Agenda (Thursday, 7 July)
• Mobile Accessibility Taskforce Agenda (Tuesday, 5 July)

Kim Patch

• MATF Minutes 28 July 2016 (Thursday, 28 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• MATF Minutes 21 July 2016 (Thursday, 21 July)
• MATF Minutes 7 July 2016 (Thursday, 7 July)

Laura Carlson

• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Wednesday, 6 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Tuesday, 5 July)

Léonie Watson

• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Wednesday, 6 July)

Marc Johlic

• Re: Mobile Accessibility Taskforce Agenda (Thursday, 21 July)
• Re: Mobile Accessibility Taskforce Agenda (Wednesday, 6 July)

Patrick H. Lauke

• Re: Mobile Accessibility Taskforce Agenda (Wednesday, 27 July)
• Small PR on Mobile-A11y-TF-Note (Wednesday, 27 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation (Thursday, 21 July)
• Re: Mobile Accessibility Taskforce Agenda (Thursday, 21 July)
• Re: Mobile Accessibility Taskforce Agenda (Monday, 18 July)
• Re: 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) (Monday, 18 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 18 July)
• Re: Summary of 2.1 discussion an attempt at consensus (Sunday, 17 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Minor tweak/correction to 2.5.1 (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 15 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Thursday, 14 July)
• Re: Regrets for this week's call (Thursday, 14 July)
• Regrets for this week's call (Thursday, 14 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Tuesday, 12 July)
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors (Tuesday, 12 July)
• Re: [WebAIM] Color of link text (Monday, 11 July)
• Re: [WebAIM] Color of link text (Monday, 11 July)
• Re: [WebAIM] Color of link text (Monday, 11 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 11 July)
• Re: [WebAIM] Color of link text (Monday, 11 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 11 July)
• Re: [WebAIM] Color of link text (Sunday, 10 July)
• Re: FW: [WebAIM] Color of link text (Sunday, 10 July)
• Re: FW: [WebAIM] Color of link text (Sunday, 10 July)
• Re: FW: [WebAIM] Color of link text (Sunday, 10 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Friday, 8 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Friday, 8 July)
• Re: Mobile Accessibility Taskforce Agenda (Thursday, 7 July)
• Re: Should we require all functionality to be operable with pointer? (Tuesday, 5 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Re: Should we require all functionality to be operable with pointer? (Monday, 4 July)
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Monday, 4 July)
• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)
• Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT (Sunday, 3 July)
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" (Friday, 1 July)
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" (Friday, 1 July)

Shadi Abou-Zahra

• [regrets] Re: Mobile Accessibility Taskforce Agenda (Tuesday, 5 July)

Steve Faulkner

• Re: Jonathan's concern: Zoom in responsive drops content (Monday, 4 July)

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