- From: Detlev Fischer <detlev.fischer@testkreis.de>
- Date: Fri, 28 Apr 2017 17:44:14 +0200 (CEST)
- To: john.foliot@deque.com, acampbell@nomensa.com
- Cc: w3c-wai-gl@w3.org
> > The Mobile Accessibility Task Force proposals cover both "web" content, "web apps" and Native apps > > I don’t think they have tried to cover native apps (MATF – please correct me if you did?!) If memory serves, for of many the SCs that we were initially working on, it did not matter whether it would be web or somewhere on the range from web to native that Alastair has drawn up. Success Criteria like 3.2.6 Accidental Activation as well as the proposed #60 Target size, #63 Touch with Assistive Technology, #66 Pointer inputs with additional sensors, #67 Device sensors, 70 Orientation seem to apply to both web and native. I think we were working under the assumption that we would cover aspects that were related to the form factor: small screen, other sensors, (often) lack of physical keyboard, and especially touch / gesture interaction. Then thankfully Patrick entered the fray and made the point that the desktop / mobile distinction is flawed. SCs like Target size that first seemed straightforward then really got difficult by having to take into account differnet input modalities and the fluidity of responsive web design triggered both by viewport sizes AND the UA zoom function. I join the ranks of those who would like more clarity on the definition of (web) content that WCAG 2.1 and future versions will apply to (backed by examples). WCAG2ICT and EN 301 549 assume that a subset of WCAG can also apply in parts to general software (native apps).
Received on Friday, 28 April 2017 15:44:44 UTC