E-mail List Archives
Re: Native or web?
From: Barry Hill
Date: Jan 29, 2019 9:50AM
- Next message: glen walker: "Re: Accessible, flexible select box"
- Previous message: glen walker: "Re: Native or web?"
- Next message in Thread: Patrick H. Lauke: "Re: Native or web?"
- Previous message in Thread: glen walker: "Re: Native or web?"
- View all messages in this Thread
Thanks, Joe and Patrick.
Joe, that's where I was thinking for the app, but I was concerned that it
was an app written for IOS and probably uses java to emulate the gestures
used by a IOS device, but I'm concerned whether or not it will use the VO
gestures. I can't get my hands on it to test it.
Patrick, you've hit the nail on the head there. It is indeed cross-compiled
and packaged as a native app.
As this app is only to be used on IOS devices, could it be that some of the
WCAG 2.1 guidelines go too far, even for level A? Yes, the new ones under
2.1 for mobile will be relevant, but wouldn't the IOS mobile guidelines be
more useful?
Cheers
B
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
Patrick H. Lauke
Sent: Tuesday, January 29, 2019 2:35 PM
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] Native or web?
On 29/01/2019 13:37, Barry Hill wrote:
> If an app is written using html ostensibly for IOS use only, which
> guidelines would be most appropriate, WCAG 2.1 or mobile accessibility
> guidelines? I think the pertinent question is, is it a native or a web
app?
The more pertinent question here would be: when you say it's written using
HTML, do you mean it's then packaged/cross-compiled, running inside a native
app shell with a webview, or literally loaded in Safari?
If the latter two, it's still web content shown by a web user agent (in the
case of the webview, a very cut-down one in terms of user controls, but a
user agent nonetheless). If it's cross-compiled and packaged (using
something like PhoneGap), the lines get a bit more blurred (though I believe
fundamentally it's still running inside a webview for the most part, so
still web content).
Also note that there aren't really separate/different mobile accessibility
guidelines per se. There is guidance on how to apply/interpret WCAG 2.0 (not
sure if there's a 2.1 version out yet) for mobile apps, but fundamentally
the (tech agnostic) success criteria remain the same.
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
http://webaim.org/discussion/archives
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
- Next message: glen walker: "Re: Accessible, flexible select box"
- Previous message: glen walker: "Re: Native or web?"
- Next message in Thread: Patrick H. Lauke: "Re: Native or web?"
- Previous message in Thread: glen walker: "Re: Native or web?"
- View all messages in this Thread