See also: IRC log
<trackbot> Date: 27 August 2014
<janina> Meeting: PFWG telecon
<janina> agenda: this
<scribe> scribe: jongund
JF: I moved
... In apartment now
JS: Hopefully pleasant, with connectivity
JF: Happy with connectivity
JS: 2 minutes
JS: Any corrections or
additions?
... Any objections to publishing
JF: I support
resolution: publish minutes as submitted
JS: TPAC, another group wants to
spend time with us
... The digital publish group, met with them to form a new
working group
... Web and TV interest group and HTML group
... There are other CSS, WebApp and IndieUI
... Any comments or questions
JF: Anything specific with CSS
JS: I though you were looking into it
JF: Me??
JS: Will discuss later
JS: Michael
MC: There are three actions from today, that are "find out if someone is implementing XXX"
JS: Need to look up an fix
Shane: Topic was zoom control...., meta item to block zoom control
MC: Need to change this
JS: Can we advance to next
week
... I will be on the call next week...
MC: This is a calendar widget
that goes monday through sunday...
... Need to update those actions
... Other spec review actinos
... The closest is due march 5th (this year)
JS: New publications
MC: CSS3 is published as last call, maybe a second last call
JS: We comented on the first last call, did they do anything with them
MC: We need to look at counter, I
can't remember when we sent comments
... Here we are
... Response from "atkins"
... We need to look at his response, he did not understand the
comment
JS: Who looked at CSS counters?
MC: I will have to find the
action
... "COunter" Lisa Seaman reviewed it
... LS reviewed it and then I got a wording action, it is also
closed
... My conclusion was that this is WCAG techniques
JF: At a meta level this is generated content
MC: It is a constrained class of
generated content, but it is generated content
... If the counter ..., you can use speak as on how it should
be pronounced, there are speak defaults...
JS: I don't recall, we should action LS to review
JF: I have asked to work with the
CSS working group, do we have a list of other issues?
... If we have a couple hours with them...
JS: It comes to use from the last call process, and not from a working group joint meeting
JF: We seem to have an open question from the CSS working group
JS: Waiting for a joint CSS meeting may take a long time
MC: We have last call response time constraints
<MichaelC> ACTION: Lisa to review CSS Counter Styles Level 3 http://www.w3.org/TR/2014/WD-css-counter-styles-3-20140826/ - due 2 weeks [recorded in http://www.w3.org/2014/08/27-pf-minutes.html#action01]
<trackbot> Created ACTION-1503 - Review css counter styles level 3 http://www.w3.org/tr/2014/wd-css-counter-styles-3-20140826/ [on Lisa Seeman - due 2014-09-10].
<MichaelC> action-1503: There are open questions for a previous review, see https://lists.w3.org/Archives/Member/wai-liaison/2013Nov/0000.html
<trackbot> Notes added to action-1503 Review css counter styles level 3 http://www.w3.org/tr/2014/wd-css-counter-styles-3-20140826/.
MC: Creating action for Lisa review CSS counters in next two weeks (MC created)
JS: We may have a meeting with LS in the next hour
<MichaelC> action-1503: may have last discussed 9 July 2014 https://www.w3.org/2014/07/09-pf-minutes.html#item10
<trackbot> Notes added to action-1503 Review css counter styles level 3 http://www.w3.org/tr/2014/wd-css-counter-styles-3-20140826/.
MC: There is a spec on predefined counter styles, lists of various counters...
JS: Tie to last action?
MC: Maybe
... This document defines localized list styles, it is not REC
track, maybe we do not need to worry about
JS: Rich is not here? Rich?
... We did have a meeting monday with the digital publishing
group, markus and other people
... Drafting a a charter for a working group related to added
vocabulary to ARIA related to semantic structure
... Shane?
Shane: It turns out that HTML5 excludes alternative vocabularies, even though we designed are spec
MC: They defer to PF for defining the vocabulary
Shane: We can add stuff that is prefixed
MC: That would be harder to sell, if we wanted to ...
RS joined
JS: Do we have authority to add roles?
Shane: We can, but epub can't
JS: That why they are working with us
RS: Thats one of the reasons
JS: You were very careful not to say "namespaces"
Shane: Vocabulary is the
word
... namespace refers to elements, not attributes
JS: The goal is to have a draft
by mid september, they are highly motivated
... There is a parallel push to printing to paper, which
combines HTML+CSS, it is an interesting parallel process
Shane: There is XHTML Print spec, it is a place to start
JS: Any other questions or
comments?
... RS we talking about ARIA, anything else
RS: We are working on the API
mapping specifications, we have an issue with name
computation
... In order for each specs (e.g. HTML and SVG), we do not
replicate the ..., name calculations of names are tied to the
host language, for example "alt" does not exist in
SVG....
... They don't support CSS :before and :after
... We could create separate specs on name computation for HTML
and SVG
JS: Will DPUB need it?
RS: For the moment they just want
roles, nothing that affects name computation
... At least for now it is a host name module...
... That for me is the write way to do it, but can we do
it?
MC: I am pretty sure we can, we have room in the charter
RS: We need to think about exit
criteria for ARIA 1.1
... If ARIA 1.1 points to the core spec, what we have to
conforms to is important...
JS: Lets not deep dive into this now
MC: I extend the core, I don't think testing the core, does not require testing the mapping specs, but testing mapping specs requires testing the core
RS: We would test with HTML5
MCL We have said all along ARIA 1.1 is HTML 5 specs
JS: We have two more topics to
discuss today
... ANy other comments?
MC: We have longdesc is in CR
JS: We actually got CR to do what
CR was suppose to do
... Worst case may require some changes, all the implementation
pieces are covered, we lost the calendar, ...., get a good
spec
... My vote tomorrow will be exposing links to accessibility
APIs, that is the wrong answer for other APIs..., wire into
applications
... JF is this make sense to you?
JF: That's an accurate overview of where we are right now
JS: We need to say what we really
mean for each environment
... Joanie has concerns about using fragments
... Fragments are a starting point, but not an end piint
Shane: Basically it comes down,
we really need a way to get event handlers, jquery has a way to
do this
... 2 Ways
... The DOM group is one, they say there is a potential for
abuse
... There is always a chance in the DOM for abuse
... Event handlers could be replaced, for example a script that
processes "passwords"
... This can already be done, this just makes it easier
... There is a performance issue, mainly if you want to know
about ancestors
... These are the two main issues
JS: You have some different approaches
Shane: Can we extend the DOM??
JS: How bad do we want to this?
Shane: JG has a use case
RS: Yes we want to know if there are device specific handlers, for example the keyboard event handlers
JG: Evaluation and quality
assurance tools need to know about events on DOM nodes
... I think it will make it alot easier for people to develop
QA and evaluation tools
RS: If people use Indie UI this
is less of a problem
... It would be good to enumerate handlers
JS: Discuss on a monday call
Shane: We have tools and Oracle I bet has test tools
JS: We need to get people to work on this and the timing of requests
RS: With this be the DOM event handlers?
Shane: My action was to determine this, this would be in the DOM
RS: DOM events or DOM spec
Shane: DOM spec
RS: I think we need this
... The original request was from 1998
... Think about it this way,say we write a spec..., if your
going to implement an ARIA role than you need to test if it has
IndieUI event
... We need this for IndieUI
JG: You need also to know if an element is interactive
JS: We need to go write an
extension spec
... To start the process we will put on the agenda soon
... We are past the hour