Draft Test for UAAG2 2.11.2 Execution Placeholder

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

Received on Thursday, 20 June 2013 17:01:26 UTC