See also: IRC log
<scribe> Scribe: JR
JA: Joining the call today we have Gregory Rosmaita...working on PF and HTML5
http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0016.html
JA: Seems to make sense
... Would be good to hear from KF
... Also we should hand to WAI-PF to see if we can get their
input
<scribe> ACTION: JA to Will forward PP's message to x-tech. [recorded in http://www.w3.org/2007/07/26-ua-minutes.html#action01]
JA: THere used to be screen reader settings to block full page refreshing.
GR: Talk with Charles Chen of LiveVox, implementing ARIA live regions.
PP: Related to example in my msg
- screen reader option even to overrule "rude"
... May be helpful to invite CHarles to call
<scribe> ACTION: JA to Contact Charles Chen to invite him to the call. [recorded in http://www.w3.org/2007/07/26-ua-minutes.html#action02]
JA: Anything else to ask?
PP: No it's all in the msg for now.
GR: xtech is a public
archive
... THere is a PF-ARIA wiki where best practices are being
built - in ESwiki
... Our problem is we are trying to push for ARIA to be
implemented in HTML5
GR Roles into HTML5
<AllanJ> JR: reviews proposal
<AllanJ> PP: was there a discussion of the 'canvas' element
<AllanJ> JR: no, 'canvas' has many definitions.
<AllanJ> GR: 'canvas' element is in HTML5
<AllanJ> PP: worried about confusion with terms. should be fine with good definition
JA: Let's note concern about use
of "canvas"...
... Use of canvas is sceondary , just in definition
... So should be ok for now
GR: This vocab issue is also a
prob in HTML5
... Have heard canvas used elsewhere
JR: Prefer not to define canvas since defn would be circular back to base browser
<scribe> ACTION: JR to Will update wiki for 3.1 [recorded in http://www.w3.org/2007/07/26-ua-minutes.html#action03]
<AllanJ> http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0007.html
<AllanJ> JR: Problem: use scripts to launch windows without interface (scroll bars, etc.)
<AllanJ> ...add new checkpoint specific to new window interface.
<AllanJ> JR: X.Y Toggle user agent window formatting
<AllanJ> - Allow configuration not to allow user agent windows to be formatted in
<AllanJ> such a way that navigation or control by the user are limited (e.g.,
<AllanJ> fixed size, no scrollbars, etc.).
<AllanJ> GR: requirements, 1. warn user of new window opening...
<AllanJ> 2. new windows spawned, use UA user preference setting, and over-ride author java script
<AllanJ> JR: assume no setting for show/no show scroll bar
<AllanJ> JR: limited setting...use author setting, or full window interface
<AllanJ> JR: 1 checkbox, author setting or fully functional browser window...
<AllanJ> based on user current UA settings for scroll bars, button bars, etc.
<AllanJ> JR and GR in agreement
<AllanJ> ACTION: rework new proposal, flesh out setting and UA behavior [recorded in http://www.w3.org/2007/07/26-ua-minutes.html#action04]
JA: Clarify that this is for 3.4
<scribe> ACTION: PP to Proposal to combine 3.2 and 3.3 [recorded in http://www.w3.org/2007/07/26-ua-minutes.html#action05]
JA: GR took this on for
WAI-PF...
... INteresting that no one wants to own it...
... WCAG started it...
GR: Would like to treat "until
user agents" as dependencies...
... for HTML5?
... HTML group using HTML5 as starting point instead of HTML
4.01
... To retain some access stuff we need to justify them.
JA: Just checked, no "until user
agent" clauses in WCAG2
... In reviewing this, only so much can go in code....
e.g. checkpoint 7.1, until user agents allow UA's to control flickering....
don't cause the screen to flicker...
but there are many different ways to get things to flicker...
but some ways it is impossible for the user agent to know...
so there is nothing they can do.
GR: By looking at these carefully, we home to get HTML5 to accept Events...
JA: Any other response from PF
list?
... HTML5 seen this?
GR: So want to take until user
agent doc and point to WAI-user agent support page
... So as you go though you'll see how things have been
addressed
<AllanJ> current UA support for WCAG http://www.w3.org/WAI/Resources/WAI-UA-Support
GR: It's a doc that lists all the "until user agent" clauses - it includes WCAG techs - GR would like to add links to user agent support page
JA: Might also be useful to use
UA implementation reports
... As related resources, looked at UAAG 1.0 mapping to WCAG
2.0
Actually that was GR
JA: Happy to work with GR, maybe on xtech
GR: Likes to bring issues to
xtech...RECAPCH etc
... First step for me is to post 2 docs...
... "Until User Agents" doc and WAI User Agent support
doc
... WAI User Agent support doc just has added anchors over the
version in uA space
... Will help us clarify things that UA just doesn't have
access to
... Talking about adding timing to HTML5 but already done in
SMIL
... Let's just see how this develops
... Until user agent clauses just bug me
JA: Interesting to get crosstalk
going on - maybe intersting to send to compound docs
group
... But let's develop it more first
GR: Frustrating that rare use cases are being used to remove things from HTML5
<scribe> ACTION: JA to Get thoughts together about 3.4 "All executable content" managing configuration [recorded in http://www.w3.org/2007/07/26-ua-minutes.html#action06]
<AllanJ> http://teitac.org/wiki/Talk:Web_and_Software:_July_11#Highly_visible_keyboard_focus
This is scribe.perl Revision: 1.128 of Date: 2007/02/23 21:38:13 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: JR Inferring ScribeNick: JR Default Present: Jim_Allan, Gregory_Rosmiata, JR, pparente Present: Jim_Allan Gregory_Rosmiata JR pparente Regrets: Cathy_Laws Kelly_Ford Agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0015.html Got date from IRC log name: 26 Jul 2007 Guessing minutes URL: http://www.w3.org/2007/07/26-ua-minutes.html People with action items: ja jr pp rework WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]