Accessible Platform Architectures Working Group Teleconference

25 Oct 2017

See also: IRC log


janina, MichaelC, Mark, Wilcock, JF, IanPouncey, tink
john, gottfried, Joanie
JF, tink


<JF> scribe: JF

preview agenda with items from two minutes

JS: basic agenda.

Good news - new member for/at APA. [Introductions]

Welcoming Mark Wilcock

TPAC 2017 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017

<janina> https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017

JS: beginnings of an agenda

Monday is looking quite full - if there is something that you are directly participating in please be sure that times work for you

JS: there are still things coming that aren't on the calendar

ie. having a chat with the automotive folks (ref: a11y and autonomous driving cars)


JS: is Monday morning a good time to prep for this, in anticipation of a Tuesday joint-meeting?
... Charles LaPierre and others from Publishing have some requests related to that as well

IP: yep, sounds fine
... sadly behind on github issues - will address that this week
... have started working on an agenda for our joint meeting with CSS WG

AGenda so far: introductions, the history of the TF, progress and recent push

where we are, participants, and hopefully a call for help

the real "meat" however is to discuss known issues/concerns, as well as seek input on future requests

also, how to most effectively intergrate withtheir WG

JS: questions?
... Introductions will need to be brief when we meet with that group - anticipate a large turnout
... agenda sounds good - can Ian share that so that we can forward it along?

do we want to focus on any particular issues? (highlight things that need to be worked on now)

i.e. media queries issue/concern

IP: yes, the key goal is to gain focus and clarity on topics

JF asking if we might invite EO to the meeting?

IP: can add agenda item to discuss whether or not to involve EO...

whether we invite them or not TBD - perhaps have a chat with EO post TPAC

JS: we can talk about that during the prep time
... we will only have an hour, so this may not yet be mature enough

<tink> scribe: tink

IP: I'll work on a list of initial topics, and will circulate.

Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8


<trackbot> action-2153 -- John Foliot to Review and draft a warning note for orienation api spec, for apa review -- due 2017-10-25 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2153


<trackbot> action-2151 -- Janina Sajka to Review permissions https://www.w3.org/tr/permissions/ -- due 2017-10-18 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2151

JS: Still looking at it.


<trackbot> action-2123 -- Shane McCarron to Triage changelog of dom 4.1 https://www.w3.org/tr/dom41/#historical-changes-fpwd-dom4 - note stuff on mutation -- due 2017-04-19 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2123

MC: There is a new draft out.
... Shane is helping Joanie with ARIA testing.
... Should reassign?
... Becky Gibson may rejoin.
... We have actions older than a year.

kim, take up next item


new on TR http://www.w3.org/TR/tr-status-drafts.html

<MichaelC> Tracking Preference Expression (DNT)

MC: Tracking Preference Expression spec.
... Are we interested?

JS: Think not.

MC: CSS Flexbox.

<MichaelC> CSS Flexible Box Layout Module Level 1

MC: Has gone to CR.
... Do we say anything?

LW: Have we said anything before?

JS: Discussion at TPAC 2015.

MC: We agreed at some point not to hold back Flexbox, because the same problem affects a group of similar specs.

IP: There is a common issue in the form of content order.
... Suggest drafting some suggestions about how that's documented.
... Should content order follow visual order for AT, or keyboard users etc.

MC: Do you think this would be best practice for authors?

IP: Two aspects, best practice for implementation, and then adequate documentation for authors to understand how it works.

MC: The most we could ask the spec would be an accessibility consideration section.

IP: We can file issues on each repo.

MC: With Flexbox in CR it'll get harder to change things.

IP: I'd like us to start writing some of this ASAP.

LW: Wonder if we're to late for UA guidance?
... Firefox had a good solution, though it was deemed to be a bug because of the spec language, but now they've reverted it.

MC: Not sure it's too late.

JS: Consensus seemed to be that rewriting the DOM was a problem.

LW: Firefox didn't rewrite the DOM.

MC: But if we can get the browsers to agree to do it the way Firefox did, that oculd be a way forward.


LW: There is an open issue on the W3 Process to require accessibility considerations in specs.

MC: So for Flexbox we're not going to do anything directly.

Other Business

JS: Anything?

MC: MC: We need to get the CAPTCHA document updated.

JS: Having trouble getting it to a point where Roy and Michael can work on it.
... Will try for this week.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/10/25 16:50:17 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/fols/folks/
Succeeded: s/kim, take up next item//
Succeeded: s/scscribe: tink/scribe: tink/
Present: janina MichaelC Mark Wilcock JF IanPouncey tink
Regrets: john gottfried Joanie
Found Scribe: JF
Inferring ScribeNick: JF
Found Scribe: tink
Inferring ScribeNick: tink
Scribes: JF, tink
ScribeNicks: JF, tink
Found Date: 25 Oct 2017
Guessing minutes URL: http://www.w3.org/2017/10/25-apa-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]