- From: Matthew Atkinson <matkinson@tpgi.com>
- Date: Mon, 15 Aug 2022 15:33:29 +0000
- To: Lionel Wolberger <lionel@userway.org>, "public-adapt@w3.org" <public-adapt@w3.org>
- CC: Sharon D Snider <snidersd@us.ibm.com>, APA Chairs <group-apa-chairs@w3.org>
Hi all,
Please find today's minutes at https://www.w3.org/2022/08/15-adapt-minutes.html and below in text form for convenience.
Best regards,
Matthew
– DRAFT –
WAI Adapt Task Force Teleconference
15 August 2022
[2]IRC log.
[2] https://www.w3.org/2022/08/15-adapt-irc
Attendees
Present
becky, CharlesL, janina, JF, Lionel_Wolberger,
Matthew_Atkinson, MichaelC, mike_beganyi, Roy, Sharon_
Regrets
-
Chair
-
Scribe
Lionel_Wolberger, Matthew_Atkinson
Contents
1. [3]Plans for Sept.
2. [4]TPAC 12-16 September 2022 preparations
3. [5]CfC for Content Module 1.0 CR Status
1. [6]Exit criteria
2. [7]TAG response resolution
3. [8]BCI
4. [9]BCI Registry Implementation
Meeting minutes
<Github> [10]https://github.com/w3c/adapt/issues/203 : Unclear
how the Bliss symbol examples should work with i10n/i18n.
[10] https://github.com/w3c/adapt/issues/203
Plans for Sept.
Lionel_Wolberger: There's a run of Mondays in September where
we won't be meeting for various reasons.
Lionel_Wolberger: Labor Day (5th); TPAC (12th); rest week
following TPAC (19th).
<CharlesL> I will be at TPAC in person.
Lionel_Wolberger: *asks for objections; none received*
Lionel_Wolberger: Thus we agree to not meet those three weeks.
Lionel_Wolberger: There will be a lot of Adapt activity at
TPAC.
TPAC 12-16 September 2022 preparations
Lionel_Wolberger: TPAC is Technical Plenary and Advisory
Committee meetings. Excellent place to move work forward.
Lionel_Wolberger: Look at the APA schedule; APA has a lot of
meetings; Adapt is covered in many of these.
[11]https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022
[11] https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022
Lionel_Wolberger: It'd be helpful to have a run down of what
Adapt expects at TPAC. We have work with CSS, Verifiable
Credentials. Also interest in i18n.
janina: Also the TAG... we received an invite and are following
up with them.
janina: There are some issues they raised with respect to
transitioning to CR, and Sharon did a lot of useful research to
allow us to check on how we responded to those.
… Also looking at building the registry. (Following up with
MichaelC and Russell regarding the nature of the spreadsheet
that can be used as the basis.)
janina: TAG is important for all the work we're doing—registry
too, as it's a new vehicle.
JF: TAG = Technical Architecture Group
CharlesL: With the Registry, should we reach out to Ralph, who
is the technical person behind the website, in addition to TAG?
MichaelC: We'd loop Ralph in on the transition request to
publish it. There are other technical people who're on the
front line too.
Lionel_Wolberger: There will also be joint meetings with APA
and COGA; what's Adapt's role there?
janina: We're not yet fully aware of COGA's agenda, though
there is a 3-way meeting with AGWG and COGA first thing on
Monday. This will cover Functional Needs, as COGA wanted to
discuss this.
janina: I asked for other agenda from COGA.
MichaelC: We may not have COGA facilitators present; we are
following up about whether this can go ahead on the APA
planning call.
janina: I'll speak with COGA tomorrow.
Lionel_Wolberger: Doesn't seem that Adapt is key to the
currently-planned joint meeting.
janina: Yes (whilst it could be part of the solution, it's not
fundamental to that agenda).
Lionel_Wolberger: Other meetings?
janina: We (chairs) are following up, re TAG.
Lionel_Wolberger: I'll be there locally. Will we have remote
participation?
janina: I expect all meetings will have remote participation as
an option.
Lionel_Wolberger: Will propose a breakout, and update the
slides.
Matthew_Atkinson: The other part is a
probably-less-than-one-minute pitch about Adapt, which we can
all learn, and impart to people as-and-when the opportunity
arises.
MichaelC: Not sure about the breakout schedule/proposition as
of yet.
<janina> [12]https://www.w3.org/2022/09/TPAC/Overview.html
[12] https://www.w3.org/2022/09/TPAC/Overview.html
Lionel_Wolberger: Shall we wear buttons (we did back in
Verifiable Credentials)? What about a one-page document that we
could provide to interested people?
janina: Yes to the document (no to buttons)—could use the
abstract we already have. Printing it out and putting a QR code
to the wiki page/the spec.
janina: If people want to set these things up, I'm sure the
group would be happy for it to happen.
Lionel_Wolberger: I can print these out for the breakout
session.
Lionel_Wolberger: Do we want to talk about CSS about Adapt and
Media Queries?
janina: Yes; it's scheduled (on the wiki).
Lionel_Wolberger: Do we want to address the concern about the
burden of authoring?
janina: I think our energies are better placed in getting the
specs advanced at this point.
janina: We need the Registry to be at FPWD in order to be able
to get Content to second CR.
Matthew_Atkinson: I see the concerns about authoring burden.
Especially with the registry in conjunction with authoring
tools, there are several ways the tools could help authors add
concepts to their content. We should keep this in mind, and
build on the specs later.
… It's important to keep the behavior predictable at run-time
(but there's lots we can do at authoring time to raise
awareness).
JF: We met at TPAC in Burlingame (2017) and there were some
WYSIWYG authoring tool people there; we could approach them
with ideas about this.
<JF> Web Editing Working Group: [13]https://www.w3.org/2021/06/
web-editing-wg-charter.html
[13] https://www.w3.org/2021/06/web-editing-wg-charter.html
Lionel_Wolberger: Should we touch base with ATAG? [Group
indicated maybe, but just right now the focus is on WCAG
2.2-related work.]
Lionel_Wolberger: Anything with i18n?
janina: We've resolved our issue with them; we have other
issues to discuss with them regarding other work.
Lionel_Wolberger: How about COGA?
janina: We need agenda.
Lionel_Wolberger: let Sharon and I work on this in planning.
Sharon_: +1
CfC for Content Module 1.0 CR Status
Exit criteria
Lionel_Wolberger: This was assigned to me and Matthew_Atkinson
and we've been working on it.
Matthew_Atkinson: We have listed 205 possible attribute/value
pairs
… we will need at least two independent implementations
… Matthew_Atkinson is preparing a test page that will offer all
attribute/values to any potential test
… the exit criteria need some more work
Lionel_Wolberger: The exit criteria will express how tests will
be logged, so we can see when we have achieved our exit
critera.
Link to the exit criteria google doc, [14]https://
docs.google.com/document/d/
1bNEUCqE7SxwkhmENIO620yVTjeAnhn_5Bi4AY8oQJEA/edit#
[14] https://docs.google.com/document/d/1bNEUCqE7SxwkhmENIO620yVTjeAnhn_5Bi4AY8oQJEA/edit
Lionel_Wolberger: When finalized, where should we publish the
exit criteria?
MichaelC: Typically we publish it as an appendix on the spec
itself.
TAG response resolution
Sharon_: I did the research: [15]https://lists.w3.org/Archives/
Public/public-adapt/2022Jul/0011.html
[15] https://lists.w3.org/Archives/Public/public-adapt/2022Jul/0011.html
janina: We covered this earlier; we're as ready as we can be
for the TAG meeting.
BCI
janina: We're waiting to hear back from Russell; I touched base
with MichaelC on the follow-up just before this call.
<Github> [16]https://github.com/w3c/adapt/issues/203 : Unclear
how the Bliss symbol examples should work with i10n/i18n.
[16] https://github.com/w3c/adapt/issues/203
BCI Registry Implementation
MichaelC: I'll propose a draft document that will define the
registry and its structure.
Lionel_Wolberger: We have a CSV file now.
MichaelC: Yes; the registry doc will provide required
explanation around this, of the aims, structure, relevant
policies.
MichaelC: Can't promise a draft before TPAC (though working on
it). We should have something high-level before then.
Lionel_Wolberger: *Runs through outline*
MichaelC: If you're happy to draft the outline, go ahead. I
should probably draft the structure-related parts.
MichaelC: The most important part for us is to describe the
meaning of the data.
Minutes manually created (not a transcript), formatted by
[17]scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).
[17] https://w3c.github.io/scribe2/scribedoc.html
--
Matthew Tylee Atkinson (he/him)
--
Principal Accessibility Engineer
TPG Interactive
https://www.tpgi.com
A Vispero Company
https://www.vispero.com
--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
On 15/08/2022, 14:48, "Lionel Wolberger" <lionel@userway.org> wrote:
CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.
Hi all,
Please find below the agenda for Monday's WAI-Adapt TF call and let us know if there are any other topics that need to be added:
Chair: Lionel
* agenda+ Plans for Sept. (Note: 3 weeks without Adapt TF meetings - Labor Day, week of TPAC and week after TPAC)
* agenda+ TPAC 12-16 September 2022 preparations
* agenda+ CfC for Content Module 1.0 CR Status, Issues raised by the W3C Director upon their review [1] Exit criteria, [2] TAG Response Resolution [3] BCI
* agenda+ BCI Registry Implementation
* agenda+ Respond to issue #203 (Janina)
* agenda+ Discuss @rel vs. purpose/destination/action -- add to the explainer
* agenda+ Content Module Implementations Status, focus on new candidates
The teleconference information is at: call info - adapt <https://www.w3.org/2017/08/telecon-info_adapt>
Time:
· 10 am Eastern time
· 5 pm IS
· 3 pm UK time
IRC access
An IRC (Internet Relay Chat) channel will be available during the call at: https://irc.w3.org/?channels= <http://irc.w3.org/?channels=adapt>adapt
The server is irc.w3.org <https://irc.w3.org/>
The port number is 6665
The channel is #adapt.
You can write any name as a nickname
Resources and useful links
· Wiki <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49Ldrp2nQ-x1W30mhG94fDYzLW1GBcSW3F6jV_W45NqmX43TBFHW3T6jkg3T1McJf4mCW9mV3&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>; - this page has links to all our work
· mailing list archives <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj26QkH8W3T3qGX1JHM74W43Wg2w2p76z4W3T4FNJ1Lm8YzW3ZWTXk45W2z0W3SYFSb3K8R4LW41PFYp4ttcHyw43Tw4j48K2&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>
· Web-Based Surveys (WBS) <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49LdqK1N4hm1W1N81nQ3Cfv3hw1N4K5047V2&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>;
· adapt source repository issue tracker <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW3P28X24hCPvhW43T4Pc1Vp7RpW3H3bfK1LyzF74W1vp1&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>.
· Scribing and Participation Tips: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
· Demo: https://github.com/ayelet-seeman/coga.personalisation and https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.htm <https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html>
<https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4hLZp04myBBCf43Wg2w04&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>Lionel Wolberger
COO, UserWay Inc.
<https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4hLZp04myBBCf43Wg2w04&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>
+1 (415) 800-4557 <tel:+14158004557>
lionel@userway.org
<https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj26QkHkW4cJ2Vy3zkrlhW49LdrX1LzQ9y4S68T1&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>
Important Reads: Accessibility and SEO Impact <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4hLZp04myBBCW43Wg2w3CbHnhW1LF6VG1GCt5gW3z8p1343Q9gXW3F5sLD4cKJmZW3ZWWrh1GF-0yf4cJ2B_04&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f> & Accessibility Tax Credits <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4hLZp04myBBCW43Wg2w3CbHnhW1LF6VG1GCt5gW3z8p1343Q9gXW3F5sLD4cKJmZW3ZWWrh1GF-0yf4cJ2B_04&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>
On Fri, Aug 5, 2022 at 11:38 PM Sharon D Snider <snidersd@us.ibm.com> wrote:
Hi all,
Please review the agenda for Monday's WAI-Adapt TF call and let us know if there are any other topics that need to be added:
Chair: Sharon
* agenda+ CfC for Content Module 1.0 CR Status, Issues raised by the W3C Director upon their review
* [1] Exit criteria & Conformance in Content Module (Lionel & Matt)
* [2] TAG Response Resolution
* [3] agenda+ BCI & Registry Implementation (https://www.w3.org/2021/Process-20211102/#registries)
* agenda+ Respond to issue #203 (Janina)
* agenda+ TPAC 12-16 September 2022 preparations
* agenda+ Discuss @rel vs. purpose/destination/action -- add to the explainer
* agenda+ Content Module Implementations Status, focus on new candidates
The teleconference information is at: call info - adapt <https://www.w3.org/2017/08/telecon-info_adapt>
Time:
· 10 am Eastern time
· 5 pm IS
· 3 pm UK time
IRC access
An IRC (Internet Relay Chat) channel will be available during the call at: https://irc.w3.org/?channels= <http://irc.w3.org/?channels=adapt>adapt
The server is irc.w3.org <https://irc.w3.org/>
The port number is 6665
The channel is #adapt.
You can write any name as a nickname
Resources and useful links
· Wiki <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49Ldrp2nQ-x1W30mhG94fDYzLW1GBcSW3F6jV_W45NqmX43TBFHW3T6jkg3T1McJf4mCW9mV3&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>; - this page has links to all our work
· mailing list archives <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj26QkH8W3T3qGX1JHM74W43Wg2w2p76z4W3T4FNJ1Lm8YzW3ZWTXk45W2z0W3SYFSb3K8R4LW41PFYp4ttcHyw43Tw4j48K2&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>
· Web-Based Surveys (WBS) <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW4mKLS-4mbkbhW49LdqK1N4hm1W1N81nQ3Cfv3hw1N4K5047V2&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>;
· adapt source repository issue tracker <https://t.sidekickopen90.com/s3t/c/5/f18dQhb0S7kF8cFFTBW4T_qld2zGCwVN8Jbw_8QsRtKVn1vXj1p1kknW16gGBN41Jd6G101?te=W3R5hFj4cm2zwW3P28X24hCPvhW43T4Pc1Vp7RpW3H3bfK1LyzF74W1vp1&si=8000000004174048&pi=8e540703-aba8-4282-85a0-c6cb1d664a5f>.
· Scribing and Participation Tips: http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
· Demo: https://github.com/ayelet-seeman/coga.personalisation and https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.htm <https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html>
Regards,
Sharon Snider
IBM Design ► IBM Accessibility Team
(512)965-3957
www.ibm.com/able <https://www.ibm.com/able> and w3.ibm.com/able <https://w3.ibm.com/able>
Received on Monday, 15 August 2022 15:33:47 UTC