W3C

- DRAFT -

SV_MEETING_TITLE

18 Apr 2016

See also: IRC log

Attendees

Present
Janina, JF, fesch, ShaneM, ryladog
Regrets
Chair
Janina
Scribe
ShaneM

Contents


<scribe> ScribeNick: ShaneM

COGA Issue Review

ShaneM: Do alerts generally need to stay there until they are achnowledged?

janina: I am not aware. I dont know WCAG well

LJWatson: not unless it falls under time-sensitive content.
... what would you do with a hidden live-region notification?
... requirement might need to take visibility in mind.

<scribe> ACTION: ShaneM to pull key issues out of the COGA payments. [recorded in http://www.w3.org/2016/04/18-apa-minutes.html#action01]

<trackbot> 'ShaneM' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., smccarro2, smccarro).

<scribe> ACTION: smccarro2 to pull key issues out of the COGA payments. [recorded in http://www.w3.org/2016/04/18-apa-minutes.html#action02]

<trackbot> Created ACTION-2024 - Pull key issues out of the coga payments. [on Shane McCarron - due 2016-04-25].

<scribe> ACTION: janina to extract key issues from the mobile documents. [recorded in http://www.w3.org/2016/04/18-apa-minutes.html#action03]

<trackbot> Created ACTION-2025 - Extract key issues from the mobile documents. [on Janina Sajka - due 2016-04-25].

API & Payments Architecture Review

People have not reviewed yet. Keep in mind that it is mostly about browser payments. Not a general case architecture document.

Ryladog: we have an opportunity to maybe talk with manu about this. he had a formal objection for other reasons. Specifically on the browser payments API maybe there is room to effect change.

ShaneM: not set in stone yet. Just FPWD.

Other Business

next and future meetings

May second for the next meeting.

Mobile Docs Review

janina: R&D Working Group document seems out of date 4 years later.

Proposed WCAG extension for mobile covers some of what we will cover, but not necessarily all of the use cases. Things like what content is represented in what order, for example.

trackbot, end meeting

Summary of Action Items

[NEW] ACTION: janina to extract key issues from the mobile documents. [recorded in http://www.w3.org/2016/04/18-apa-minutes.html#action03]
[NEW] ACTION: ShaneM to pull key issues out of the COGA payments. [recorded in http://www.w3.org/2016/04/18-apa-minutes.html#action01]
[NEW] ACTION: smccarro2 to pull key issues out of the COGA payments. [recorded in http://www.w3.org/2016/04/18-apa-minutes.html#action02]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/04/18 17:39:59 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found ScribeNick: ShaneM
Inferring Scribes: ShaneM
Default Present: Janina, JF, fesch, ShaneM, ryladog
Present: Janina JF fesch ShaneM ryladog

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 18 Apr 2016
Guessing minutes URL: http://www.w3.org/2016/04/18-apa-minutes.html
People with action items: janina shanem smccarro2

[End of scribe.perl diagnostic output]