Re: Question on Active state styling for links

I'm challengesd by this topic when I consider lists of items like onewould
find in the settings section of any mobile device. How do we apply the
thoughts suggested in this discussion to the numerous lists of topics and
items that are actually buttons that open either settings directly or other
pages of links of other setting values. These may all be selectable to
perform a function or link to another page to perform a function. Alan
On Jul 14, 2015 1:29 PM, "Jim Allan" <jimallan@tsbvi.edu> wrote:

> +1 to Jonathan
> having the link or button or what ever control change in some manner is
> useful. Color change for the default action (opening link, activating
> button) lets the user know that they "hit the target". The color change is
> also useful so I know I am on "target" when doing a "long press" or "mobile
> hover" to make to context menu open.
> I sometimes wish the screen would blink or something when I press on a
> small link/button...even though the color changes, I cannot see it because
> my finger tip more than covers the element area.
>
> Jim
>
> On Tue, Jul 14, 2015 at 7:57 AM, Jonathan Avila <
> jon.avila@ssbbartgroup.com> wrote:
>
>> > As Jeanne put it: "Is there a particular value in providing alternative
>> styling for :active links in the mobile environment? That is, when the link
>> is touched or clicked that there is a visible change in appearance."
>>
>> Yes, as I said in my first response and as Kim reaffirmed there is value
>> in that feedback.  It's a common native app paradigm for an interactive
>> element to change when you touch it.  For example, on my iPhone when I
>> touch a home screen icon it gets darker letting me know that I did indeed
>> activate it to launch the app.  This is especially helpful in situations
>> where there is no other immediate response and you have that visual
>> feedback to know that your touch was at least acknowledged.  As I said
>> before in my opinion it doesn't appear to be a current WCAG failure -- but
>> yes IMO it has value.  I think this is evidenced by the touch state
>> properties that exist in the mobile platforms.
>>
>> Jonathan
>>
>> --
>> Jonathan Avila
>> Chief Accessibility Officer
>> SSB BART Group
>> jon.avila@ssbbartgroup.com
>>
>> 703-637-8957 (o)
>> Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
>>
>>
>> -----Original Message-----
>> From: Shawn Henry [mailto:shawn@w3.org]
>> Sent: Tuesday, July 14, 2015 8:21 AM
>> To: Jonathan Avila; MATF; wai-eo-editors
>> Cc: Kevin White
>> Subject: Re: Question on Active state styling for links
>>
>> Hi Jonathan,
>>
>> A bit more clarification: In <
>> http://w3c.github.io/wai-quick-start/designing.html#ensure-that-interactive-elements-are-easy-to-identify>
>> the item in question is "touch-screen activation" and "Touch or click on
>> link" -- that is, providing feedback that a link *is being activated*
>> (rather than that it is activate-able (aka affordance).
>>
>> As Jeanne put it: "Is there a particular value in providing alternative
>> styling for :active links in the mobile environment? That is, when the link
>> is touched or clicked that there is a visible change in appearance."
>>
>> Best,
>> ~Shawn
>>
>>
>> On 7/10/2015 6:36 AM, Jonathan Avila wrote:
>> >> I think that is an issue here -- that is, if we keep that guidance,
>> >> we might need to clarify that it's not a requirement.
>> >
>> > Shawn,  I assume the idea is that this would be WCAG advisory/best
>> > practice technique bout could be a potential WCAG Mobile Extension
>> > success criteria/requirement.  We need to categories the techniques
>> > are compiling based on survey results from the TF.  We started this
>> > process last year but did know an extension was possible at that time.
>> >
>> >>> Here is the example from EO  --the "Getting Started Tips",
>> >>> specifically on "Ensure interactive elements are easy to
>> >>> identify":
>> >>> -http://w3c.github.io/wai-quick-start/designing.html#ensure-interact
>> >>> ive-elements-are-easy-to-identify
>> >
>> >>>
>> > After looking again at the link Jeanne sent -- it would appear that
>> > this particular item is a separate best practice/advisory item that we
>> > had also noted by the group.  Discoverability -- that is does the item
>> > appear to be interactive.  That to me is a separate but related
>> > concept of "does it look like something I can touch or click, etc."
>> >
>> > Jonathan
>> >
>>
>> -------- Forwarded Message --------
>> Subject: Question on  Active state styling for links
>> Resent-Date: Wed, 08 Jul 2015 13:52:18 +0000
>> Resent-From: wai-eo-editors@w3.org
>> Date: Wed, 08 Jul 2015 09:52:14 -0400
>> From: Jeanne Spellman <jeanne@w3.org>
>> To: MATF <public-mobile-a11y-tf@w3.org>
>> CC: Michael Cooper <cooper@w3.org>, Kevin White <kevin@w3.org>,
>> wai-eo-editors <wai-eo-editors@w3.org>
>>
>> I received a question that originated with the EO working group where
>> they would like an opinion from the Mobile Accessibility Task Force.
>>
>> Is there a particular value in providing alternative styling for :active
>> links in the mobile environment? That is, when the link is touched or
>> clicked that there is a visible change in appearance.
>>
>> An informal opinion from the WCAG WG is that WCAG doesn't address the
>> need for alternative styling -- outside of issues of how it is styled, e.g.
>> for color and contrast.  Is there a particular value from the mobile
>> perspective that merits creating a technique for this?
>>
>> Here is the example from EO  --the "Getting Started Tips", specifically
>> on "Ensure interactive elements are easy to identify": -
>> http://w3c.github.io/wai-quick-start/designing.html#ensure-interactive-elements-are-easy-to-identify
>>
>>
>> Thanks,
>>
>> jeanne
>>
>>
>>
>>
>>
>
>
> --
> [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>Jim Allan,
> Accessibility Coordinator
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>