HTML Accessibility Task Force Teleconference -- 05 Feb 2015

<trackbot> Date: 05 February 2015

<scribe> scribe: MarkS

Any other items for the agenda?

Transcripts

<JF> Use cases and stuff for a transcript element, attribute…

JF: Back before plan 2014, Media sub team did work on this. quite a bit
... Syliva Pfeiffer, chaals, janina and I met a number of times to iron out a proposal. we ended up with transcript element and transcript attribute
... apple wanted to have the link visible on page
... put together a change proposal, never had a decision from chairs
... probably our best place to start
... 4 different use cases and examples in the wild
... satisfies all of the req in the Media Accessibility User Requirements doc
... video element would take transcript attribute which would take an ID
... the the transcript attribute would point to transcript element
... this should satisfy apple's requirements
... its very complete. should be a great place to start. includes use cases
... if we can get wider review from this group, we should be able to start an extension spec

CN: I would encourage everyone to look at the use cases and reqs stuff very carefully. We should be clear that these are right

JF: I think we spent at least 5-6 hours working collaboratively on this.
... its very comprehensive

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

<chaals> close action-300

<trackbot> Closed action-300.

CN: we can close JF's action item

<chaals> action-298

<trackbot> action-298 -- Charles McCathie Nevile to Set the focus management discussion up in html wg -- due 2015-01-22 -- OPEN

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

CN: 298, is still open

JF: you can close 301

CN: Shane alt doc changes, do you want to put that on agenda

SM: not this week, lets do it next week

CN: Coordinate with WCAG chairs. I've contacted them

SM: you can close 302

CN: 303 is due in a week then

<chaals> action-303 due in 1 week

<trackbot> Set action-303 Present alt doc changes due date to 2015-02-12.

<chaals> close action-302

<trackbot> Closed action-302.

<chaals> close action-304

<trackbot> Closed action-304.

Proposed Work Items - http://www.w3.org/WAI/PF/html-task-force , http://www.w3.org/WAI/PF/HTML/wiki/51wishlist

CN: looking to finalize our work items
... should be accurate for at least the next 6 months (or until completion)
... possible to take on new work as well
... we've been working from the wishlist
... in about a week, I would hope to have a call for consensus on our work items
... it will be in a wiki page.
... make it easier to keep it up to date

LW: i picked up the date picker stuff from last week

<LJWatson> http://www.w3.org/WAI/PF/HTML/wiki/Datepickers

CN: cyns, are you going to do menu work, slated for this summer

CS: Fall is actually more likely
... i will look at it this summer, but it will take longer to complete the work

CN: we're trying to keep the work statement accurate. we may not want to put it on there now. we are putting work items on wiki, so it will be easier to keep up to date
... may want to hold off putting it on there until later then.
... any more on work item/statement stuff

LW: I talked to brian kardell about moving panel work into this space.

Web Payments work (chaals)

CN: this is something we should keep an eye on. I have a task to get more info on this work
... there was a workshop on this yesterday
... there are some documents around that people can review.links:

<chaals> CG use cases - being provided to the IG as input

CN: one of the things that the payments group is doing is that they want to make sure they meet accessibility requirements
... think PF may want to keep an open dialog with this group

<chaals> Use cases for payment

CN: they are also clear that they don't want to do this only in their own tiny space, they want to open it up to other experts from other groups, like HTML, a11y ,etc

<chaals> s|-> http://opencreds.org/specs/source/use-cases/ CG use cases - being provided to the IG as input||

CN: they have a draft document of use cases. I thought it was hard to understand as a non-web-payments person. the minutiae of the web payments system
... hoping it will become more clear
... there are many issues in the use cases that are not HTML specific, but interesting nonetheless (from and a11y perspective)
... its a complex and important space

<Zakim> ShaneM, you wanted to mention my (notional) involvement in web payments

SM: I just wanted to say that I have been monitoring this and credentialing work. I will be ramping up my activity in web payments, so I will keep a close eye on this.

JF: shane answered my question. I was hoping we had people dedicated to this. I know chaals, katie haritos shea and now shane, so that's good

CN: The chair of the group, david E is not someone many of us know, but he is interested in supporting a11y. technical guy.

face to face meetings

CN: waiting for decisions from HTML and WebApps. seems like HTML group will meet in Redmond
... if you are going to that meeting, good. it will be HTML focused, but encourage a11y reps to attend if they can.
... proposed dates are 13-17 of april
... informal note. if anyone is going to CSUN, the SVG a11y people are going to try to get together to do some technical work
... RS will know more

RS: yes.
... Tuesday night

CN: meeting adjourned

<chaals> [adjourned]

- DRAFT -

HTML Accessibility Task Force Teleconference

05 Feb 2015

Attendees

Contents