<Kathy> grouped targets with more than 5 items have at least one dimension that is 44 pixels and the other is at least 22 pixels

Understanding Documentation and Techniques: Target Size

Kathy: addressing people's concerns about touch target size– at AAA we shouldn't have it in there because were asking people to do significant changes and I can't accept the AAA requirement. Some people saying that's what AAA is all about
... want to see if mobile group is okay with putting this in with a note. Groups of targets with more than five items 44 x 22. That's the note for AA, AAA will go in without the note – that's the proposal

Marc: thinking of little tiny controls on the phone. When links got introduced that made sense, many people want to access link also. Think of myself, I'm constantly doing the pinch. is the touch target size easily solved by doing the pinch?

Kathy: low vision user film talking about when he uses zoom and when he needs font size increase
... significant usability issue if were talking about scrolling versus size. Also looking at how users are using magnification – generally magnifying the screen then interacting with it and doing something else. I'm okay with this minimum – that's from my user research and talking to Kim two – horizontal scroll, vertical scroll can be a significant barrier as well. We are battling two...
... different things. I do think the user behavior with touchscreens especially when you've got groups of things – maybe not so much in form control, but just links. I think the behavior is exactly what you do Marc right now on the phone – that applies to people with low vision and mobility impairments as well

Marc: I'm struggling with how far this needs to go. I was more in favor of saying don't lock the viewport and having a target size of X. To me the bigger problem is when you lock the viewport on someone so they can't do the zoom

Kathy: right now mobile is overwriting that – so it's less of an issue because the manufacturers have just said we are going to ignore it anyway

Marc: I'm always reading news stuff and I'm trying to zoom it and I can't zoom it. It might be when it's in their own little browser rather than the chrome browser on my device – maybe it's a hybrid app using the browser. That's what I find frustrating – they take away my ability to zoom in. That's more frustrating than the actual target size. If I can zoom in I can hit the target

Kathy: we have to think about the user experience to when you can magnify and then interact. Two different scenarios. When you can see more things on the screen versus less things on the screen. User impact overall usability, but we're talking about making it more difficult for users with disabilities so it's proportionately different from a user experience standpoint which is kind of the...
... benchmark. That's where I'm breaking this out now – certain things we can expect the user to do and other areas where as Shad mentioned one of the big issues for him in forms you don't want to zoom to lose the context of the page. Other contexts where we do have a group it's okay – less of an impact to magnify. That's why I think when we are talking about this we are generally okay just...
... because the end-user is going to do different behaviors based on what they are doing

next steps

Writing understanding for the SC's. Also, if you have thoughts on beefing up understanding, additional use cases etc., keep adding to the Github Issues to keep everything in one place and make it easier for whoever takes up the task of writing understanding.

Question about referencing existing comments in Github issues thread – in the header of the comment you want to reference click on the time (e.g. 6 hours ago). Clicking changes the address in the browser address bar to reference that comment in the thread. So you can then copy the address bar link for the direct link.