W3C

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

14 Mar 2018

Attendees

Present
Joanmarie_Diggs, janina, tdrake, MichaelC, JF, gottfried
Regrets
Chair
janina
Scribe
gottfried

Contents


<scribe> scribe: gottfried

Agenda Overview; Announcements

<janina> .

John: Conversation with Sam Goto, engineer at Google.
... Making forms better by attaching metadata to form inputs.
... Merging forms together by responding to voice input.
... Strong metadata for form inputs. WCAG criterion and personalization.
... Microdata is brittle and breaks at scale. Google does not look at it strongly.
... Can Sam join our group?
... He is interested, and he is paid by Google. Will benefit our work.
... Where should we ask him to join? APA, AG?

Michael: Personalization is in ARIA.

Janina: Coga is joint APA & AG
... but not specifically about metadata, but including.

John: Coga work seems fitting to the metadata topic.

Ted: Why is personalization in ARIA?

Janina: Historical reasons. Not clear if personalization will become an ARIA module.

Michael: Issue is being sorted out in the personalization tf.

John: Preference for ARIA?

Janina: Yes, for historical reasons.

John: At some point, it might be good to have a discussion on the larger topic of addressing the needs of persons with cognitive.
... We have two task forces that seem to have overlap.

Janina: There are different people.

<joanie> https://github.com/w3c/personalization-semantics/issues/54

Janina: We will do it.
... You want him to talk to Michael.

Michael: TV Raman can nominate him, and then i need to add him to the tf.

Janina: Charles is the facilitator

Next & Future Meetings -- Suggesting 28 March

<JF> +1 to no meeting next week

Michael: Janina suggests that we not meet next week due to cSUN.

<janina> Dailing back ...

(no objection)

No meeting next week. N

Next meeting on March 28.

Captioning Followup

<janina> http://lists.w3.org/Archives/Public/public-apa/2018Mar/0000.html

Janina: Proposed response from TTML.
... Is the specific response adequate?
... Does it cover all?
... Especially request to Gottfried.
... Is the title okay?

Gottfried: Will respond by email today.

John: The concern about scaling was understood. TTML now points to MAUR. That's a big win.

Janina: Would be nice to sound more positive, i.e. "supports ...".

John: That's editorial nature.

Janina: Please send comments to me this week.

W3C Spec Template Redesign http://lists.w3.org/Archives/Public/www-style/2018Feb/0064.html

Michael: They are doing another redesign of the TRs.
... There were some a11y problems in CSS in the last rounds that we did not catch. Hopefully they will be addressed now.

<janina> Fantasie email about this at:

<janina> http://lists.w3.org/Archives/Public/www-style/2018Feb/0064.html

Michael: Also redesign on other aspects, e.g. masthead. Could potentially introduce new a11y problems.
... Basic instructions for participating are in the message.
... To what level should we be involved?
... If we fail to provide feedback in their timeline, we won't have a chance later.

<Zakim> JF, you wanted to note we must ensure a horizontal review before launch

John: W3C process has horizontal reviews. It cannot launch until this has happened.

Michael: They need to solicit for horizontal review, not to obtain.
... They may only give a few weeks. We have the obligation to provide early review.
... Don't think there will be an explicit horizontal review.

John: Who is them?

Michael: Project led by W3C staff. Other contributing, and students.

John: I am concerned about that they are not mandated to receive horizontal review.
... How can we do this?

Janina: That's an AC question.

Michael: They will solicit review, and as long as their timeline is reasonable, it is on us to deliver.

Janina: We all agree on this. Need to look at the issues.

CSS Updates -- Ian

Ian is not present.

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

action-2123?

<trackbot> action-2123 -- Ted Drake to Triage changelog of dom 4.1 https://www.w3.org/tr/dom41/#historical-changes-fpwd-dom4 - note stuff on mutation -- due 2018-01-24 -- OPEN

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

Ted: Haven't been able to work on it.

Michael: They could go to CR at any time.
... Would be good to put notes on the action page.

Janina: Link this from Shadow DOM?

<MichaelC> action-2052: also note review of DOM 4.1 action-2123

<trackbot> Notes added to action-2052 Review https://www.w3.org/tr/shadow-dom/ shadow dom.

Janina: We are planning to have Charles talk to us about Shadow DOM after CSUN

<MichaelC> action-2123: Ted to put notes in wiki and close action

<trackbot> Notes added to action-2123 Triage changelog of dom 4.1 https://www.w3.org/tr/dom41/#historical-changes-fpwd-dom4 - note stuff on mutation.

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

<MichaelC> CSS Text Decoration Module Level 4

First public wd

Michael: You could probably do bad things to accessibility, but it is not inherent to the spec.
... Like thick strike-through.

Janina: I don't want to go without having Ian present.
... No need to review.
... We have enough serious stuff.

<MichaelC> Custom Elements

Michael: We were concerned about this - know we don't know how it will proceed.

Janina: That's part of our conversation with Charles. Shadow DOM and Customs.

<MichaelC> HTML Accessibility API Mappings 1.0

Michael: ARIA wg will review this.
... Don't know if they are also reviewing HTML API mappings.

Joanmarie: We will include HTML.
... Most people in ARIA wg don't have the knowledge to review the mappings.
... But i am going to review.
... And there are other people that can do this.

Janina: Can APA ask them officially?
... Then it bounces back here

<MichaelC> Text Layout Requirements for the Arabic Script

John: Shadi?

Michael: I don't think we need to do a formal review
... No need to review for APA

<MichaelC> WebAssembly Core Specification

Michael: I think i should have set that as assigned.

APA Verticals -- Continuing discussion

Janina: We wanted to reduce the roaster to have one name per vertical.

Michael: (going through the list)
... Mixed reality has no name.

Janina: Ask RQTF?

Ted: I am looking at a change in my work. Might have more availabilities.

<MichaelC> iJanina: We wanted to reduce the roaster to have one name per vertical.|https://www.w3.org/WAI/APA/wiki/Verticals_to_Track|

Michael: Lead for e-learning?

John: Pearson Publishing involved?

Michael: Our main contact left Pearson.
... Shadi has been doing work in Web of Things.
... We should ask him to lead Web of Things.
... Graphics tf not active anymore.
... Next step will be to assign tasks to each person leading a vertical.
... Like writing a plan, who do we want to recruit, and how?

Other Business

No other things

Janina: We are done.

We will meet two weeks from today.


. Janina

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/03/14 16:59:45 $

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/being/having/
Succeeded: s/chair:/./g
Default Present: Joanmarie_Diggs, janina, tdrake, MichaelC, JF
Present: Joanmarie_Diggs janina tdrake MichaelC JF gottfried
Found Scribe: gottfried
Inferring ScribeNick: gottfried
Found Date: 14 Mar 2018
People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]