See also: IRC log
CS: ~200 tests that map to previous WCAG
drafts, not up-to-date
... maybe should start updating instead of reviewing them
CV: when is the review process ending for WCAG
LCWD?
... how long it will take to process the comments
CS: not sure if we'll be ready before the end
of march
... risk that if we update stuff they may end up changing again
<Christophe> Editor's draft: http://www.w3.org/WAI/GL/WCAG20/
SAZ: is there an editors draft planned? it usually has notes on what may change
CS: january 28th is the latest
<Christophe> Diff-marked version: http://www.w3.org/WAI/GL/WCAG20/Overview-diff.html
SAZ: think updating the tests may be a good
idea, agree with the concern
... maybe editors draft could help
CS: could ask editors if there are such plans
<scribe> ACTION: CS ask WCAG editors if there will be an editors draft available, that marks all the areas of the document that are in question to change (so that we can update the tests for the stable parts of the document) [recorded in http://www.w3.org/2008/02/19-tsdtf-minutes.html#action01]
CI: in metadata we reference techniques, but
these are far from being stable
... can't reference techniques that may change
... not our priority to update the current tests, prefer to improve the
review process
... tim's review raised several questions, better to address these first
CV: ideal scenario is to be able to update the
test while reviewing it
... but no firm position either way
CS: another issue is that BenToWeb still has a
couple hundred tests ready to be uploaded
... may not make sense to upload them now if they won't be updated
SAZ: are there any timing constraints?
CV: no, project is over
RESOLUTION: don't update the tests yet, see first if there will be guidance from WCAG WG
Cynthia: idea is to test widgets like desktop
applications
... we have inspect32 tool that help evaluate the API
... helps compare data going to the API vs what you see on the screen
... could help for instance test for WAI-ARIA
... can see if information is truely programmatically determined
... there are some issues, for example lists and tables don't get mapped
CV: so you test in the DOM?
Cynthia: not in the DOM, in the Windows API -
iAccess (?)
... states and roles are exposed to the API
... really useful techniques, faster than examining code
SAZ: several steps between code and API, how does platform impact this?
Cynthia: mapping same for Windows Firefox or
IE, didn't test on other OS
... it is browser dependent to a certain degree
CV: did not yet address WAI-ARIA
... only solutions was to write widgets and describe how they interact
Cynthia: this is a much faster way to test, for example if things that look like links are in fact links
CS: where is this tool?
Cynthia: it's freely available, IBM also has a similar tool
<Christophe> URL: http://www.microsoft.com/downloads/details.aspx?familyid=3755582A-A707-460A-BF21-1373316E13F0&displaylang=en
SAZ: this relates to work of User Agent working
group and the protocols and formats WG
... need to keep that relationship in mind
Meeting on Tuesday 26th
tentative meeting on Tuesday 4th March