W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2013

Fwd: UAAG 2 Feedback - too late?

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 25 Jul 2013 08:40:48 -0500
Message-ID: <CA+=z1WkbCrkq_By49L67-2OuU27AO9hZ3OBw7Q1qs76KN+nn8A@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
---------- Forwarded message ----------
From: Foliot, John <john.foliot@chase.com>
Date: Tue, Jul 23, 2013 at 5:47 PM
Subject: UAAG 2 Feedback - too late?
To: "jimallan@tsbvi.edu" <jimallan@tsbvi.edu>

 Howdy friend!  ****

** **

Hope all is well in the Lone Star state, and that you’ve not completely
baked yourself to death.  I musty truthfully confess that I have been
remiss in reviewing UAAG 2 Draft to date; it’s a time and resources issue
(as it always is).****

** **

However, today I was doing some research and testing and noted something
that I felt worth mentioning.  Specifically, I am testing a report that one
of our team members could not get the @title expansion on the <abbr>
element, but could on the <acronym> element. This seems curious and weird,
and/but a test suite and a round of testing will get to the bottom of it
(I’ve not yet done the testing, that will happen this week).****

** **

HOWEVER… when I was setting up the Unit Test for our team, I also set out
to document the expected behavior, and that was an interesting search.
Unless I’ve missed it, there is no specific behavior proscribed (nor even
suggested) for this use case, the best I could find was:


“1.1.1 Render Alternative Content: For any content element, the user can
choose to render any types of recognized alternative content that are
present. (Level A)”

– which is close, but… (so comment 1 – is there something that speaks to
this use-case: <abbr title=”World Wide Consortium”>W3C</abbr>?)****

** **

** **

Also, as I was looking around, I noted the specific absence of RFC 2119
language (MUST, SHOULD, MAY). Was this deliberate? ****

** **

As I embark on the forced march in our org, specific and precise language
saves a ton of discussion down the road (and trust me, been dragged into
that weed patch more than once already). For example, using that same
example, I would have written it this way:****

“1.1.1 Render Alternative Content: For any content element, the user MUST
be able to choose to render any type of recognized alternative content that
is present. (Level A)”****

** **

Minor editorial change, but a significant difference in instruction – more
specific and in a language that engineers already clearly grok: RFC 2119 is
used all over the place, including on numerous W3C documents.****

** **

Ultimately, my test suite page looks like this:****
Expected Result(s)****

Upon encountering the abbr or acronym elements, that information SHOULD be
conveyed to the screen reader user. When the title attribute is also
applied, the value of the title MUST be announced on user demand (for
example, the user has configured their AT to do so).****

Source: UAAG 2.0: Guideline 1.1 - Provide access to alternative
1.1.1 Render Alternative Content: For any content element, the user can
choose to render any types of recognized alternative content that are
present. (Level A) ****


So, feedback/comment #2 (and realizing this is way late), I believe that
UAAG would have more impact if it employed RFC 2119 language, over vaguer
instructions such as “can” and “it is recommended”.****

Anyway, my $0.05 Canadian (I can no longer give just 2 cents, as Canada has
abolished the penny…. J)****

** **



John Foliot****

Senior Web Accessibility Specialist****

Corporate Internet Group,****

JPMorgan Chase ** **

  600 Harrison Street, 5th Floor, San Francisco, CA, 94107****

  749 West El Camino Real, 2nd Floor, Mountain View, CA 94040 ****

Mobile: 650-468-5785****

** **

This transmission may contain information that is privileged, confidential,
legally privileged, and/or exempt from disclosure under applicable law. If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or use of the information contained
herein (including any reliance thereon) is STRICTLY PROHIBITED. Although
this transmission and any attachments are believed to be free of any virus
or other defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to ensure
that it is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss or damage
arising in any way from its use. If you received this transmission in
error, please immediately contact the sender and destroy the material in
its entirety, whether in electronic or hard copy format. Thank you.

Jim Allan, Accessibility Coordinator & Webmaster
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
Received on Thursday, 25 July 2013 13:41:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:44 UTC