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

Thursday, 28 July 2016

• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation John Foliot
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation David MacDonald
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Jeanne Spellman
• MATF Minutes 28 July 2016 Kim Patch
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Jeanne Spellman

Wednesday, 27 July 2016

• Re: Mobile Accessibility Taskforce Agenda Patrick H. Lauke
• Small PR on Mobile-A11y-TF-Note Patrick H. Lauke

Tuesday, 26 July 2016

• Mobile Accessibility Taskforce Agenda Kathy Wahlbin

Sunday, 24 July 2016

• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation David MacDonald

Thursday, 21 July 2016

• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation David MacDonald
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Patrick H. Lauke
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Kim Patch
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation David MacDonald
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Kim Patch
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Kim Patch
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Patrick H. Lauke
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation David MacDonald
• Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Kim Patch
• RE: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation Jonathan Avila
• Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation David MacDonald
• MATF Minutes 21 July 2016 Kim Patch
• Re: Mobile Accessibility Taskforce Agenda Alistair Garrison
• Re: Mobile Accessibility Taskforce Agenda Marc Johlic
• Re: Mobile Accessibility Taskforce Agenda Patrick H. Lauke

Tuesday, 19 July 2016

• Re: Mobile Accessibility Taskforce Agenda David MacDonald

Monday, 18 July 2016

• Re: Mobile Accessibility Taskforce Agenda Patrick H. Lauke
• 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) Patrick H. Lauke
• Mobile Accessibility Taskforce Agenda Kathy Wahlbin
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Alastair Campbell

Sunday, 17 July 2016

• Re: Summary of 2.1 discussion an attempt at consensus Patrick H. Lauke
• Re: Summary of 2.1 discussion an attempt at consensus Gregg Vanderheiden

Saturday, 16 July 2016

• Summary of 2.1 discussion an attempt at consensus David MacDonald

Friday, 15 July 2016

• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT David MacDonald
• Re: Minor tweak/correction to 2.5.1 David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Minor tweak/correction to 2.5.1 Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT 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 David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT 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 Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT 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 Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke

Thursday, 14 July 2016

• Re: Should we drop any WCAG 2 SCs in 2.1? David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT David MacDonald
• Re: Regrets for this week's call Alistair Garrison
• RE: Regrets for this week's call Kathy Wahlbin
• Re: Regrets for this week's call Detlev Fischer
• Re: Regrets for this week's call Patrick H. Lauke
• Regrets for this week's call Patrick H. Lauke

Wednesday, 13 July 2016

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

Tuesday, 12 July 2016

• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors Alastair Campbell
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT 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 Gregg Vanderheiden

Monday, 11 July 2016

• Re: [WebAIM] Color of link text Patrick H. Lauke
• Re: [WebAIM] Color of link text David MacDonald
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors Gregg Vanderheiden
• Re: [WebAIM] Color of link text Patrick H. Lauke
• Re: [WebAIM] Color of link text David MacDonald
• RE: 1100% may be physically impossible and still not achieve the results on smaller monitors Jonathan Avila
• Re: [WebAIM] Color of link text Patrick H. Lauke
• Re: [WebAIM] Color of link text David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Jonathan Avila
• Re: [WebAIM] Color of link text Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke

Sunday, 10 July 2016

• Re: [WebAIM] Color of link text Patrick H. Lauke
• Re: FW: [WebAIM] Color of link text Patrick H. Lauke
• Re: [WebAIM] Color of link text Gregg Vanderheiden
• Re: FW: [WebAIM] Color of link text Patrick H. Lauke
• Re: FW: [WebAIM] Color of link text Patrick H. Lauke
• FW: [WebAIM] Color of link text Jonathan Avila

Friday, 8 July 2016

• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT 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 David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT 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 Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Alastair Campbell
• Re: Jonathan's concern: Zoom in responsive drops content Detlev Fischer
• Re: Jonathan's concern: Zoom in responsive drops content Alastair Campbell
• Re: Jonathan's concern: Zoom in responsive drops content Patrick H. Lauke
• Re: Jonathan's concern: Zoom in responsive drops content Alastair Campbell

Thursday, 7 July 2016

• Re: Jonathan's concern: Zoom in responsive drops content Gregg Vanderheiden
• Re: Jonathan's concern: Zoom in responsive drops content Alastair Campbell
• MATF Minutes 7 July 2016 Kim Patch
• RE: Mobile Accessibility Taskforce Agenda Kathy Wahlbin
• Re: Mobile Accessibility Taskforce Agenda Patrick H. Lauke
• Re: Mobile Accessibility Taskforce Agenda Jeanne Spellman
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors Alastair Campbell
• Re: Mobile Accessibility Taskforce Agenda Henny Swan

Wednesday, 6 July 2016

• Re: Mobile Accessibility Taskforce Agenda Marc Johlic
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors David MacDonald
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors Léonie Watson
• Re: Jonathan's concern: Zoom in responsive drops content Alastair Campbell
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors Gregg Vanderheiden
• RE: 1100% may be physically impossible and still not achieve the results on smaller monitors ALAN SMITH
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors David MacDonald
• Re: 1100% may be physically impossible and still not achieve the results on smaller monitors Laura Carlson
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• 1100% may be physically impossible and still not achieve the results on smaller monitors ALAN SMITH
• Re: Jonathan's concern: Zoom in responsive drops content Alastair Campbell
• Re: Jonathan's concern: Zoom in responsive drops content Alastair Campbell

Tuesday, 5 July 2016

• Re: Jonathan's concern: Zoom in responsive drops content Gregg Vanderheiden RTF
• Re: Jonathan's concern: Zoom in responsive drops content Laura Carlson
• Re: Jonathan's concern: Zoom in responsive drops content Alastair Campbell
• Re: Jonathan's concern: Zoom in responsive drops content Gregg Vanderheiden
• RE: Mobile Accessibility Taskforce Agenda ALAN SMITH
• [regrets] Re: Mobile Accessibility Taskforce Agenda Shadi Abou-Zahra
• Mobile Accessibility Taskforce Agenda Kathy Wahlbin
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Gregg Vanderheiden RTF
• RE: Jonathan's concern: Zoom in responsive drops content Jonathan Avila
• Re: Should we require all functionality to be operable with pointer? Patrick H. Lauke

Monday, 4 July 2016

• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Gregg Vanderheiden RTF
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• Re: Should we require all functionality to be operable with pointer? Gregg Vanderheiden
• Re: Jonathan's concern: Zoom in responsive drops content 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 Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT David MacDonald
• Re: Should we require all functionality to be operable with pointer? Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Jonathan's concern: Zoom in responsive drops content Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Should we require all functionality to be operable with pointer? Gregg Vanderheiden
• Re: Jonathan's concern: Zoom in responsive drops content Gregg Vanderheiden
• RE: Should we require all functionality to be operable with pointer? Jonathan Avila
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Gregg Vanderheiden RTF
• Re: Jonathan's concern: Zoom in responsive drops content Patrick H. Lauke
• Re: Should we require all functionality to be operable with pointer? Gregg Vanderheiden RTF
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT 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 Patrick H. Lauke
• Re: Should we require all functionality to be operable with pointer? Patrick H. Lauke
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• Re: Should we require all functionality to be operable with pointer? David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• Re: Jonathan's concern: Zoom in responsive drops content Gregg Vanderheiden
• RE: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Jonathan Avila
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Gregg Vanderheiden
• RE: Jonathan's concern: Zoom in responsive drops content Jonathan Avila
• RE: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Jonathan Avila
• RE: Jonathan's concern: Zoom in responsive drops content Jonathan Avila
• RE: Jonathan's concern: Zoom in responsive drops content Jonathan Avila
• Re: Should we require all functionality to be operable with pointer? Gregg Vanderheiden
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Gregg Vanderheiden
• Re: Jonathan's concern: Zoom in responsive drops content Gregg Vanderheiden
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• Re: Jonathan's concern: Zoom in responsive drops content David MacDonald
• Re: Should we require all functionality to be operable with pointer? David MacDonald
• Re: Jonathan's concern: Zoom in responsive drops content Patrick H. Lauke
• Re: Jonathan's concern: Zoom in responsive drops content Patrick H. Lauke
• Re: Jonathan's concern: Zoom in responsive drops content Patrick H. Lauke
• Re: Jonathan's concern: Zoom in responsive drops content Steve Faulkner
• Re: Should we require all functionality to be operable with pointer? Patrick H. Lauke
• Should we require all functionality to be operable with pointer? David MacDonald
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT Patrick H. Lauke
• Re: Jonathan's concern: Zoom in responsive drops content Patrick H. Lauke
• Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT David MacDonald
• Jonathan's concern: Zoom in responsive drops content David MacDonald

Sunday, 3 July 2016

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

Friday, 1 July 2016

• Re: Conforming alternative for mobile should not be Desktop David MacDonald
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" Gregg Vanderheiden RTF
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" Patrick H. Lauke
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" Gregg Vanderheiden RTF
• Re: Conforming alternative for mobile should not be Desktop David MacDonald
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" Detlev Fischer
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" Patrick H. Lauke
• Re: Quick (hopefully) question about WCAG 2 glossary definition of "keyboard interface" Gregg Vanderheiden RTF
• Re: Conforming alternative for mobile should not be Desktop David MacDonald

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