See also: IRC log
<trackbot> Date: 15 May 2014
979 jim - rewrite of 1.4
978 jeanne - write proposal for ms05 response
977 greg - glossary entry for 'recognize'
976 jim - def of rendered content
975 jim - use of uaui or rc in document
974 jan - work text into introduction
972 jeanne - smith cr05 response re: heading nav
browsers need to do more was mentioned.
<scribe> scribe: allanj
kp: we need a page on how to file bugs against all browsers on the UA home page
aside -- http://heydonworks.com/practical_aria_examples/#input-tooltip accessible tooltip with css only
and it works on mobile
HAPPY GLOBAL ACCESSIBILITY AWARENESS DAY!! http://www.globalaccessibilityawarenessday.org/events.html
media use cases http://www.w3.org/2011/webtv/wiki/Media_APIs/Use_Cases
js: written by web and TV use
cases. UAWG has been asked again to review these in terms of
... we can write new ones if we want
jr (the ghost): - everywhere they mention "tablet" it might be better to say "Mobile device" or "Table/Smartphone"
- use case: ability to view captions only on a second device (Table/Smartphone)
- use case: ability to hear secondary audio channel only on second device (Table/Smartphone)
ja: use case captcha blocking setting service up
<jeanne> use case #1: -- no CAPTCHA
js: May 30
ja: 2 more UAWG meeting
gl: first glance - pretty
generic, basic computer use
... what about GII universal remote
ja: not baked yet.
... ACTION: put tv use cases on agenda
wayne has joined the group
read 1.4 character spacing...need to refine language before it gets final
wayne has left the group
close item 1
js: deadline for charters is next
week before AC meeting
... need to update the timelines
... made good progress, but not had many f2f meetings
... should finish comments in next several weeks
... will probably do 2 publishing cycles for 2nd last call
ja: so that makes CR in March (possibly)
then we need to complete testing of implementations before PR
js: have a f2f to only write tests
gl: should start another track of keeping of implementations
ja: we have a wiki page for that
js: finish these comments and
publish by end of june
... then 4-6 weeks of test writing, perhaps f2f
tpac - last week of OCT
gl: could do video telecon
js: work well in pairs, but conference calls get in the way
gl: hangouts, google docs, webinar where we can share the same document
js: process the comments from June publishing, get those comments, redo document...2nd last call 1st quarter of 2015
ja: could we go to 2 hour calls?
kp: rather other extended event
gl: 2 hour calls work well some times
kp: need to have 2 implementations for each sc.
kp: rework the wiki
... for structure, and link to google docs, link to github pages
js: discussion of process, exit criteria, etc.
cr - mar 2015, pr - dec 2015 or mar 2016, ...adjust others accordingly
for Proposed Rec (PR) need all testing done and 2 implementations for each SC.
ja: 1.4.3 bullet character spacing - Wayne wants further review.
gl: line spacing seems more prescriptive, and more restrictive
last week discussion concerned min/max increment
<Greg> It went from a range and two exact intermediate values, to the same range with 8 intermediate values.
gl: thought it was min/max and #
... no strong feelings, but seems opposite of original intention
* orig - Line spacing of at least 1.0, 1.3, 1.5, and 2.0 times the font
<scribe> new - Line spacing between 1.0 and 2.0 times the font height in .1
kp: what's practical
js: min/max and # of steps
proposed- Line spacing between 1.0 and 2.0 times the font height with at least 3 step in between
gl: but less spacing needed for high magnification
ja: that a AAA 1.4.6
proposed- Line spacing between 1.0 and 2.0 times the font height with at least 2 step in between
gl: word had default of 1, 1.5, 2
... support user style sheets is level A, all of these are then already done
spending time on this is not productive...
js: what about media players
ja: caption styling?
js: play list, etc.
gl: this is content, not UI
<Greg> Are we saying that user style sheets are a powerful but techie way for customizing the presentation of content, and they're Level A, but we encourage user agents to provide easier, less techie ways of doing it through their UI (e.g. menu items and configuration dialogs), perhaps at lower priority?
ja: wish it were the reverse, that basic customization are A and are covered in the UI, at AAA then css kick in.
<Greg> But the current wording allows them to rely on the user style sheets, and thus (assuming they support user style sheets which are Level A) no work would ever be required to comply with 1.4.3 etc.
js: approach of basic config -
line spacing, justification, text size color and need a UI
... line spacing is AA, character spacing is AAA
gl: justification is AA
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 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 Default Present: Jeanne, Kim_Patch, Jim_Allan, Greg_Lowney, +1.562.256.aaaa, Wayne WARNING: Replacing previous Present list. (Old list: -1.562.256.aaaa) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Jeanne, Kim_Patch, Jim_Allan, Greg_Lowney, Wayne Present: Jeanne Kim_Patch Jim_Allan Greg_Lowney Wayne Regrets: jan kelly Found Date: 15 May 2014 Guessing minutes URL: http://www.w3.org/2014/05/15-ua-minutes.html People with action items: WARNING: Possible internal error: join/leave lines remaining: <scribe> wayne has joined the group WARNING: Possible internal error: join/leave lines remaining: <scribe> wayne has joined the group[End of scribe.perl diagnostic output]