MINUTES: APA WEEKLY Teleconference; Wednesday 13 November at 1700Z

MInutes from this call can be found here:
https://www.w3.org/2019/11/13-apa-minutes.html

...or below:

[11:01] <JF> agenda?
[11:01] * Zakim sees 9 items remaining on the agenda:
[11:01] * Zakim 1. Agenda Review & Announcements [from janina]
[11:01] * Zakim 2. Task Force Updates [from janina]
[11:01] * Zakim 3. Charter Updates
https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
[from
janina]
[11:01] * Zakim 4. new on TR http://www.w3.org/TR/tr-status-drafts.html [from
janina]
[11:01] * Zakim 5. HTML Review
http://lists.w3.org/Archives/Public/public-apa/2019Nov/0003.html [from
janina]
[11:01] * Zakim 6. Community Groups Tracking Review
https://www.w3.org/WAI/APA/wiki/Community_Groups [from janina]
[11:01] * Zakim 7. Actions Checkin (Specs)
https://www.w3.org/WAI/APA/track/products/8 [from janina]
[11:01] * Zakim 8. Other Business [from janina]
[11:01] * Zakim 9. be done [from janina]
[11:02] <joanie> present+ Joanmarie_Diggs
[11:04] <Joshue108> present+
[11:06] == Becka11y [~bgibson@public.cloak] has joined #apa
[11:06] * Becka11y is joining
[11:07] <JF> scribe: JF
[11:07] <JF> zakim, take up item 1
[11:07] <Zakim> agendum 1. "Agenda Review & Announcements" taken up [from
janina]
[11:07] <Becka11y> present+
[11:08] * Joshue108 just a heads up I will be driving soon but on the call.
[11:08] <JF> JS: standard agenda, with some persistent items (Matthew's
review of HTML, Becky's review of community groups)
[11:08] <JF> MA: know that Josh has done review of XR materials, will
tackle that this week
[11:09] <JF> JO: There has been some discussion at RQTF about this too
[11:09] <JF> JO: will be working on that later today / this week
[11:10] <JF> zakim, next item
[11:10] <Zakim> agendum 2. "Task Force Updates" taken up [from janina]
[11:10] <JF> JS: Josh mentioned the RQTF discussion earlier today - follow
up from the Immersive Workshop last week in Seattle
[11:11] <JF> JS: triggered some thoughts related to MAUR
[11:11] <JF> might need to split the document into multiple parts - getting
quite large
[11:11] <JF> JS: still awaiting the official W3C transcripts
[11:11] <JF> not yet released. Will advise when made public
[11:12] <JF> JO: Good summary. Have a sense that we are gaining critical
mass
[11:12] <JF> lots of interest in this topic
[11:12] <JF> JS: Also, the Pronunciation TF met today
[11:13] <JF> topics include future process... will be asking Leonie
(representing Web Plat) to an APA call, so that we can plan out
implementation and uptake for their spec
[11:13] <JF> this means we need to ensure we cover all the bases. As this
will be mainstream, we need to also figure out hand-off and timing (etc.)
[11:14] <JF> need to meet with Irfan et al regarding this
[11:14] <JF> we also discussed the wide, mainstream application being a
"nice to have", but if we don't get something that works for AT, we'll
still have come up short
[11:15] == Joshue108 [~joconnor@public.cloak] has quit ["Be back later"]
[11:15] <JF> Irfan discussed a F2F meeting @ CSUN. Discussed possibly going
to the ATIA conference in January
[11:15] <JF> JS: any other TF info?
[11:15] <JF> knows that Personalization is working towards publishing
[11:16] <JF> JO: hoping to have the accessible RTC doc ready soon as well
[11:16] <JF> zakim, next item
[11:16] <Zakim> agendum 3. "Charter Updates
https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22"
<https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22%22>
taken
up [from janina]
[11:16] <JF> JS: anything here?
[11:16] <JF> MC: yes, a few
[11:17] <MichaelC> -> https://www.w3.org/Payments/WG/charter-201910.html Web
Payments draft charter
[11:17] <MichaelC> ->
https://www.w3.org/Payments/WG/charter-201910-diff.html Web Payments draft
charter diff
[11:17] <JF> This group is continuing work... do not have a liason
statement to APA, even though we are working with them
[11:18] <JF> JS: we had discussed creating a power document for them at one
point...
[11:18] <JF> JS: since they've scoped this under the UI, there may not be
much for us. We did discuss the need for an "accessible" receipt. Pretty
much everything else is covered in WCAG
[11:18] <JF> MC: so, do they need a liason with APA?
[11:19] <JF> JS: I would "trade away" a Liason if Ian was prepared to add
the warning comment
[11:20] <JF> MC: don't want to conflate charter discussion with our "ask"
[11:20] <janina> Oops. brb
[11:21] <JF> MC: they have added a section related to accessibility
considerations. So we decided about a year ago that we could live with that
[11:22] <JF> JS: we might take that list and iterate on it here...
[11:22] <JF> MC: getting back to charter... do we have any comment to make?
Hearing that we need to do a follow-up on Payment Request API
[11:23] <JF> per charter that should be in the next version
[11:23] <JF> JS: for the statement that got incorporated
[11:23] <JF> MC: if we want something, we will need it soon
[11:24] <JF> ACTION Janina add accessible receipting to the accessibility
statement for payments
[11:24] * trackbot is creating a new ACTION.
[11:24] <trackbot> Created ACTION-2220 - Add accessible receipting to the
accessibility statement for payments [on Janina Sajka - due 2019-11-20].
[11:25] <MichaelC> action-2220:
https://www.w3.org/WAI/APA/wiki/Payment_Request_API
[11:25] * trackbot is adding a note to action-2220.
[11:25] <trackbot> Notes added to action-2220 Add accessible receipting to
the accessibility statement for payments.
[11:26] <MichaelC> -> https://w3c.github.io/dxwg/charter/index.html Data
Exchange WG draft charter
[11:27] <MichaelC> ->
https://w3c.github.io/charter-drafts/audio-2019.html Audio
WG draft recharter
[11:28] == florian_ [~florian_@public.cloak] has joined #apa
[11:28] * JF bonjour Florian
[11:29] <JF> [Discussion of reviewing Audio WG materials]
[11:30] <JF> MC: We've not provided much to them in the past. Do we want to
have a liason for this as well?
[11:30] <JF> JS: Wishing Joannie was here... wondering if we need to chat
with them
[11:31] <JF> JS: thinking we may need to have a mechanism for 'exclusion'
of TTS [sic], and other concerns
[11:31] * joanie says to JF: Joanie (one n) IS here
[11:31] <JF> MC: we need to figure out if we want a liaison statement from
them to us at this point
[11:31] * JF takes back an N
[11:32] <JF> s/liason/liaison
[11:32] * joanie says I'm also on the call. I spoke a couple of minutes ago
[11:32] * JF says I'm brain dead...
[11:32] <MichaelC> ->
https://htmlpreview.github.io/?https://github.com/grorg/admin/blob/wg-charter-draft/wg-charter.html
GPU
for the Web Working Group Charter
[11:32] <JF> MC: One last item, not yet ready for horizontal review, but
pending and may be of interest of us
[11:33] <JF> notice of interest for a new charter
[11:33] <JF> MC: thought we might be doing some work that relates to this
(?)
[11:34] <JF> JS: Thinks yes, as there is also a lot of AI there...
[11:34] <JF> MC: requesting comments as PR on tyheir draft charter
[11:34] <JF> s/tyheir/their
[11:35] <JF> JS: sounds like more discussion is needed, but we are missing
a key participant
[11:35] <JF> zakim, next item
[11:35] <Zakim> agendum 4. "new on TR
http://www.w3.org/TR/tr-status-drafts.html" taken up [from janina]
[11:35] <JF> MC: there are a few that are "stuck"
[11:35] <MichaelC> -> https://www.w3.org/TR/css-text-3/ CSS Text Module
Level 3
[11:36] <JF> there is a CSS module - we've looked previously and then there
was nothing, so...
[11:36] <JF> JS: if we didn't find anything previously, let's not go fishing
[11:36] <MichaelC> -> https://www.w3.org/TR/did-core/ Decentralized
Identifiers (DIDs) v1.0
[11:36] <JF> JS: the CAPTCHA killer
[11:37] <JF> MC: now is the time for a review. who should we assign this to?
[11:37] <MichaelC> action: janina to review Decentralized Identifiers
(DIDs) v1.0 https://www.w3.org/TR/did-core/ - due 4 weeks
[11:37] * trackbot is creating a new ACTION.
[11:37] * RRSAgent records action 1
[11:37] <trackbot> Created ACTION-2221 - Review decentralized identifiers
(dids) v1.0 https://www.w3.org/tr/did-core/ [on Janina Sajka - due
2019-12-11].
[11:37] <JF> JS: can assign to me
[11:37] <MichaelC> action-2221:
https://www.w3.org/WAI/APA/wiki/Decentralized_Identifiers_(DIDs)_v1.0
[11:37] * trackbot is adding a note to action-2221.
[11:37] <trackbot> Notes added to action-2221 Review decentralized
identifiers (dids) v1.0 https://www.w3.org/tr/did-core/.
[11:37] <JF> zakim, next item
[11:37] <Zakim> agendum 5. "HTML Review
http://lists.w3.org/Archives/Public/public-apa/2019Nov/0003.html" taken up
[from janina]
[11:37] <Matthew_Atkinson> Review of my review findings, including
short-term things and also matters in which I think we should be interested
and should be tracking:
https://lists.w3.org/Archives/Public/public-apa/2019Nov/0003.html
[11:38] <JF> JS: please start with largest concerns first
[11:38] <JF> MA: propose to discuss 4 major issues, then loop back to
existing questions
[11:38] <JF> MA: was invited to the WHAT WG a11y team @ GitHub
[11:39] <JF> MA: kind of cool
[11:39] <JF> only had one comment to advance: navigation in the opener not
being announced by AT
[11:39] <JF> believe we need to file an issue with a warning for authors:
screen readers likely won't know this is happening
[11:40] <JF> once I file on GitHub, will advise the list
[11:40] <JF> there is another issue that I'd like some opinion on
[11:40] <JF> +1 to MA's approach
[11:41] <JF> MA: Question - there have been some tweaks to tabindex
behavior - minor - one of things observed is that some browsers place the
video 'player' in the focus order, and then the controls
[11:42] <JF> which I think is good, as it speeds interaction (no need to
tab through all the controls)
[11:42] <JF> however there seems to be a discussion of taking the audio and
video elements *OUT* of focus order
[11:43] <JF> W3C prescedence is that those elements *are* focused, but WHAT
WG wants to remove that
[11:43] <JF> MA: is this an issue?
[11:43] <JF> +1 to keeping audio and video in focus order
[11:44] <JF> MA: the way that FF works today, if the page has the default
controls, the video is a "floating block", as are the controls - they folat
above (or below) the video player
[11:44] <JF> that is the practical behavior of both FF and Chrome
[11:44] <JF> Q+
[11:44] * Zakim sees JF on the speaker queue
[11:45] <JF> JS: don't want to rely just on "current practices"
[11:45] <JF> MA: agree. My concern is that some folks might see this as a
pro, but others as a con
[11:45] <Becka11y> q+
[11:45] * Zakim sees JF, Becka11y on the speaker queue
[11:45] <JF> MA: although the browser generated controls were less
accessible than I expected
[11:46] <JF> don't think the spec speaks to how they should be laid out -
the behavior was unusual
[11:46] <JF> think that either way, p[eople will have opinions
[11:46] <JF> ack me
[11:46] * Zakim sees Becka11y on the speaker queue
[11:46] <janina> q?
[11:46] * Zakim sees Becka11y on the speaker queue
[11:46] <janina> ack jf
[11:46] * Zakim sees Becka11y on the speaker queue
[11:47] <JF> JF: suggest to use the "Pave the cowpaths" metaphor. If this
is current behavior now, it should be 'specced' as such
[11:47] <JF> MA: wil review again to make sure this isn't a recurring issue
[11:48] <JF> if this doesn't match relaity, will use the "shold match"
argument
[11:48] <JF> MA: do we think this should hold up publishing
[11:49] <JF> BG: only concern is if they mandate "taking away"... they
currently don't. But what happens when they land on the video? Does it
announce the title, or also announce the controls
[11:49] <JF> JB: the screen reader may or may not give enough of accurate
information
[11:49] <JF> BG: not every user goes line-by-line, they may be tabbing
instead
[11:49] <Becka11y> ack becka11y
[11:49] * Zakim sees no one on the speaker queue
[11:50] <JF> JB: we might also argue that this is a SR bug
[11:50] <JF> JB: have seen previousl giant "hacks" to try and force SR
behavior
[11:50] <JF> MA: so, am I hearing everyone in favor of keeping video and
audio in focus order
[11:51] <JF> JB: "personally" thinks it could go either way, but...
[11:51] <JF> but if everyone outside of us says it *SHOULDN'T*, screen
readers have other mechanisms to deal with concern
[11:52] <JF> JB: this is all about containers at some level, so ya, we can
figure this out
[11:52] <joanie> s/JB:/JD:/
[11:52] * joanie says to JF Joanie Diggs
[11:52] <JF> MA: OK, so when I file this, the "bug" is that the spec
doesn't match the browsers, and then we can offer some suggestions
[11:52] * JF sorry Joanie.. can I just say "Hey you!"...?
[11:52] <joanie> s/JB:/JD:/g
[11:53] * joanie says to JF I prefer "She who mustn't be named" :)
[11:54] <JF> MA: Not clear if the scrubber control comes into focus...
clear that there is a bigger discussion here we need to think through
[11:54] <JF> MA: I think I have enough to file a bug, but... should this be
a delay to the publication?
[11:54] <JF> MA: believe no. Is this a show stopper
[11:58] <JF> JF: either there is a bug filed against the spec, or against
the browsers...
[11:58] <JF> MA: asking about process
[11:58] <JF> MC: File in WHAT WG, and a reference issue at W3C. Not sure if
this snapshot would be turned into a rec
[11:59] <JF> JS: yes, and don't want to wait a whole additional year
[11:59] <JF> MC: OK, then file bug at WHAT WG
[11:59] <JF> MA: will email list later today. Will note that we feel it is
an issue, and advise of forthcoming GitHub issue (to be filed tomorrow)
[12:00] <JF> and then link to the bug on our lists
[12:00] <JF> [agreement on Matthew's plan]
[12:01] <JF> MA: two other concerns in the email - won't discuss now, but
there are some other things believe we should be tracking
[12:01] <JF> please read and check out the concerns
[12:02] <JF> JS: standing agenda item. We may need to put Becky ahead of
you on next agenda
[12:02] <JF> RRSAgent, make logs public
[12:02] == Becka11y [~bgibson@public.cloak] has left #apa []
[12:02] <RRSAgent> I have made the request, JF
[12:02] <JF> trackbot, end meeting
[12:02] * trackbot is ending a teleconference.
[12:02] <trackbot> Zakim, list attendees
[12:02] <Zakim> As of this point the attendees have been JF,
Matthew_Atkinson, Joanmarie_Diggs, Joshue, Becka11y
[12:02] <trackbot> RRSAgent, please draft minutes
[12:02] <RRSAgent> I have made the request to generate
https://www.w3.org/2019/11/13-apa-minutes.html trackbot
[12:02] <trackbot> RRSAgent, bye
[12:02] <RRSAgent> I see 1 open action item saved in
https://www.w3.org/2019/11/13-apa-actions.rdf :
[12:02] <RRSAgent> ACTION: janina to review Decentralized Identifiers
(DIDs) v1.0 https://www.w3.org/TR/did-core/ - due 4 weeks [1]
[12:02] <RRSAgent>   recorded in
https://www.w3.org/2019/11/13-apa-irc#T17-37-11
[12:02] == RRSAgent [rrsagent@public.cloak] has left #apa []
[12:03] <JF> zakim, please part
[12:03] <Zakim> leaving.  As of this point the attendees have been JF,
Matthew_Atkinson, Joanmarie_Diggs, Joshue, Becka11y
[12:03] == Zakim [zakim@public.cloak] has left #apa []


On Tue, Nov 12, 2019 at 9:34 AM Janina Sajka <janina@rednote.net> wrote:

> Colleagues:
>
> Webex info is available at this non-public page:
>         https://www.w3.org/2017/08/telecon-info_apa
>
> Minutes from our last teleconference are available at:
> https://www.w3.org/2019/10/30-apa-minutes.html
>
> See "Resource: APA@TPAC" section below for Fukuoka TPAC minutes.
>
> What:   APA Weekly Teleconference
> When:   Wednesday 13 November
>         12:00 PM        Boston -- U.S. Eastern  Time            (EST: UTC
> -5)
>         Corresponding times in other time zones are:
>
> http://timeanddate.com/worldclock/fixedtime.html?msg=APA+Teleconference&iso=20191113T12&p1=43&ah=1
> Where:  Webex Teleconference Code: 645 857 915
>         https://www.w3.org/2017/08/telecon-info_apa
>         IRC: irc.w3.org Channel: #apa
>         Additional logistics below
>
> ** Preliminary Agenda for APA WG Telecon Wednesday 13 November 2019
>
> agenda+ Agenda Review & Announcements
> agenda+ Task Force Updates
> agenda+ Charter Updates
> https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
> agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html
> agenda+ HTML Review
> http://lists.w3.org/Archives/Public/public-apa/2019Nov/0003.html
> agenda+ Community Groups Tracking Review
> https://www.w3.org/WAI/APA/wiki/Community_Groups
> agenda+ Actions Checkin (Specs)
> https://www.w3.org/WAI/APA/track/products/8
> agenda+ Other Business
> agenda+ be done
>
> Resource: APA & Task Force Teleconference Minutes
> APA Telecon:    https://www.w3.org/2019/10/30-apa-minutes.html
> RQTF:           http://www.w3.org/2019/10/23-rqtf-minutes.html
> COGA TF:        https://www.w3.org/2019/11/07-coga-minutes.html
> p13n:           https://www.w3.org/2019/11/11-personalization-minutes.html
> Pronunciation:  https://www.w3.org/2019/10/30-pronunciation-minutes.html
>
> Resource: APA@TPAC2019 in Fukuoka, Japan; 16-20 September
> Thursday:       http://www.w3.org/2019/09/18-apa-minutes.html
> Friday:         http://www.w3.org/2019/09/20-apa-minutes.html
> ---XR & Immersive Web
>         http://www.w3.org/2019/09/20-apa-minutes.html#item01
>         http://www.w3.org/2019/09/18-apa-minutes.html#item01
>         http://www.w3.org/2019/09/18-apa-minutes.html#item04
> ---WebRTC & Support for RTT
>         http://www.w3.org/2019/09/20-apa-minutes.html#item02
> ---Pronunciation TF
>         http://www.w3.org/2019/09/18-apa-minutes.html#item03
>         http://www.w3.org/2019/09/20-apa-minutes.html#item05
> ---Personalization TF & I18N Issues
>         http://www.w3.org/2019/09/18-apa-minutes.html#item07
> ---FAST Discussion
>         http://www.w3.org/2019/09/18-apa-minutes.html#item06
> ---Joint Meeting with Digital Publishing
>         http://www.w3.org/2019/09/18-apa-minutes.html#item05
> ---CSS A11y Task Force
>         https://www.w3.org/2019/09/15-css-minutes.html#item29
> ---Web Authentication & CAPTCHA Turing Testing (at the bottom of)
>         https://www.w3.org/2019/09/20-webauthn-minutes.html
>
> Resource: CAPTCHA Note (Final)
> http://www.w3.org/TR/turingtest
> Errata CfC:
> http://lists.w3.org/Archives/Public/public-apa-admin/2019Oct/0020.html
>
> Resource: FAST & Horizontal Reviews
> Introductory:   https://www.w3.org/2019/Talks/0516_FAST_MC/ Checklist:
> http://w3c.github.io/pfwg/wtag/checklist.html
> Checklist:      http://w3c.github.io/apa/fast/checklist
>
> Resource: Knowledge Domain
> CG:             https://www.w3.org/community/knowledge-domain/
> APA Issue #9:   https://github.com/w3c/apa/issues/9
> RQTF:
> https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/STEM_Literature_Review
>
> Resource: Pronunciation Task Force
> FPWD Decision:
> http://lists.w3.org/Archives/Public/public-apa/2019Aug/0044.html
> Email:  https://lists.w3.org/Archives/Public/public-pronunciation/
> Wiki:   https://github.com/w3c/pronunciation/wiki
> Issues: https://github.com/w3c/pronunciation/issues
> github: https://github.com/w3c/pronunciation
>
> Resource: Research Questions Task Force (RQTF)
> Wiki:
> https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Main_Page
> Email Archive:  https://lists.w3.org/Archives/Public/public-rqtf/
> Home Page:      https://www.w3.org/WAI/APA/task-forces/research-questions/
> Work Statement:
> https://www.w3.org/WAI/APA/task-forces/research-questions/work-statement
>
> Resource: CSS Accessibility Task Force
> Home Page:      https://www.w3.org/WAI/APA/task-forces/css-a11y/
> Work Statement:
> https://www.w3.org/WAI/APA/task-forces/css-a11y/work-statement
> Issue Tracker:  https://github.com/w3c/css-a11y/issues
>
> Resource: COGA Task Force
> Wiki:           http://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/
> Email Archive:
> http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/
> Timeline:       https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page
> Gap Analysis:   https://www.w3.org/TR/coga-gap-analysis/
> Home Page:      http://www.w3.org/WAI/PF/cognitive-a11y-tf/
> Work Statement: http://www.w3.org/WAI/PF/cognitive-a11y-tf/work-statement
>
> Resource: Personalization Task Force:
> Overview:
> https://github.com/w3c/personalization-semantics/wiki/TPAC2019-WebApps-Symbols-Overview
> Specification:  https://www.w3.org/TR/personalization-semantics-1.0/
> Email Archive:
> http://lists.w3.org/Archives/Public/public-personalization-tf/
> Wiki:           https://github.com/w3c/personalization-semantics/wiki
> Issue Tracker:  https://github.com/w3c/personalization-semantics/issues
> Home Page:      https://www.w3.org/WAI/APA/task-forces/personalization/
> Work Statement:
> https://www.w3.org/WAI/APA/task-forces/personalization/work-statement
>
> Resource: Key APA Pages For Reference
> Your personal tracker: http://www.w3.org/2005/06/tracker/users/my
> APA Tracker (Issues and Actions): http://www.w3.org/WAI/APA/track
> Spec Review History: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review
> CG Review Matrix: https://www.w3.org/WAI/APA/wiki/Community_Groups
> Verticals Matrix: https://www.w3.org/WAI/APA/wiki/Verticals_to_Track
> Home Page: http://www.w3.org/WAI/APA/
> Charter: http://www.w3.org/2015/10/apa-charter.html
> Decision Policy: http://www.w3.org/WAI/APA/decision-policy
> Member List:    https://www.w3.org/2004/01/pp-impl/83907/status
> W3C Process for Busy People:
>         https://github.com/w3c/wg-effectiveness/blob/master/process.md
>
> Resource: Webex & Teleconference Logistics
> Teleconference Data:    https://www.w3.org/2017/08/telecon-info_apa
> Webex Best Practices:
> https://www.w3.org/2006/tools/wiki/WebExBestPractices
>
> *IRC Logistics
> IRC: server: irc.w3.org, channel: #APA
>
> IMPORTANT: Upon joining IRC, please identify yourself:
> present+ [your_name]
> Ex: present+ Janina_Sajka
>
> * Some helpful Scribing and Participation Tips
> http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
>
> For more on the IRC setup and the robots we use for agenda and speaker
> queuing and for posting the log to the web, see:
>
> - For RRSAgent, that captures and posts the log with special attention
>   to action items:
> http://www.w3.org/2002/03/RRSAgent
>
> - For Zakim, the IRC interface to the bridge manager, that will maintain
>   speaker and agenda queues:
> http://www.w3.org/2001/12/zakim-irc-bot
>
> - For a Web gateway to IRC you can use if your network administrators
>   forbid IRC, see:
> http://www.w3.org/2001/01/cgi-irc
>
> - For more on W3C use of IRC see:
> http://www.w3.org/Project/IRC/
>
> --
>
> Janina Sajka
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:       http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures        http://www.w3.org/wai/apa
>
>
>

-- 
*John Foliot* | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com

Received on Wednesday, 13 November 2019 18:05:52 UTC