target size

I would like to see us get something into WCAG 2.1 on target size. Mobile
guidelines address it and mobile accessibility guidelines such as the BBC
also address it. However, we have a higher bar on testability and applying
across technologies etc..  I don't think we should punt this SC to Silver,
because the primary reason given for a WCAG update was mobile, and this is
a fundamental issue with mobile. It would be a huge hole to ignore it
because we couldn't come to consensus on this version.

There seem to be 2 ways we could approach it here in 2017

1) Make a wide SC with exceptions and not too hard sizes to implement
applicable to all content and all views.
2) Use the viewport size as a threshold with larger target requirements and
fewer exceptions on screen sizes that are more likely to be used with a

I'm in favour of the 2nd solution, viewport size.  However, I understand
objections to this approach:
1. many feel there is "no such thing as mobile" and
2. target size is important on big screens too
3. its hard to determine screen size because of resolutions ... etc

So I'm ok with coming to a consensus on the first item. I think we're close
to consensus on the first one. But to get consensus I think it needs to be
easier for menus (22x22 minimum) and an exception for

The size of the target at the default viewport size is at least 44 by 44
CSS pixels for pointer inputs except where:

- a mechanism is available to change the size of the target
- the target is available through an equivalent link or control that is at
least 44 by 44 CSS pixels
- the target cannot be 44 by 44 CSS pixels due to mandatory layout
- the target is an in-page link
- the target is embedded in a block of text or is part of group of
navigation links
- the target is controlled by the user agent and cannot be modified

David MacDonald

*Can**Adapt* *Solutions Inc.*
Mobile:  613.806.9005


GitHub <> <>

*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy

Received on Wednesday, 12 April 2017 18:31:55 UTC