See also: IRC log
<trackbot> Date: 13 June 2013
<allanj> Action+ Face 2 Face - finalize
<scribe> scribe: Harper_Simon
<scribe> ScribeNick: sharper
JA: Is there anything we have forgot before Last Call
JR: may receive stuff in comments as we move on which would help answer this questions.
JS: already have 2 comments - but
other than that we are in good shape - but are there any loose
ends - except UA defn.
... lets look over the document and see if it triggers anything
over the next week.
RESOLUTION: Check over the next week
JA: Dates for f2f... August
27-29
... All OK?
All: all good with dates - KP / JA / JS / JR / SH (wont be able to make it)
RESOLUTION: All well on f2f
GL: TPAC in Nov - do we need to
talk about it?
... What are the logistics - will the group be working the 5
days - maybe too early
JS: Will be meeting for 2 days of the 5 days period m/t or t/f - Wed is the tech plenary day
<jeanne> http://www.w3.org/2013/11/TPAC/
<jeanne> http://lists.w3.org/Archives/Public/w3c-wai-ua/2013AprJun/0095.html
JS: explaining / reading the Test content
JA: wasn't able to complete his last week.
JS: Welcome comments
KP: be useful for some of these had an example of actually doing this through a browser - ie putting a browser through this may make the test better.
GL: Really well put together - likes the way it is split and thinks it's clear - runs into trouble in test 2 - the flow to 3 only applies of a global switch
JS: tried to do it so it would go either (in context)
G: L: Leaving it upto the tester - could add a note
JR: needs to be combined - starts with loading the test - verbalising thoughts on the fly - text to follow:
<Jan> JR: I would combine the two tests...
<Jan> JR: Start by loading in the test content known to contain alternatives
<Jan> JR: Loop on the known alternatives
JA: Could create a test page for this...?
<Jan> JR: Make sure the choose mechanism is present (whether global or local)
<Jan> JR: Then activate the mechanism and check to make sure it rendered
JA: will be coming to appendix E soon - for which I've started an excel sheet
JS: second one - reading from the mail text - to note 'sample alternative content' web page to write fro all types of alt content for testing purposes.
GL: May need to be multiple
documents
... what are we concerned with
<allanj> http://www.w3.org/wiki/Open_Web_Platform
<allanj> http://www.w3.org/wiki/HTML/MediaAccessibilityChecklist
W3C standards define an Open Web Platform for application development that has the unprecedented potential to enable developers to build rich interactive experiences, powered by vast data stores, that are available on any device.
JA: we need to scope this
... Most of this seems to be HTML - so maybe we need to scope
test to this
JS: people can write test for this
GL: 1.1.1 there is alt content in
SVG - can they still pass if they don't render this
... they don't have to support his?
<allanj> in the browser declaration, we support these technologies. then they must be tested against them.
RESOLUTION: JS: will contact other in w3c re the scope and standards
<jeanne> ACTION: jeanne to research in W3C the breadth of technologies we will have to test against for CR. SVG? MathML? SMIL? [recorded in http://www.w3.org/2013/06/13-ua-minutes.html#action01]
<trackbot> Created ACTION-837 - Research in W3C the breadth of technologies we will have to test against for CR. SVG? MathML? SMIL? [on Jeanne F Spellman - due 2013-06-20].
Move back to discuss point 4 - what passed and what failed
JA: test page should help on this - in directions we should say write down what is missed (JS: added this text to test)
GL: discussing the language used in the text - looking for alternative ways to express this
<Greg> 3. For each piece of alternative content in the sample document:
<Greg> 1) if the alternative content is not visible, select FAIL
<Greg> 4. Select PASS.
JR: gave the ATAG perspective
JS: People should we pick one to complete for next week
<jeanne> Greg - 2.4.4
GL 2.4.4
JR: 2.11.2
... gives text for the way ATAG does things - black and white
lists required by testers, as well as grey list - maybe an
issue but not automatically flagged
<allanj> ja: 1.7.1
JR: in summary we are gunna need a thrid list
JA: 1.7.1
SH 1.1.4
<Jan> JR: I will do 2.11.2 Execution Placeholder
KP: 2.1.1
<Jan> s/2.12.2/2.11.2
GL: sent spreadsheet to the list
<allanj> http://lists.w3.org/Archives/Public/w3c-wai-ua/2013AprJun/0086.html
KP: discusses process for
this.
... can convert this to a google spreadsheet - how will
crowdsourcing happen?
... can just supply this via a link - or can sign up users via
their google accounts
... second way someone has to manage this
JS: safer
KP: safer but takes a little more time
JR: Slower on front - but trust the data better
JS: agreed
RESOLUTION: Google spreadsheet, and manage users via user names.
KP: Could do this for other examples and resources.
JR: we should limit the number of documents we have as changes may still occur - so reducing possibility for these to be contradictory is useful.
KP: Different kinds of solutions
to this being suggested.
... is able to manage to get this up there.
<scribe> ACTION: KimPatch to hangle the google spreadsheet installation for crowdsourcing [recorded in http://www.w3.org/2013/06/13-ua-minutes.html#action02]
<trackbot> Error finding 'KimPatch'. You can review and register nicknames at <http://www.w3.org/WAI/UA/tracker/users>.
<scribe> ACTION: Kim to handle the google spreadsheet installation for crowdsourcing [recorded in http://www.w3.org/2013/06/13-ua-minutes.html#action03]
<trackbot> Created ACTION-838 - Handle the google spreadsheet installation for crowdsourcing [on Kimberly Patch - due 2013-06-20].
JA: has 20 Alt Contents from Appendix E - and created a spreadsheet
<allanj> http://www.w3.org/WAI/UA/2013/ED-IMPLEMENTING-UAAG20-20130607/#alternative-content-list
JA: other ideas re alt content
JR: talks about accessibility information (not alt content) we tie to wcag (ie ATAG)
<Jan> http://www.w3.org/WAI/AU/2013/ED-IMPLEMENTING-ATAG20-20130220/#prompting-types
JR: taking group through the list as above
GL: Could think about this with regard to alt content being human readable - but meta data could be useful but not considered alt content
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) Succeeded: s/exel/excel/ Succeeded: s/standrads/standards/ Succeeded: s/12/11/ FAILED: s/2.12.2/2.11.2/ Found Scribe: Harper_Simon Found ScribeNick: sharper Default Present: Jeanne, Jim_Allan, +1.661.748.aaaa, Greg_Lowney, Kim_Patch, kford, Jan, sharper, [Microsoft] Present: Jeanne Jim_Allan +1.661.748.aaaa Greg_Lowney Kim_Patch kford Jan sharper [Microsoft] Regrets: Eric Found Date: 13 Jun 2013 Guessing minutes URL: http://www.w3.org/2013/06/13-ua-minutes.html People with action items: jeanne kim kimpatch WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]