WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Native or web?


From: Jonathan Avila
Date: Jan 29, 2019 5:39PM

One trick I use to see if something is a webview or not is to look at the Voice Over rotor settings in iOS when focused on the content in question and see if there are HTML type rotor settings for links, lists, form controls, table, etc. If so you are in a webview.


Jonathan Avila, CPWA
Chief Accessibility Officer
Level Access
703.637.8957 office

Visit us online:
Website | Twitter | Facebook | LinkedIn | Blog

Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Patrick H. Lauke
Sent: Tuesday, January 29, 2019 9:35 AM
Subject: Re: [WebAIM] Native or web?

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

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.

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