WCAG Team C

<scribe> scribe: Michael

Ensuring the only way to get to an inaccessible version is from a link from the accessible version, and the inaccessible version is not indexed in the search engine

resolution: take to survey

Failure due to using the blink element

resolution: take to survey

Failure due to using the text-decoration:blink property

Failure due to using the text-decoration:blink property

resolution: discussion of user CSS to override author CSS problems confusing, if we want that it should be its own technique

<scribe> ACTION: Michael to discuss with Becky if we can get Mozilla to provide an option to turn off blinking [recorded in http://www.w3.org/WAI/GL/2006/03/06-wcag-teamc-minutes#action01]

resolution: take to survey

Allowing users to complete an activity without any time limit

resolution: ok to poll users

Failure caused by defaulting to non-conforming version as a result of content negotiation

resolution: ok to poll users

Failure due to a script that causes a blink effect without a mechanism to stop the blinking at 3 seconds or less

resolution: ok to poll users

Failure due to an object or applet, such as Java or Flash, that has blinking content without a mechanism to pause the content that blinks for more than three seconds

resolution: ok to poll users

Failure due to having a session timeout without a mechanism for saving user's input and re-establishing that information upon re-authentication

resolution: mechanism to restart movement does not have to be the same as the mechanism to pause it
... idea of creating a separate technique about automatically restarting content after pausing when user didn't request restart - move to boneyard for later development
... issue of resuming where movement stopped vs "jumping ahead" in real time (stock ticker) - move to boneyard for future development
... ok to poll users

agenda planning

resolution: non-controversial edits can be advanced without running by Team C again