W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2015

RE: Proposed mobile techniques for SC 3.1

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Mon, 20 Apr 2015 13:17:18 +0000
To: 'WCAG' <w3c-wai-gl@w3.org>
Message-ID: <BY2PR03MB272F975316A04DEBE03FDC69BE00@BY2PR03MB272.namprd03.prod.outlook.com>
Ø  +1 to David. The text constraints thingy……

I agree and I’ve documented this.  There are actually additional ways using fixed positioned content that developers can prevent access to page content when pinch zoom is used.  Thus, it makes sense to have a specific failure for viewport scale restriction but also an additional failure for other techniques that prevent text resize.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
Phone 703.637.8957
Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | Twitter<http://twitter.com/#!/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP>

From: Katie Haritos-Shea GMAIL [mailto:ryladog@gmail.com]
Sent: Monday, April 20, 2015 9:07 AM
To: 'David MacDonald'; 'Andrew Kirkpatrick'
Cc: 'WCAG'
Subject: RE: Proposed mobile techniques for SC 3.1

+1 to David. The text constraints thingy……☺



* katie *

Katie Haritos-Shea
Senior Accessibility SME (WCAG/Section 508/ADA/AODA)

Cell: 703-371-5545 | ryladog@gmail.com<mailto:ryladog@gmail.com> | Oakton, VA | LinkedIn Profile<http://www.linkedin.com/in/katieharitosshea/> | Office: 703-371-5545

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Monday, April 20, 2015 6:46 AM
To: Andrew Kirkpatrick
Cc: WCAG (w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>)
Subject: Re: Proposed mobile techniques for SC 3.1

We may have this but I want to þe sure we have a failure if the application overrides the pinch zoom or other native zooming capacity..


Cheers,

David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn<http://www.linkedin.com/in/davidmacdonald100>

www.Can-Adapt.com<http://www.Can-Adapt.com>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>

On Thu, Apr 9, 2015 at 12:51 PM, Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> wrote:
3.1 Keyboard Control for Touchscreen Devices

  *   Ensuring keyboard control for all functionality
  *   Ensuring touch access control for all functionality
  *   Ensuring that users are not trapped in content (using touch and keyboard)
  *   Defining the hover, focus, selected and touch (regular, long) states

     *   Use focus, hover and select states consistently and in a way that follows the respective platform conventions
Questions:

1)      Does each technique make sense to you?  (for now these are just titles, so it can be a challenge to be certain)

2)      Do you agree that the referenced success criteria is applicable to each suggested technique, or that the technique is applicable to the SC)?

3)      Do you think that there is another technique that this might better be an example for instead of a technique on its own?

4)      Do you think that each is likely to be sufficient or advisory?

5)      Are there other techniques that you can think of that address the SC in the mobile space?


Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe Systems

akirkpat@adobe.com<mailto:akirkpatrick@adobe.com>
http://twitter.com/awkawk

http://blogs.adobe.com/accessibility



Received on Monday, 20 April 2015 13:17:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:19 UTC