Accessible Platform Architectures Working Group Teleconference

13 May 2020


jasonjgw, janina, scott_h, Joshue, Judy, SteveNoble


Accessibility of remote meetings.

<scribe> scribe: janina

jgw: Notes Judy's recent changes ready for discussion

jb: Trying to get the page to make more sense to random visitors unfamiliar with W3C-speak
... Also wanted to take a casual tone
... Also worked on formatting -- nesting levels, etc
... Wanted to point to what people might expect, specifically what existing WAI guidance may be applicable so moved up WCAG section
... Also added an Intro
... We need to include comments guidance
... Also how to participate, etc

<Joshue108> JS: We have some standard language from the CAPTCHA doc.

<Joshue108> JB: We need a Github repo?

<Joshue108> JS: We have one.

<Joshue108> Going to suggest language..

js: For comments, use standard APA ...

To comment, [29]file an issue in the W3C apa GitHub repository. If this is not feasible, send email to [30]public-apa@w3.org ([31]comment archive). In-progress updates to the document may be viewed in the [32]publicly visible editors' draft.

jo: Coming together nicely. Covers issues and ongoing relevant work in RQTF

jb: Remaining todo include cross links to other docs

+1 to cross links!

sr: Likes the doc, very useful
... Notes last point at bottom; to expand media reference

jb: Clarifies that any WCAG 2.2 additions would be in text for existing SC

jo: Would not want to add to this

jb: Notes many orgs creating tips docs; but we have the ability to move guidance into our technical docs
... Asks whether any objections to WCAG 2.2 guidance being up top

jgw: That's where it should be

[structuring discussion]

<Joshue108> JS: I've a general reaction

<Joshue108> Seems like the actional stuff is more important to highlight..

<Joshue108> The gap stuff is things that we need to figure out.

<Joshue108> Thinking of the audience, it needs to be something they can apply now

<Joshue108> JS: We may not have written it up yet..

<jasonjgw> Janina: notes the interoperability advantages of WebRTC with the user agent of choice.

<Joshue108> But one of the strongest reasons we support RTC is the interoperabiity you get with your browser of choice

JO and JS agree to write up a brief pointer section to RAUR and other benefits of implementing RTC standards related tech

<Joshue108> ACTION: Josh and Janina to write up a brief pointer section to RAUR and related docs on the benefits of using RTC standards etc

<trackbot> Created ACTION-2255 - And janina to write up a brief pointer section to raur and related docs on the benefits of using rtc standards etc [on Joshue O Connor - due 2020-05-20].

<Joshue108> https://github.com/w3c/apa/

<Joshue108> https://github.com/w3c/apa/issues

<Joshue108> public-apa@w3.org

<Joshue108> JW: Some of these things could end up with coming into RAUR, Josh will you have a look?

<Joshue108> JOC: Yup

Summary of Action Items

[NEW] ACTION: Josh and Janina to write up a brief pointer section to RAUR and related docs on the benefits of using RTC standards etc

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2020/05/13 14:02:27 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: jasonjgw, janina, scott_h, Joshue, Judy, SteveNoble
Present: jasonjgw janina scott_h Joshue Judy SteveNoble
Found Scribe: janina
Inferring ScribeNick: janina
Found Date: 13 May 2020
People with action items: janina josh

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

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]