RE: ‘Functional Performance-like’ SC for WCAG 2.1?

I agree Jason with the sentiment, but the SC are the requirements of WCAG so the 12 Guidelines and 4 Principles do not get built in or tested for….

 

​​​​​

 

 

 

* katie *

 

Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)

 

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

 

From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Thursday, July 21, 2016 1:03 PM
To: Katie Haritos-Shea GMAIL <ryladog@gmail.com>; 'WCAG WG' <w3c-wai-gl@w3.org>
Subject: RE: ‘Functional Performance-like’ SC for WCAG 2.1?

 

These are interesting thoughts, Katie – see responses below.

 

From: Katie Haritos-Shea GMAIL [mailto:ryladog@gmail.com] 
Sent: Thursday, July 21, 2016 12:45 PM

The advantage of using them are that they would/could provide coverage for those instances of modalities and interactions that are either unknown (not developed yet) or very hard to write a SC for. Because being too specific related to technologies ends up limiting a SC. An example would be from a question I had this week: what SC would cover a web banking app that required the users to take a picture of a check – and provides visual cues of when the check is in the right place in the viewer? – it would need perhaps verbal instructions also (move it to the left a little). 

[Jason] Yes, it would, but in the absence of those instructions it would seem to be a straightforward violation of Guideline 1.1 in WCAG 2. The non-text content is dynamic (it changes depending on the user’s positioning of the camera), but it’s still non-text content; and the solution is still to provide text alternatives.

 

Another advantage would be for those countries that don’t have an ICT Accessibility standard with Functional Performance Criteria.

 

​​​​​So these are suggested starting blobs…..

 

1.      Without Vision.  Where a visual mode of operation is provided, there must be at least one mode of operation that does not require user vision.

2.      With Limited Vision. Where a visual mode of operation is provided, there must be allowed at least one mode of operation that magnifies, one mode that that reduces the field of vision required, and one mode that allows user control of contrast. 

3.      Without Perception of Color. Where a visual mode of operation is provided, there must be at least one mode of operation that does not require user perception of color. 

4.      Without Hearing. Where an auditory mode of operation is provided, there must be at least one mode of operation that does not require user hearing. 

5.      With Limited Hearing. Where an auditory mode of operation is provided, there must be allowed at least one mode of operation that improves clarity, one mode that reduces background noise, and one mode that allows user control of volume. 

[Jason] “Perceivable” covers the above.

6.      Without Speech. Where a spoken mode of operation is provided, there must be at least one mode of operation that does not require user speech. 

[Jason] This is addressed by the operability requirements of WCAG 2.

7.      With Limited Manipulation. Where a manual mode of operation is provided, there must be at least one mode of operation that does not require fine motor control or operation of more than one control at the same time. 

8.      With Limited Reach or Strength. Where a manual mode of operation is provided, there must be at least one mode of operation that is operable with limited reach and limited strength.

[Jason] We don’t cover these explicitly, except by requiring a keyboard or keyboard interface as an alternative.

9.      With Limited Cognition. Provide at least one mode that minimizes the cognitive, memory, language, and learning skills required of the user.

[Jason] Content must be “understandable”.

10.  Minimize Photosensitive Seizure Triggers. Where visual modes of operation are provided, there must be at least one mode of operation that minimizes the potential for triggering photosensitive seizures.

[Jason] We address this in WCAG 2 (2.3).

 

Thus, I think most of the principles and guidelines are in place to cover the above. We already want success criteria to be interpreted by having regard to their purpose (avoiding literal, “legalistic” in the pejorative sense, interpretations).

Perhaps what Katie is asking for could be seen as a direction to users of WCAG that, where your situation isn’t addressed by the specific success criteria, apply the more general principles and guidelines, which are akin to abstract functional requirements, and which could be supplemented in a later revision to include what isn’t already explicitly covered.

My point here is that much of the thinking and even much of the text is already there if you temporarily hide away the success criteria and just look at the upper levels of WCAG (principles and guidelines).

 

 

  _____  

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

 

Thank you for your compliance.

  _____  

Received on Thursday, 21 July 2016 17:07:55 UTC