See also: IRC log
<trackbot> Date: 10 December 2014
<janina> agenda: this
<janina> scribe: Fred_Esch
<MichaelC> Colour blindness accessibility Community Group
mc: : color blindness community group is of interest
RESOLUTION: publish minutes as submitted
Janina: next week will be last meeting of the year
<scribe> ACTION: 1536 to shane [recorded in http://www.w3.org/2014/12/10-pf-minutes.html#action01]
<trackbot> Error finding '1536'. You can review and register nicknames at <https://www.w3.org/WAI/PF/Group/track/users>.
mc: : goes through actions
<MichaelC> action-1536: http://www.w3.org/TR/mixed-content/
<trackbot> Notes added to action-1536 Review mixed content for a11y concerns.
mc: expects lots of publications next week
rs: does MC need to move SVG docs?
mc: yes, I will move it next week
janiana: 3 years ago... we started looking at this, what is our intent?
<MichaelC> Placeholder page on Touch a11y mapping
<janina> Lisa, 92473#
<janina> yes?
rs: we talked about device
independence... are we concerned about accessibility?
... interaction model discussion
... we may not need a separate mapping as each platform has
intellectual property...
... need a way for platform independent actions
... whether we have an API for actions, is that enough?
... has a spreadsheet what apple supports
janina: we are beyond keyboard input, needs to be in indy UI group
rs: it would be nice to have same
terminology for device independent groups
... maybe modules should be the way to address responsive
input... since we have overlap of groups
mc: : we talked about doing a placeholder doc ... not sure what the documentation should look like
janina: will discuss in indy UI
work group next week
... and will dove tail with web events...
<Zakim> MichaelC, you wanted to ask about pointer events and outcome of touch events cg
mc: communities are confused...
janina: we think indy UI should
do it, in coordination with other groups, concerned about
IP
... knows what to do on next steps
mc: sent a comment to css, about making focus outline invisible, asked for a warning in the spec
<MichaelC> As the outline on elements in the ‘:focus’ state is depended on by keyboard users for interaction with the page, authors should not make the outline invisible on such elements without making sure an alternative highlighting mechanism is provided.
mc: add warning to authors
RESOLUTION: accept css resolution to CSS issue 43
<ShaneM> http://www.w3.org/TR/2014/WD-mixed-content-20140722/
sm: description of section
4.3
... is there any requirement to expose mixed content, via
AT?
... explains mixed content - secure content which might contain
insecure, possibly brought in from another site...
rs: what is the value of knowing it is a mixed site?
sm: you can block some mixed content if you want, like media that may come from somewhere else
janina: should be uag\
rs: browsers dont implement
UAAG
... they need to follow WCAG.
jn: provides example of mixed content, concern of third party services (auto captions...) where the media comes from secure content but the captions come from a non secure source
<Zakim> JF, you wanted to comment on the impact ehre for third-party "audio descriptions", etc
<Zakim> jamesn, you wanted to ask if browsers expose the secure/insecure info to AT at the moment
<jamesn> ok
rs: wants to ensure we accessible - AT already expose stuff like this
<Zakim> ShaneM, you wanted to ask if we should be commenting to this group or someone else?
<janina> Shane's suggestions at:
<janina> http://lists.w3.org/Archives/Public/public-pfwg/2014Dec/0090.html
mc: sending comment (on time) content from Shane's email
RESOLUTION: Michael will send opening comments per Shane's email
janina: ARIA new day tomorrow, authoring meeting in old ARIA time on Mondays
jf: has concern on heartbeat
janina: some issues, but we need to get group consensus when we have issues
rs: there are lots of issues in
the heartbeat
... we are months away from recommendation...
jf: just commenting on thread...
mc: will bring back conversation on xtech, to pf list
<JF> need clarity around definions and difference between UI and GUI
all: discussion on heartbeat issues
rrsagent make minutes