See also: IRC log
<trackbot> Date: 03 December 2014
<janina> agenda: this
<scribe> scribeNick: jamesn
First SVG Accessibility TF meeting scheduled for 9am on Friday 12 Dec
RESOLUTION: publish the minutes to the public list
reminder about end of year calendar
We are not meeting Christmas eve and not meeting NYE
Individual groups all make their own decisions
ARIA will not be meeting 25 and 1st
Week Dec 22 and Dec 29 will be busy otherwise... back to work on Jan 5. PF will meet Jan 7
ACTION-1552?
<trackbot> Sorry, but ACTION-1552 does not exist.
ACTION-1552?
<trackbot> Sorry, but ACTION-1552 does not exist.
ACTION-1522?
<trackbot> ACTION-1522 -- James Nurthen to Try to find an example where user style sheet cannot override author intent -- due 2014-11-19 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1522
<MichaelC> action-1522 due 2 weeks
<trackbot> Set action-1522 Try to find an example where user style sheet cannot override author intent due date to 2014-12-17.
leave open
MC: nothing that looks interesting
JS: DPUB has not gone up yet. they agreed to change the title
First SVG Accessibility TF meeting scheduled for 9am on Friday 12 Dec
<MichaelC> Character Description Language Community Group
This group will develop Character Description Language (CDL), an XML application for stroke-based representation of any CJK character.
JS: is it of interest?
MC: would this interfere with
accessibility of characters
... has applications for machine recognition, learning etc.
JS: they are trying to get the level up which could help a11y
MC: doesn't look like the group
is very active anyway
... sounds like we don't need to track
JS: New time, publications coming.
RS: we have a new aria 1.1 coming
out next week
... it is a heartbeat draft.
JS: also a FPWD
RS: got accessible name
computation in a seperate document. Other specs will refer to
that
... that 1 spec is very important and folks should take a
look
... there are a lot of things involved
... do we also produce something higher level for developers to
make it easier to understand
JN: would we put something more for devs in the authoring practices
RS: what they need is to know how
everything comes together
... need to know what order they are pulled in - how
concatenated together etc.
FE: wanted to understand how it would work with the authoring practices
JS: move to the procedural
questions
... do we have a persistent URI - is the document ready?
MC: they are github URIs
JS: will send out a Call for
consensus this afternoon
... 2 heartbeats and a FPWD
MC: have tweaked the abstract
JS: The Monday meeting is moving to Thursdays - same time.
RS: the more meaty topics will start 30 mins into the call
JS: we have changed the access code
92473 will go away
we will go to something that includes apa
aria call is now 2742
JS: trying to bring it down to 2
codes
... do we want to keep the traffic on public-pf or move things
around
CS: aapi was only on xtech to be public can move to public-pf
JS: has this been brought to the
council yet?
... my expectation is early in the year this will happen
RS: have you seen activity on the epub subteam starting?
JS: not out of epub actually starting up
RS: I
'm not pushing that foreward
JS: in that funny time of year
when things take longer
... the doc that JB came up with?
<janina> https://specs.webplatform.org/html-aria/webspecs/master/
<MichaelC> https://specs.webplatform.org/html-aria/webspecs/master/
<MichaelC> https://rawgit.com/w3c/aria-in-html/master/index.html
MC: anyone can publish stuff on
webplatform. Would have thought that this is related to the doc
in W3c space. The doc in the webplatform looks different
... Not sure what is going on
Abstract
This specification defines the web developer (author) rules (conformance requirements) for the use of [wai-aria] attributes on [HTML5] elements. It also defines requirements for Conformance Checking tools and a subset of requirements for UA implementers.
RS: They want to modularise HTML and this would be the basis for the ARIA module in HTML
CS: webplatform is a strange
place for this
... has anyone asked SF what the goal is?
JS: we may ask him to the TF call
CS: are you sure he is not just
playing around with things
... lets ask him
MC: the copyright looks
problematic
... you cannot waive w3c's copyright
RS: he does link to the aria spec
MC: things are being coped from the spec and we don't know if there is a proceudre in place to keep stuff up to date
I echo CS's comment to just ask him
MC: Bruce Lawson blogged abiut
web components about creating new elements to make them
operable including adding aria
... about all I can say about the issue
<MichaelC> http://www.brucelawson.co.uk/2014/on-the-accessibility-of-web-components-again/
CS: if anyone is an IAAP member
there was a webinar about this
... there were a few examples about this
MC: this is an in the wild experiment which is being conducted. If it gains traction without accessibility there would be a lot of work to do.
CS: was following this on webapps
JS: Isn't this similar to what Ben Peters is doing
CS: related but different
scenarios
... there is a PWD of something
link above is broken
change githubusercontent to git and should work
needs more than that
<MichaelC> https://github.com/w3c/webcomponents
MC: mung your own urls from the repos
<MichaelC> http://w3c.github.io/webcomponents/