HTML Accessibility Task Force

Weekly teleconf

<chaals> chair: Chaals

<plh> scribe: plh

<chaals> scribe: chaals

canvas implementation - RichS, MarkS, where are we up to?

[see PLH's email]

PLH: wrote 3 of the missing tests, the fourth one I don't understand. need to sit down with Mark to work it out.

… updating results. For one new test there is a bug in chrome, not reporting the right region in accessibility API, will double-check before filing bug.

… If we're lucky, Mark and I will meet to make progress this arvo. Else Monday.

<plh> canvas update

CMN: You expect hitregions will make it?

PLH: Hope so. If we have an implementation with a recognised bug expected to be fixed, we should be able to move forward with it.

face to face meeting - what are we doing / what did we do?

<plh> scribe: plh

Charles: only 3 or 4 of us were able to attend
... looking at keyboard a11y for ARIA
... and Joanie is helping in our understanding of the webkit code

(see minutes at http://www.w3.org/2015/07/08-html-a11y-minutes.html)

Charles: questions about the f2f?

[none heard]

editing the alt guidance https://github.com/w3c/alt-techniques

Charles: any news from Shane?
... we have a github repo. PR to gh-pages branch?

Shane: go for it

transcripts: call for First Public Working Draft? w3c.github.io/html-transcript/html-transcript-src.html

Charles: [under discussion at the f2f]
... we'll continue to propose a FPWD
... PRs are welcome

action item review https://www.w3.org/WAI/PF/HTML/track/actions/open

[going through the actions]

Charles will chase the tab panel through the WICG

action-260?

<trackbot> action-260 -- Shane McCarron to Present web payments in tf meeting -- due 2015-06-30 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/HTML/track/actions/260

Shane: make it 3 weeks from today

<chaals> action-260 due in 3 weeks

<trackbot> Set action-260 Present web payments in tf meeting due date to 2015-07-30.

<chaals> ACTION: JF get the matrix to Shane… [recorded in http://www.w3.org/2015/07/08-html-a11y-minutes.html#action03]

<trackbot> Created ACTION-330 - Get the matrix to shane… [on John Foliot - due 2015-07-16].

<chaals> action-327 due in 1 week

<trackbot> Set action-327 Check if chrome hitregion implementation actually works due date to 2015-07-16.

<chaals> close action-317

<trackbot> Closed action-317.

Charles: we've been looking at readonly for forms
... we think it make sens to have readonly for checkboxes, textinput, etc.
... we see people trying to do so
... idea is to make them unfocusable

Editing the HTML spec

<chaals> scribe: chaals

<plh> https://github.com/w3c/spork/blob/master/README.md

PLH: spent yesterday doing things in the HTML spec, so here is how to do it.

Start at spork's readme - that's the tool that converts the WHATWG spec to HTML 5.1

… change spork, it generates the spec.

… If we manage to make progress on modularisation, the story may change entirely.

… if we make modules, people will be able to make changes that will be propogated from spork.

<plh> https://github.com/w3c/spork/pulls?q=is%3Apr+is%3Aclosed

… Start with the readme, edit a clone. Spork applies JS rules to the spec. In the editing section it tells you what has to be changed- we have examples, as above.

… Depending on the type of change you make, e.g. touching something we are modifying, you have to find which rule is applying by grep for a keyword.

… If you modify something we haven't touched from WHATWG, you make the rules - we have examples of that too.

… Yesterday I modified an algorithm, and fixed a typo.

<paulc> Are your changes tracked in a Bugzilla bug?

… So I encourage you to look into that. It is a little painful, you have to use jquery. Takes a bit of getting used to.

… But then goes faster. If you have trouble, I'm happy to help you.

<SteveF> plh: sounds painful ;-)

… But I hope that now I have cleaned up documentation, it should be easier.

s/plh: sounds painful ;)//

PLH: Yes, changes have bugzilla references in them.

<paulc> Thanks

PLH: Not painful - takes understanding but isn't that complicated.

CMN: If there is a change that is a bit controversial, what is the process?

PC: Make the change, send a note to public-html.

… when editors were cherrypicking WHATWG changes, they sent patch notices - bug number, what they did. Seems a reasonable model to follow.

PLH: I did pull requests, Robin merged them.

… I didn't commit directly.

… If you have a change like that, make a PR and have the discussion in bugzilla/ public-html

PC: Seem to be in a middle ground here. Not many people would know that they should start tracking github for pull requests. We should aim to be transparent so people know what is going on.

PLH: I made Pull Requests…

… and Bugzilla changes

PC: Yes, but people don't see those unless they signed on to track the bug when it was created.

… so people won't know.

PLH: OK, for the substantive algorithm that was a substantive change matching implementation, it makes sense to send something.

PC: OK. We should encourage people to write to the WG about the Pull Requests, as a way of socialising how we are working and remind people where to look.

<plh> https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&columnlist=bug_id%2Cassigned_to%2Creporter%2Cbug_status%2Cresolution%2Cshort_desc%2Copendate%2Cchangeddate&component=HTML5%20spec&list_id=58112&order=opendate%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&product=HTML%20WG&product=HTML.next&query_format=advanced

PC: there are fewer bugs - has there been a change?

PLH: Yes.

CMN: A bunch of people have been closing out invalid bugs…

PLH: There are bugs that will not generate changes in teh spec. I have been going through the easy ones to learn how to edit HTML.

<paulc> THANK YOU, plh

PC: Thank you PLH

PLH: Welcome :)

<JF_> +1 thanks PLH

[teleconf adjourned]