Re: Draft Test for UAAG2 2.11.2 Execution Placeholder

Does this test procedure need an outermost loop that iterates over all the document formats supported by the user agents? For example, should a full featured web browser test both an HTML file and an SVG file? Are there any other W3 file formats that support executable content?

I'm not entirely clear on what does and does not count as "executable content that would normally be contained within an on-screen area". A script in HTML is not itself contained in such an area, but it may confine itself to modifying that portion of the DOM or canvas, so would that make it count? What about a script run in an iFrame? Or the foreignObject and/or handler elements in SVG?

Minor editorial remarks:

This procedure (as do many others) contains an implicit step #0, locating or creating a test content file. Can they even get to step #1 if they can't complete the prerequisites? Perhaps a more accurate order would be 1. if the format doesn't meet the criteria, then select SKIP; 2. locate or create a test content file; 3. load the test content file...

The sentence "This accessible content is needed to test..." should include some wording that would make the bullet item(s) into complete sentences, e.g. end with "and must:".

#1 the parenthetical example in #1 reads like it's saying PNG is executable content, when it's really saying that PNG is a format that does not include contained executable content. It might be clearer as "If the technology in question cannot contain executable content (e.g. PNG cannot contain scripts, EMBED or OBJECT) then select SKIP."

Technically, 3.4 should be something like "If the placeholder fails to be rendered in place of the executable content..."

     Thanks,
     Greg

-------- Original Message --------
Subject: Draft Test for UAAG2 2.11.2 Execution Placeholder
From: Richards, Jan <jrichards@ocadu.ca>
To: WAI-UA list <w3c-wai-ua@w3.org>
Date: 6/20/2013 9:00 AM
> SC: 2.11.2 Execution Placeholder: The user can request a placeholder instead of executable content that would normally be contained within an on-screen area (e.g. Applet, Flash), until explicit user request to execute. (Level A)
>
> Test Resource: Contained executable content test content file
> This accessible content is needed to test criteria related to the handling of contained executable content:
>   - be a complete file in the "included" web content technology(ies) that includes all of the tepical methods for embedding executable content (e.g. embed, object, canvas in HTML5)
>
> 1. If the technology in question does not include contained executable content (e.g., PNG) then select SKIP.
> 2. Load the " Contained executable content test content file "
> 3. For each type of contained executable content:
>    1. Examine the user interface (or search the documentation) to identify the mechanism for requesting a placeholder be displayed rather than the executable content. The mechanism(s) might include global preference, context menus, etc.
>    2. If no mechanism exists, then select FAIL.
>    3. If a mechanism exists, activate the mechanism.
>    4. If the placeholder fails to be rendered, then select FAIL.
>    5. Check whether the placeholder has a mechanism for the user to indicate a request for the contained content to begin executing.
>    6. If such a request mechanism is absent, then select FAIL.
>    7. Test to see if the request mechanism causes the contained content to begin to execute. If it does, then *Go to the next type contained executable content *.
>    8. Otherwise, select FAIL.
> 4. Select PASS (all contained executable content must meet the requirements)
>
>
>
> Cheers,
> Jan
>