WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: desktop and mobile standards.

for

Number of posts in this thread: 6 (In chronological order)

From: Sean Murphy
Date: Mon, Jan 18 2016 10:41PM
Subject: desktop and mobile standards.
No previous message | Next message →

All,

Is there any standards for Mobile and desktop apps at the same standard as W3c? Also is there any standards for UI libraries used in desktop, mobile or web apps?

I am aware that MS and Apple have their own framework for accessibility. But I was wondering if there is any initiatives to try and have a single standard to cover accessibility for UI for everyone. As third-party vendors don't seem to follow any standards. Thus once someone uses a UI in their product and it doesn't have accessibility built in it or utilise the OS accessibility framework. The product becomes inaccessible.

Sean

From: Guy Hickling
Date: Tue, Jan 19 2016 6:14AM
Subject: Re: desktop and mobile standards.
← Previous message | Next message →

The information you want can be found on W3C's Web Accessibility Initiative
(WAI) pages, where they have a page specifically for mobiles
<https://www.w3.org/WAI/mobile/> which includes both mobile native apps and
web apps).

Essentially the WCAG is intended to cover all web pages and documents, and
native apps, regardless of the devices or technology used. Everything in
the WCAG is written generically as it is not limited to websites.

So it applies to mobile apps and other apps just as much as websites. The
page above says this: "WAI is working to enhance technologies for mobile
accessibility, including:* IndieUI
<http://www.w3.org/WAI/intro/indieui>; *(Independent
User Interface) is a way for user actions to be communicated to web
applications, including mobile applications. This will make it easier for
applications to work with a wide range of devices, including assistive
technologies.

Of course mobiles, and the apps on them, work differently - touchscreen
gestures being a difference of course, and that is all covered on pages
you'll see links for on the page above. Another useful page they have on
the subject, for instance, is at
https://www.w3.org/TR/mobile-accessibility-mapping/.

Of course much depends on the app vendors, and they should use the W3C's
UAAG (User Agent Accessibility Guidelines), which provides extra advice to
them, but still based on the WCAG. Unfortunately app vendors are just as
far behind on accessibility as millions of major websites, probably even
more so, which is the reason for the non-compliance you mention. I hope
this helps.

Regards,
Guy Hickling
http://www.enigmaticweb.com

From: Jennifer Sutton
Date: Tue, Jan 19 2016 7:39AM
Subject: Re: desktop and mobile standards.
← Previous message | Next message →

I apologize if I missed this link reference in an earlier message, but
here's a link to a note from the WG (from September of 2013) that may be
helpful:

Guidance on Applying WCAG 2.0 to Non-Web Information and Communications
Technologies (WCAG2ICT)


http://www.w3.org/TR/wcag2ict/



http://www.w3.org/TR/wcag2ict/

Best,
Jennifer

From: Sean Murphy
Date: Tue, Jan 19 2016 7:43PM
Subject: Re: desktop and mobile standards.
← Previous message | Next message →

Guy,


I will double check those links. If the standards are more focusing on apps with web content included, then that is fine. But I am more interested in UI standards for non-browser apps like programs that don't interact with the web or at least the app doesn't use any aspects of the web for the UI. Let me have a look and get back if I have more questions.

Sean
> On 20 Jan 2016, at 12:14 am, Guy Hickling < = EMAIL ADDRESS REMOVED = > wrote:
>
> The information you want can be found on W3C's Web Accessibility Initiative
> (WAI) pages, where they have a page specifically for mobiles
> <https://www.w3.org/WAI/mobile/> which includes both mobile native apps and
> web apps).
>
> Essentially the WCAG is intended to cover all web pages and documents, and
> native apps, regardless of the devices or technology used. Everything in
> the WCAG is written generically as it is not limited to websites.
>
> So it applies to mobile apps and other apps just as much as websites. The
> page above says this: "WAI is working to enhance technologies for mobile
> accessibility, including:* IndieUI
> <http://www.w3.org/WAI/intro/indieui>; *(Independent
> User Interface) is a way for user actions to be communicated to web
> applications, including mobile applications. This will make it easier for
> applications to work with a wide range of devices, including assistive
> technologies.
>
> Of course mobiles, and the apps on them, work differently - touchscreen
> gestures being a difference of course, and that is all covered on pages
> you'll see links for on the page above. Another useful page they have on
> the subject, for instance, is at
> https://www.w3.org/TR/mobile-accessibility-mapping/.
>
> Of course much depends on the app vendors, and they should use the W3C's
> UAAG (User Agent Accessibility Guidelines), which provides extra advice to
> them, but still based on the WCAG. Unfortunately app vendors are just as
> far behind on accessibility as millions of major websites, probably even
> more so, which is the reason for the non-compliance you mention. I hope
> this helps.
>
> Regards,
> Guy Hickling
> http://www.enigmaticweb.com
> > > >

From: Joseph Sherman
Date: Tue, Jan 19 2016 8:27PM
Subject: Re: desktop and mobile standards.
← Previous message | Next message →

Have you seen the article:

mattgemmell.com/accessibility-for-iphone-and-ipad-apps/<http://mattgemmell.com/accessibility-for-iphone-and-ipad-apps/>;


Joseph
On Jan 19, 2016 9:43 PM, Sean Murphy < = EMAIL ADDRESS REMOVED = > wrote:
Guy,


I will double check those links. If the standards are more focusing on apps with web content included, then that is fine. But I am more interested in UI standards for non-browser apps like programs that don't interact with the web or at least the app doesn't use any aspects of the web for the UI. Let me have a look and get back if I have more questions.

Sean
> On 20 Jan 2016, at 12:14 am, Guy Hickling < = EMAIL ADDRESS REMOVED = > wrote:
>
> The information you want can be found on W3C's Web Accessibility Initiative
> (WAI) pages, where they have a page specifically for mobiles
> <https://www.w3.org/WAI/mobile/> which includes both mobile native apps and
> web apps).
>
> Essentially the WCAG is intended to cover all web pages and documents, and
> native apps, regardless of the devices or technology used. Everything in
> the WCAG is written generically as it is not limited to websites.
>
> So it applies to mobile apps and other apps just as much as websites. The
> page above says this: "WAI is working to enhance technologies for mobile
> accessibility, including:* IndieUI
> <http://www.w3.org/WAI/intro/indieui>; *(Independent
> User Interface) is a way for user actions to be communicated to web
> applications, including mobile applications. This will make it easier for
> applications to work with a wide range of devices, including assistive
> technologies.
>
> Of course mobiles, and the apps on them, work differently - touchscreen
> gestures being a difference of course, and that is all covered on pages
> you'll see links for on the page above. Another useful page they have on
> the subject, for instance, is at
> https://www.w3.org/TR/mobile-accessibility-mapping/.
>
> Of course much depends on the app vendors, and they should use the W3C's
> UAAG (User Agent Accessibility Guidelines), which provides extra advice to
> them, but still based on the WCAG. Unfortunately app vendors are just as
> far behind on accessibility as millions of major websites, probably even
> more so, which is the reason for the non-compliance you mention. I hope
> this helps.
>
> Regards,
> Guy Hickling
> http://www.enigmaticweb.com
> > > >

From: Guy Hickling
Date: Wed, Jan 20 2016 9:57AM
Subject: Re: desktop and mobile standards
← Previous message | No next message

Sean,

Yes, let us know how useful it is, especially for sugggesting any decent
techniques for apps.

Regards,
Guy