See also: IRC log
<trackbot> Date: 21 February 2013
<janina> Meeting: HTML-A11Y Task Force Teleconference
<janina> Chair: Janina_Sajka
<scribe> scribe: MichaelC
js: CSUN conference taking place next week, many of us will be there
RESOLUTION: no meeting 28 February 2013
next meeting: 7 March 2013
js: discovered that the CfC pointed to an old revision
that didn´t include the changes mentioned in the CfC
have restarted the CfC with the correct URI
in both HTML WG and HTML A11Y TF
no objections yet
concerns raised around development path that we expect to take up in due course of that path
jb: so when would the new HTML CfC close?
end of day next Wednesday?
hopefully MikeS can still publish the following day, 28 Feb
other process steps that have to be done?
js: yes, some of the team publication steps aren´t done yet
mc: that could be front-loaded in advance of closing the CfC
jb: so guess it couldn´t get published until following week
mc: could in principle with negotiation with Webmaster and front-loading
pc: there is a backlog of HTML publications that needs to be cleared
treating first-come first-serve, this would be behind those others
jb: if we get other Team to help out can that help queue it up in advance?
pc: no problem in principle
note Transition Request needs a date, document, and short-name
sent by one of the chairs
mc: maybe could help out though don´t want to step on Mike / Robin
is this because of CSUN?
jb: not critical but want to demonstrate progress
js: just explaining that it´s legitimately in queue should be good
jb: ok
pc: will also try to push out the others
<paulc> lost contact
js: if the spec has a heartbeat, the obsoletion of longdesc might be gone
sf: not aware of plans for that
just extension specs right now
pc: will update admin list later today on the pub cycle
js: Steve asked to add a couple editors
noted off list that the candidates work for one organization; unsure of level of concern about that
meanwhile another name came forward that would balance
jb: it´s worth paying attention to that issue
glad for the multiple support offered
the balancing would help in workload and representation
considering representation between PF and HTML WGs
would like someone who´s in PF to ensure spec accuracy
sf: that´s about following the spec carefully, and responding to issues that are raised
js: the main thing we want to look at is not conflicting with the ARIA Authoring Practices
jb: in part the goal is to ensure the PFWG is stimulated to look more closely via one of these editors
js: PF has normative docs that are top priorities but is publishing update of Authoring Practices
important to coordinate content
sf: the main component of this document is the table that maps HTML elements to ARIA features
because that´s not clear in HTML spec alone
<Judy> Judy suggests that going forward, the "author" designation could be used to reflect Steve's role developing this doc, and that Gez and David be noted as Editors
js: suggest the editors of the various docs coordinate
jb: ^
sf: don´t plan to step away immediately, need to transition them in
can manage mechanical aspects while they help with content, keep it up to date
RESOLUTION: David MacDonald, Gez Lemon, Hans Hillen join Steve Faulkner as editor of Using WAI-ARIA in HTML
js: the TF co-facilitators have discussed with Robin Berjon
Section 4.8.1.1 deals with using alt in HTML, and has sub-sections
wasn´t clear this particular organization was the best presentation for a spec
also some of the examples weren´t ideal
and some guidance conflicted with WCAG recommendations
Robin said we should think through what the best presentation of this content within the HTML spec should be
then can look at how it relates to HTML-ISSUE-30 stuff
I plan to submit content explaining that @alt is in general the best way to handle text alternatives
but it doesn´t handle all cases
point to @longdesc extension spec and others
then need to look at the sub-sections, their order, content, etc.
will work this out on the HTML WG list
plan to work iteratively
because of CSUN, don´t expect progress for a couple weeks
sf: Robin wants to see that the content in the spec continue to be there, but that the form of it is subject to modification
is ok with updating the specific guidance of sub-sections
note this has been normative up to now
plan to keep base guidance normative but examples informative
js: agreed to leave some authoring guidance in
but limit to well-established practices
point elsewhere for guidance that requires more exposition
pc: is this for 5.0 or 5.1?
sf: initial plan was 5.1
when we arrive at consensus on contents, could port back to 5.0
pc: as a separate spec, or directly in HTML 5.1?
sf: directly in 5.1
... one push-back on normative requirements was on things that
can´t be machine checked
could be a reason to reduce some of the normative statements
since we plan to do this iteratively, not drop a whole bunch of changes in
perhaps section by section
we´ll have opportunity to build support piece by piece
js: early on we should address what the subsections should be and the order they should be in
then tackle them one by one
jb: W3C held a digital publishing workshop last week
jointly with International Digital Publishing Forum
well attended
lots of a11y interest
there was a dedicated panel on accessibility moderated by Janina
covered Digital Rights Management, haptics, aural CSS, educational testing
looking now at priorities and mode of coordination going forward
and which parts of W3C work are involved
js: ePub wants to be as close to HTML 5 as possible
need to get requirements to the table
has been done well with mobile
IDPF doesn´t have much staff availability to get involved
There was discussion on direct accessibility of graphical content
haptic was one idea
also work underway in SVG
understanding that @alt and @longdesc are workarounds, prefer to move to direct accessibility model
There was a lot of discussion of MathML
educational publishers really need it, and have done a lot of work to build support
but insufficient support in the browsers
suggestion made to fork the open source projects, though unsatisfactory
different ideas about how widespread it is
on the open Web not seen much
but in walled gardens, such as educational publishing, it´s widespread
that usage not always visible
Joining CSS FtF meetings will be one opportunity to explore requirements
CSS fonts, CJK relationship, line spacing
pc: so the more successful marketing of HTML 5 and Open Web is
the more communities like this we need to get on board
e.g., in the media space, dealing with a requirement to insert advertisements into the media stream
¨With success comes more work¨
jb: in the case of publishing, they´ve wanted to coordinate for a long time
only considered forking because W3C HTML was progressing slowly
so think there will be good motiviation to more forward on joint work
yes, does expand workload on all of us
There will be questions about what work comes to what parts of W3C
this TF may need to consider which pieces it gets involved in
js: hope this can recruit resources to W3C work
IDPF has good base of adoption
ePub 3 picked up DAISY
so we´re not starting from scratch
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/AAPI/ARIA/ Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Found Scribe: MichaelC Inferring ScribeNick: MichaelC Default Present: Janina_Sajka, Michael_Cooper, hober, Stevef, Judy, paulc, [Microsoft], Cynthia_Shelly Present: Janina_Sajka Michael_Cooper hober Stevef Judy paulc [Microsoft] Cynthia_Shelly Regrets: leonie Found Date: 21 Feb 2013 Guessing minutes URL: http://www.w3.org/2013/02/21-html-a11y-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]