See also: IRC log
<trackbot> Date: 10 December 2009
<scribe> scribe: allanj
GL: discusses comments to
4.9.6
... replace UA with user agent
... clarify 'and/or' based on what's there, not what the author
provides. need to clarify in the definitions and supplemental
materials
... settle on one term for "time-based media" (4.9.3),
"animation" (4.9.7), and "video" (4.9.6)
issue: settle on one term for "time-based media" (4.9.3), "animation" (4.9.7), and "video" (4.9.6)
<trackbot> Created ISSUE-61 - Settle on one term for "time-based media" (4.9.3), "animation" (4.9.7), and "video" (4.9.6) ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/61/edit .
issue: ISO has slow multimedia as
an AA level not A
... is media broad enough, should we choose a different word,
to generalize to encompass audio, video, animation, haptic,
etc.
what about canvas element.
GL: if all control of timing is done by a script then it is up to the author to provide functionality.
issue: editorial checks -- review document for 'recognize', 'and/or', initialisms (UA, acromyns, etc.)
<trackbot> Created ISSUE-62 - Editorial checks -- review document for 'recognize', 'and/or', initialisms (UA, acromyns, etc.) ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/62/edit .
discussion of flash threshhold
WCAG flash language: Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)
SH: wants to combine 4.4.1 and 4.4.2
GL: what about 'blink' element.
if UA has a hard coded blink rate of 4+ times, then UA is in
violation.
... UA that recognizes flashing control should provide a
mechanism to limit the number of flashes.
WCAG understanding: http://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-three-times.html
<Greg> Actually my point was that if a Web page uses the <BLINK> tag and the UA renders that by flashing the content four times per second, the UA would not violate the currently worded guidelines, but we should revise the guidelines so it would be in violation of something.
<Greg> We can either modify 4.4.1 and 4.4.2 to restrict both the UA UI *and* recognized flashing in rendered content, or we could add separate success criteria for the latter.
<Greg> To go further, should the UA be required to override recognized Web content attributes that would cause blinking that violates the thresholds? Or, should the UA only be required not to violate them when IT (the UA itself) provides the blink rate?
Intent- to avoid causing seizures.
<Greg> I suggest that we recommend the user agent provide a user option to constrain recognized blinking in web content to fall within the general flashing and red flashing ranges so as to avoid triggering seizures in individuals with photosensitive seizure disorders.
intent - this is about preventing physical harm
scribe: to the user
two items: user option to set blink rate; and, default flashing rate for interface and content
<Greg> "the user interface and default presentation of recognized flashing Web content never violate..."?
<scribe> ACTION: Jim to rewrite 4.4.1 to include the user interface and default presentation of recognized flashing Web content never violate and create user has the option to... [recorded in http://www.w3.org/2009/12/10-ua-minutes.html#action01]
<trackbot> Created ACTION-258 - Rewrite 4.4.1 to include the user interface and default presentation of recognized flashing Web content never violate and create user has the option to... [on Jim Allan - due 2009-12-17].
issue: mechanism to expand marque (or other element) to read the content within - scroll bars, etc
<trackbot> Created ISSUE-63 - Mechanism to expand marque (or other element) to read the content within - scroll bars, etc ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/63/edit .
<Greg> Suggestion: the UA should allow the user to perform on CSS images and background images any action they could perform on normal, foreground images. Same with extra text e.g. bullets and numbering.
issue: the UA should allow the user to perform on CSS images and background images any action they could perform on normal, foreground images. Same with extra text e.g. bullets and numbering. UA should have access to CSS DOM or its generated content.
<trackbot> Created ISSUE-64 - The UA should allow the user to perform on CSS images and background images any action they could perform on normal, foreground images. Same with extra text e.g. bullets and numbering. UA should have access to CSS DOM or its generated content. ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/64/edit .
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: allanj Inferring ScribeNick: AllanJ WARNING: No "Topic:" lines found. Default Present: AllanJ, Jeanne, Greg, sharper, mhakkinen Present: AllanJ Jeanne Greg sharper mhakkinen Regrets: Kelly_Ford Kim_Patch Jan_Richards Henny_Swan WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 10 Dec 2009 Guessing minutes URL: http://www.w3.org/2009/12/10-ua-minutes.html People with action items: jim WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]