W3C

HTML Accessibility Task Force Teleconference

19 Jun 2014

See also: IRC log

Attendees

Present
janina, Mark_Sadecki, paulc, Adrian_Roselli, Cynthia_Shelly, Judy, John_Foliot, ShaneM
Regrets
Leonie Watson
Chair
Janina
Scribe
MarkS, JF

Contents


<trackbot> Date: 19 June 2014

<janina> Meeting: HTML-A11Y Task Force Teleconference

Identify Scribe http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List

<MarkS> scribe: MarkS

Longdesc

JS: ->http://lists.w3.org/Archives/Public/public-html-a11y/2014Jun/0042.html Longdesc CfC to transition to CR

->http://lists.w3.org/Archives/Public/public-html-a11y/2014Jun/0042.html Longdesc CfC to transition to CR

MS: Chaals and I made good progress on processing comments and tidying up loose ends in longdesc. Chaals issued a CfC last Friday, which closes tomorrow.
... Preparing documentation required for that transition. We would hope to schedule a tranisition call for the 3rd week in July with a publication date soon afterwards.

PC: That long?

<janina> pc: Any chance to do this sooner? Unfortunate to wait well into July?

<janina> pc: But, it is July!

<janina> ms: That's it.

MS: We've done preliminary scheduling and there are a lot of vacations

PC: LC for HTML closes August 15, so longdesc should still be ahead of that

Canvas 2D; Status, TF Liaison

->http://lists.w3.org/Archives/Public/public-html-a11y/2014Jun/0052.html Canvas Sub Group minutes

<JF> scribe: JF

MS: Canvas group met this week, good progress

<MarkS> Issue 300223009: Implement basic parts of hit regions on canvas2d

Firefox and Chrome supporting DrawFocus and activity around Hit Regions

MS: hope to see implementations dropping soon
... testing on Safari as well, and tests passed
... asked HTML WG about what to do with this highly functioning group. Suggestion to create a TF under the html wg

<MarkS> Draft Canvas Task Force Work Statement

MS: standard TF work statement - mentions liasons with allyTF

<MarkS> scribe: MarkS

<JF> JS: this will cease being a sub-team of this TF, and will become a larger TF within HTML WG

<JF> JS: mostly management changes

JS: there is canvas in SVG2
... learned this week

JB: How does that work? canvas in SVG. anything we need to watch out for?

JS: didn't go into details. Rich mentioned it as an example of how SVG is expanding past SVG 1
... the PF interest is to continue to formalize relationship with SVG group and mapping, etc.
... we've had a lot of interest in a11y people participating in that work

<ShaneM> SVG2 has a section on embedded content at http://www.w3.org/TR/SVG2/single-page.html#chapter-embedded

JS: good to see implementations coming along

PF's Strong Semantics Issue

JS: this was a good exercise. teased out some details we needed.
... wondering from Paul and Judy have to say regarding this issue and the future of html5 and html5.1 etc
... as HTML exits CR and returns to 2nd LC, we took a look to make sure PF was happy. ARIA sub team people focused on strong semantics setction
... worried that advise was not sufficient enough for developers
... CfC in PF asked for testing results to validate, or mark section as informative
... SteveF developed tests that proved good results, not 100% but about 90% passed
... there is an email from steve with up to date test results and bugs that have been filed.

<aardrian> http://lists.w3.org/Archives/Public/public-pfwg/2014Jun/0126.html

JS: wondering if this is something we can still handle in html5.0 or 5.1
... one of the other ARIA members noticed there were some missing aria-attributes
... wondering how we handle that

<paulc> I think we should file bugs and let the Editors process these and propose whether they will be included as LC bugs. Then the filers can decide if the processing is appropriate.

JS: should we just mark the items currently at risk?

PC: bugs may be moved into LC component by editors. Can talk to editors about that. Can be handled in LC

MS: I have already filed bugs on behalf of Brian

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26090

Implicit ARIA semantics for the <ol> and <ul> elements should include radiogroup

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26089

Implicit ARIA semantics for the <li> element should include radio

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26088

Implicit ARIA semantics for the <a> element should include radio and option

JF: there was email about strong semantics, aria in html, regarding form inputs. strong semantics in aria seemed to be in conflict with HTML

JS: Steve is actively testing, his work may reveal something like that. You might want to confirm with him. Please do it on list

Media Subteam

MS: Hope to publish a Heartbeat one week from today, June 26
... Media Accessibility User Requirements

JS: this will include all the input from comments since FPWD
... sorry it took so long, but the group was dormant for quite some time
... meeting with the Web & TV IG. They are asking for feedback and input from us, which is good.
... next activity will be to get test content for tool and UA developers that has sample alternative content

MS: presentation from Clarke Steves from cable labs on standards for labeling AD

JS: we saw no conflict there and are glad to see progress

SM: the SAP track in Canada is labelled middle english

HTML 5.1 Next Steps

JS: Leonie and I are scheduled to present next week on WebRTC but I won't be able to present next week because I will be at the Web of Things workshop. Will need to push that back. one more week, 7/3
... there are many presentations scheduled for July. Please try to keep those due dates

->https://www.w3.org/WAI/PF/HTML/wiki/51wishlist wishlist and due dates

JS: please use the wiki to share your research

Other Business

JS: chair for next week. Mark?

MS: I can chair next week

SM: I can scribe

[adjourned]

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2014/06/19 15:39:09 $