Re: AutoWCAG: Guideline 1.2 (again)

Hi Twan,

good point to select the elements.  But I have some concerns if these 
can be identified correctly because of the very different methods to 
embed (see the examples I added to the mail to the list). The elements 
differ as well as the attributes used. And the element to select is 
sometimes the parent (param -> object). It would require a quite complex 
set of rules, which may not cover all cases.

And you are right, the note should be very prominent added as an 
assumption, and it must also be noted that the list of file formats is 
not meant to be complete (actually it's a loose collection by myself at 
the moment, I didn't find a proper resource)

Regards
Frank

Am 02.07.2015 um 11:05 schrieb Twan van Houtum:
> Hi Frank,
>
> I really like the idea!
> I'm not sure I understand the first sentense of the selector. It says 
> 'all pages'. Does this mean the selector select all pages of a web 
> site? I think the selector should be focused only on the current page. 
> Something like 'Select all elements containing files capable of 
> playing audio on the current page'.
> And I think we should add an assumption or add the note about new 
> technologies could be added in future.
>
> Greetings,
> Twan
>
> 2015-07-02 10:27 GMT+02:00 Wilco Fiers <w.fiers@accessibility.nl 
> <mailto:w.fiers@accessibility.nl>>:
>
>     Hi Frank,
>     An interesting idea. I'm not too well known with your work on this SC,
>     if you send it to the auto-wcag mailing list we can discuss it there
>     and I'll bring it up in the meeting. I'd like to hear Twan's opinion
>     on this question as well.
>
>     W
>
>     2015-07-01 8:09 GMT+02:00 Frank Berker <fb@ftb-esv.de
>     <mailto:fb@ftb-esv.de>>:
>     > Hi Twan, Hi Wilco,
>     >
>     > on
>     >
>     https://www.w3.org/community/auto-wcag/wiki/SC1-2-1-audio-only-alternative
>     I
>     > noticed yesterday that the only automatic step is the selector
>     (<audio>).
>     > This restricts the test to HTML5, which is currently not the
>     broadest spread
>     > option to embed multimedia.
>     >
>     > So I suggest to describe the selector more hermeneutic, sth.
>     like that:
>     >
>     > All pages including elements containing files capable of playing
>     audio.
>     > Can be identified by any element having an attribute value
>     containing a
>     > media file format, such as .wav, .aif, .aiff, .mp3, .ogg, .oga,
>     .mov, .mid,
>     > .rm, .ra, .ram, .wma, .asf, .swf, .dcr, .avi, .mpg, .mpeg, .mp4,
>     .m4v,
>     > .webm, .flv, .isma
>     > Note: The list of media formats may not be complete and new
>     technologies
>     > could be added in future.
>     >
>     > XPath: <code>//*[contains(@*,'.mid') or contains(@*,'.mp3') or
>     {other media
>     > filetypes...} ]</code>
>     >
>     > This way the test would be fully manual, but technology-agnostic.
>     >
>     > Afterwards I would add Step 1: audio-only and step 2:
>     prerecorded, each
>     > returning inapplicable if not (same scheme on the other tests of
>     G1.2.
>     >
>     > I would try to add fully manual tests for all SC. Then we can
>     use it as a
>     > base for identifying possibilities of automation. Please let me
>     know your
>     > opinion.
>     >
>     > Greetings out of the heat
>     > 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                      http://ftb-esv.de
FTB - Forschungsinstitut Technologie und Behinderung
Grundschötteler Strasse 40,             58300 Wetter
Telefon: 02335/9681-34        Telefax: 02335/9681-19