Design Clickable Objects appear Clickable

Kathleen, Alan and I met on Monday to discuss #13 from the survey:
https://www.w3.org/2002/09/wbs/66524/20140512_survey/results#xq14

Some of the issues discussed in last Friday's meeting were:
* not testable as written
* inconsistency of button appearance across different platform standards
* whether it was really a usability issue and not an accessibility issue

We agreed that this was important for people with low vision and for 
people with cognitive disabilities, so it is an accessibility issue. We 
agreed that there were no common standards for identifying clickable 
objects across platforms, and it inappropriate for us to determine those.

We agreed that UAAG 1.3.1 and 1.3.2 cover this:
http://www.w3.org/WAI/UA/IMPLEMENTING-UAAG20/#sc_131
UAAG defines classes of objects that require custom appearance and 
options that the user agent should give to users to customize those 
objects.

We recommend classifying this as a Best Practice that refers to UAAG 
1.3.1 and 1.3.2 and quotes the mobile examples in Implementing UAAG for 
these success criteria.  The Best Practice technique for our purposes is 
that the author has to code the page or app so that the buttons or input 
fields are semantically buttons or inputs, so their appearance can be 
modified by the platform or user agent settings.

Minutes of our discussion are at:
http://www.w3.org/2014/06/02-mobile-a11y-minutes.html

Received on Monday, 2 June 2014 14:43:22 UTC