- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Fri, 18 Dec 2015 15:18:34 +0000
- To: "Richards, Jan" <jrichards@ocadu.ca>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
On 18/12/2015 15:09, Richards, Jan wrote:
> I like CSS pixels as a Sufficient technique, but if that's the SC wording then:
> (1) it rules out other approaches (e.g. just using <button> and letting the UA do the sizing) and
Well yes...as the default size that a UA decides to give to a <button>
or similar may not be sufficient. So adding CSS to explicitly say
button { width: 50px; height: 50px; }
doesn't seem unreasonable to me.
> (2) it can cause problems with text resizing that wouldn't happen if a relative unit (e.g. em) was used.
If authors are using measures other than CSS pixels, then they'd have to
check the actual rendered size in pixels using devtools, or some
calculation. This would be no different from things like "large text" in
WCAG being oddly defined in points, requiring authors to work out what
point size their text is (as they're either using px or em, for the most
part).
If the user has changed the default text size of their UA, would it not
conceptually fall under the same as "except when the user has reduced
the default scale of content" (the second part of the SC wording, as per
http://kwahlbin.github.io/Mobile-A11y-Extension/#touch-navigation)?
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Friday, 18 December 2015 15:18:57 UTC