RE: SC 1.1.1 Text Alternative Computation

Hi Frank and Katie,

Interesting discussion. I figured we would at some point pretty soon need to start looking at accessibility support. I'll put it on tomorrow's agenda so we can collect some ideas about what direction we should take this for auto-wcag.

Wilco


030-2398270 (ma t/m do)

  Goed geholpen? Recommend us: www.linkedin.com/company/accessibility-foundation/products
  --------------------------------------------------------------------------------------------------------------------
  Trainingen Toegankelijkheid: www.accessibility.nl/trainingen
________________________________________
Van: Katie Haritos-Shea GMAIL [ryladog@gmail.com]
Verzonden: woensdag 10 december 2014 16:55
Aan: 'Frank Berker'; public-auto-wcag@w3.org
CC: Katie.Haritos-Shea@Chase.com
Onderwerp: RE: SC 1.1.1 Text Alternative Computation

You might also want to add that accessibility support is also a very important requirement of WCAG 2.0

Thanks!



* 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: Frank Berker [mailto:fb@ftb-esv.de]
Sent: Wednesday, December 10, 2014 10:35 AM
To: Katie Haritos-Shea GMAIL; public-auto-wcag@w3.org
Cc: Katie.Haritos-Shea@Chase.com
Subject: Re: SC 1.1.1 Text Alternative Computation

Hi Katie,

good point.
I suggest adding the assumptions

 *   accessibility support is a requirement of UAAG2.0
 *   in controlled (e.g. intranet, corporate) environments it has to be assured that the attributes providing alternative text are supported by the installed user agents.

and to present the textual alternatives indicating their sources. This way the experienced user can assess, which attributes' text is used and if it's sufficient.

Besides: a good developer should know his environment and target audience :)

Thanks a lot
Frank

Am 10.12.2014 16:03, schrieb Katie Haritos-Shea GMAIL:
Frank,

I like the idea of adding the UAAG 2 reference, but we also should be trying to get developers to starting thinking about existing framework they are building in. If it is a closed environment, say and intranet, they should take some responsibility for building to what is supported in that network/platform. Does that network/platform exclusively utilize user agents (and possibly network approved AT) that support HTML5 and ARIA, or HTML4 and ARIA, etc.

Not sure how to present that, but that is my thinking in bringing this up…….



* 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: Frank Berker [mailto:fb@ftb-esv.de]
Sent: Wednesday, December 10, 2014 9:45 AM
To: Katie Haritos-Shea GMAIL; public-auto-wcag@w3.org<mailto:public-auto-wcag@w3.org>
Cc: Katie.Haritos-Shea@Chase.com<mailto:Katie.Haritos-Shea@Chase.com>
Subject: Re: SC 1.1.1 Text Alternative Computation

Hi Katie,

I'm aware of that fact and still see the problem to determine, if the attributes are accessibility supported, because it depends on the individual setting of user agents.
Most less experienced users will not be able to say if it is or not. Maybe we could provide the content of (aria-labelledby, aria-label) and the title attribute in brackets to the user and add the assumption, that these technologies should be supported, because this is a requirement in UAAG 2.0<http://www.w3.org/TR/UAAG20/#def-programmatically-avail>.

Our highest level of assertor requirements<https://www.w3.org/community/auto-wcag/wiki/Introduction_to_auto-wcag_test_design#Assertor_requirements_.28optional.29> is "4. advanced understanding of HTML and WCAG". In my opinion this is not enough to provide an estimation of the level of support by OS, browser and assistive technology-combinations.

I just saw, that Shadi and Wilco worked on an Accessibility Support Database (Unapproved Prototype)<http://www.w3.org/WAI/accessibility-support/>. Maybe this can be used in future to provide valid information.

Thanks for your input!
Frank



Am 10.12.2014 14:36, schrieb Katie Haritos-Shea GMAIL:
Frank,

The thing that may need to be kept in mind is that for IMAGES that use ARIA (aria-labelledby, aria-label) and the title attribute for alternative text – that there is a manual check that calls for determining if they are accessibility supported<http://www.w3.org/TR/2008/REC-WCAG20-20081211/#accessibility-supporteddef>.

See  F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image".
http://www.w3.org/TR/WCAG20-TECHS/F65.html



* 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: Frank Berker [mailto:fb@ftb-esv.de]
Sent: Wednesday, December 10, 2014 8:21 AM
To: public-auto-wcag@w3.org<mailto:public-auto-wcag@w3.org>
Subject: SC 1.1.1 Text Alternative Computation

Hi everyone,

I spent some time on WAI-ARIAs name calculation algorithm<http://www.w3.org/TR/wai-aria/roles#namecalculation> and added the results to the wiki in pseudo-code and UML<https://www.w3.org/community/auto-wcag/wiki/Text_Alternative_Computation>.
The algorithm gets all textual alternatives (aria-labelledby, aria-label, input values, alt, title) for image, input, area applet, embed and object elements and concatenates them.
The questions are now:

 *   Is my understanding of the specification valid?
 *   Best method to incorporate it in the wiki?
 *   Best method to use the algorithm from the tests the wiki, if we split the tests to elements with an alternative text and elements without an alternative text?
Thank you in advance for any input.

Best from Wetter
Frank






--

Frank Berker

fb@ftb-esv.de<mailto:fb@ftb-esv.de>                      http://ftb-esv.de

FTB - Forschungsinstitut Technologie und Behinderung

Grundschötteler Strasse 40,             58300 Wetter

Telefon: 02335/9681-34        Telefax: 02335/9681-19





--

Frank Berker

fb@ftb-esv.de<mailto:fb@ftb-esv.de>                      http://ftb-esv.de

FTB - Forschungsinstitut Technologie und Behinderung

Grundschötteler Strasse 40,             58300 Wetter

Telefon: 02335/9681-34        Telefax: 02335/9681-19




--

Frank Berker

fb@ftb-esv.de<mailto:fb@ftb-esv.de>                      http://ftb-esv.de

FTB - Forschungsinstitut Technologie und Behinderung

Grundschötteler Strasse 40,             58300 Wetter

Telefon: 02335/9681-34        Telefax: 02335/9681-19

Received on Wednesday, 10 December 2014 17:12:41 UTC