Re: MATF SCs with no manager, and SCs not yet having Pull request.

Hi David, 
thanks for reminding us all of the time pressure and for giving us this status.


#60 Target size = (@awkawk) - in the last MATF telco, consensus was that we should hold on for this - we did not think that the availabiltiy of zoom woud be reason enough not to mandate a minimum target size. We agreed that we can reduce size to 44px (iOS recommendations) and have an exception for links in inline text (horizontal dimension >= 44 px, vertical dimension 22px (maybe even less) so the issue of overlapping links in inline text is reduced. We wouls still need an exception for inline text links that have to bew short (say, three footnote links 1), 2), 3) after a sentence which would be to short to make the 44px horizontal target.
@awkawk, would you create a pull request for this one even if you personally think we don’t need it?

#67 Device sensors (@mraccess77) - Jon, will you create a pull request for this?

#66 Pointer input with additional sensors (not assigned) - seems an easy target, but perhaps not vital to include

#63 Touch with assistive technology (@joshueoconnor)- people seem to agree that as it is unclear whether 2.1.1 can be tweaked we should create a pull request on this - Joshue, will you?

#71 Non-interference of AT (@joshueoconnor) reading through issue comments there seems to be some consensus that this may not be pushed now and may be covered by conformance req 4 and may be addressed in new text in Understanding 2.1.1 - so maybe not push this now?

#70 Orientation (@marcjohlic)- there has been discussion but overall agreement to advancve this SC with some wording changes (e.g. noting that element order does not need to be the same in both orientatons but consistent in the respective chosen orientation). Marc, will you be able to create a pull request for this in time?

#61 Pointer Gestures (not assigned) - I think this is pretty straight-forward and an important requirement for touch users having difficulties with complex multi-finger touch gestures. It maz get a lot of oushback put it woud bre goof to expose it foir comments. DavidMcDonald wrote: This has no SC manager... I can submit this proposal. Time is running out. Will you Daivd?

#69 Single key shortcut alternative (@DavidMcDonald) there seems to be consensus that this should go forward, maybe with changes suggested by Davd - good to get wider feedback on this. Will you create the pull request, David?

#68 Speech input (not assigned) - a lot of discussion on the issue what the author can do about this problem, whether it is more an AT issue, whether it is actually covered elsewhere or should be phrased differently - not sure whether this should go forward

Detlev


> On 13 Feb 2017, at 21:24, David MacDonald <david100@sympatico.ca> wrote:
> 
> If we want into the first draft I think we should be making some pull requests... and getting our SC into the wider group discussion. There are 30 PR already submitted... I've done 2 of them #2 Change of content and #65 accidental activation.
> 
> I can do a PR on #69 single character shortcuts if necessary... it's got no SC manager...
> 
> 
> 
> 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 Mon, Feb 13, 2017 at 3:06 PM, David MacDonald <david100@sympatico.ca <mailto:david100@sympatico.ca>> wrote:
> 61 <https://github.com/w3c/wcag21/issues/61> Pointer gestures
> 69 <https://github.com/w3c/wcag21/issues/69> Single key shortcut alternative
> 68 <https://github.com/w3c/wcag21/issues/68> Speech Input
> 
> 
> 
> 
> 
> ​MAFT SCs which have not yet been submitted for Pull Request... (the cut off is around the corner..)
> ​
> 
> 60 <https://github.com/w3c/wcag21/issues/60> Target Size
> 
> 
> 67 <https://github.com/w3c/wcag21/issues/67> Device sensors
> 66 <https://github.com/w3c/wcag21/issues/66> Pointer inputs with additional sensors
> 63 <https://github.com/w3c/wcag21/issues/63> Touch with Assistive Technology
> 71 <https://github.com/w3c/wcag21/issues/71> Non-interference of AT
> 70 <https://github.com/w3c/wcag21/issues/70> Orientation
> 
> 
> 61 <https://github.com/w3c/wcag21/issues/61> Pointer gestures
> 69 <https://github.com/w3c/wcag21/issues/69> Single key shortcut alternative
> 68 <https://github.com/w3c/wcag21/issues/68> Speech Input
> ​
> 
> ​I tried to clean up #69. Suggested this
> 
> "Single character shortcuts are not the only way activate a control, unless a mechanism is available to turn them off or remap them to shortcuts with two or more characters."
> 
> 
> 
> Glossary
> Single character shortcut: Mechanism added to the content which triggers a control using only one character on the keyboard.
> 
> Cheers,
> David MacDonald
>  
> CanAdapt Solutions Inc.
> Tel:  613.235.4902 <tel:(613)%20235-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>