- From: Matthew Atkinson <matkinson@tpgi.com>
- Date: Mon, 5 Dec 2022 16:52:42 +0000
- To: Sharon D Snider <snidersd@us.ibm.com>, "public-adapt@w3.org" <public-adapt@w3.org>
HI all,
Please find minutes at https://www.w3.org/2022/12/05-adapt-minutes.html and repeated below in text form for convenience.
Best regards,
Matthew
– DRAFT –
Monday 5 Dec 2022 Adapt Task Force Teleconference
05 December 2022
[2]IRC log.
[2] https://www.w3.org/2022/12/05-adapt-irc
Attendees
Present
Becky, CharlesL, janina, Lionel_Wolberger, matatk,
mike_beganyi, Roy
Regrets
-
Chair
Lionel Wolberger
Scribe
matatk, matatk:
Contents
1. [3]Draft CR resolution
2. [4]Adapt Symbols Module Status
3. [5]Readiness of Explainers
4. [6]BCI Registry Specification
5. [7]Due Diligence regarding our attributes vs existing
alternatives (CSS Media Queries, @autocomplete,
microformats, DPub, etc.)
6. [8]BCI Registry Specification
7. [9]Due Diligence regarding our attributes vs existing
alternatives (CSS Media Queries, @autocomplete,
microformats, DPub, etc.)
8. [10]Summary of resolutions
Meeting minutes
Draft CR resolution
DRAFT RESOLUTION: Subject to the CfC for the AAC Registry's
First Public Working Draft (FPWD) being successful, the
WAI-Adapt TF will request a transition to Candidate
Recommendation (CR) for the Symbols Module 1.0 specification.
<CharlesL> +1
+1
<janina> +1
<Roy> +1
<Becky> +1
<Lionel_Wolberger> +1
<mike_beganyi> +1
RESOLUTION: Subject to the CfC for the AAC Registry's First
Public Working Draft (FPWD) being successful, the WAI-Adapt TF
will request a transition to Candidate Recommendation (CR) for
the Symbols Module 1.0 specification.
matatk: Well done everyone! Special ACK to Lisa.
Lionel_Wolberger: We'll let Lisa know we're making this
request.
Adapt Symbols Module Status
[11]https://w3c.github.io/adapt/symbols/
[11] https://w3c.github.io/adapt/symbols/
Lionel_Wolberger: Looks like we're done! Does anyone have any
thoughts about needed work?
janina: We don't need to go back to the TAG; I sent an email
(CC'd to the list) and we got a response from management to
agree with the email, requesting we add this info to the GitHub
threads, which Roy did. So we take this as implicit permission
to move forwrad.
Lionel_Wolberger: Do we need to explicitly confirm with TAG?
janina: When we make the transition request, management will
see this.
Readiness of Explainers
matatk: I have to make the tweak to the example needed, raised
by Becky. Didn't do it yet, due to CR and other prep, but will
be on it shortly.
<Lionel_Wolberger> [12]https://www.w3.org/TR/adapt/
[12] https://www.w3.org/TR/adapt/
Lionel_Wolberger: Is there also a TAG explainer we need to
chase?
janina: We don't need to chase the TAG explainer.
Lionel_Wolberger: This hints at work to come, covers Adapt as a
whole.
janina: There are some sections that are not yet done, but are
placeholders. We'll get to them.
Lionel_Wolberger: It talks about modules, and each one having
use cases.
matatk: The Editor's Draft is updated to refer to the Symbols
Module as opposed to content module.
[13]https://w3c.github.io/adapt/
[13] https://w3c.github.io/adapt/
Lionel_Wolberger: There's not a link to Bliss from the
Explainer.
Lionel_Wolberger: Think we should reference Bliss/the registry
in the Explainer.
janina: The magic comes from the Registry being used by/in
conjuction with other specs.
Lionel_Wolberger: No actions on the Explainer? We need you all
to read it!
janina: We're going to continue to publish updated WDs.
Lionel_Wolberger: Can we have volunteers to read it this week?
BCI Registry Specification
Lionel_Wolberger: We just met with Bliss. I was on the call
too. We're good to go from Bliss' perpective on the FPWD. [We
await the close of the formal APA CfC.]
… We discussed what'll happen after the Registry is published,
future work.
[14]https://w3c.github.io/aac-registry/
[14] https://w3c.github.io/aac-registry/
Due Diligence regarding our attributes vs existing alternatives (CSS
Media Queries, @autocomplete, microformats, DPub, etc.)
<Roy> [15]https://raw.githack.com/w3c/aac-registry/main/
snapshot.html
[15] https://raw.githack.com/w3c/aac-registry/main/snapshot.html
BCI Registry Specification
CharlesL: Last time I mentioned the symbols are too small;
looks better now. Please increase the size even more if
possible.
Roy: I tweaked the CSS; could look into it further.
Roy: Some of the SVGs are different sizes.
Roy: We get the symbols from BCI; can make CSS tweaks but can't
adjust them extensively.
CharlesL: Suggest bringing this up with BCI.
Roy: ACK; will ask Bliss.
matatk: I was looking into styling for prefers-color-scheme
too. May be able to process the SVGs; we'll discuss with BCI as
Roy mentioned.
CharlesL: Under Acknowledgements, it would be remiss to not
have Lisa included here.
Lionel_Wolberger: +1
matatk: +1
janina: +1
<Becky> +1
Roy: I'll fix that.
<mike_beganyi> +1
janina: I'd like to be specific about who worked on the
documents exactly. We must ensure that Lisa is acknowledged in
the Symbols Module.
<Roy> [16]https://w3c.github.io/adapt/symbols/#ack_group
[16] https://w3c.github.io/adapt/symbols/#ack_group
CharlesL: ACK janina's point. I don't think we could've gotten
here without Lisa bringing Bliss to the table.
Lionel_Wolberger: Lisa has been heavily involved with the AAC
agenda; not directly with the Registry. So let's make sure Lisa
is ACK'd on the Explainer and Module.
Due Diligence regarding our attributes vs existing alternatives (CSS
Media Queries, @autocomplete, microformats, DPub, etc.)
Lionel_Wolberger: We've had a lot of debates on this; not sure
where to start. Specific technical details on specific
attributes, all the way up to philosophical issues on broad
approaches.
Lionel_Wolberger: Floor is open
CharlesL: Specifically on @autocomplete. This was brought up
many times. Some confusion over whether the functionality
that's already there is enough. The problem is @autocomplete is
only for form fields. We want to be able to put it on any
element.
CharlesL: So we can't just use @autocomplete. We may share the
same values, but can't use the attr.
Lionel_Wolberger: E.g. a footer might have an address in it.
You think Adapt may want to mark that up with this attribute?
CharlesL: Yes; address (home/work) symbol could show up above
the address.
matatk: We could just wask WHATWG about allowing @autocomplete
in more places? That may require us to align completely on attr
values(?), and in this attr's case, may complicate parsing
rules too much, but worth asking?
<Lionel_Wolberger> Lionel says to Becky, your headset is
cutting in and out
Becky: What exactly would @autocomplete mean if not applied to
a form field? To me that's not about input, but just adding
more info. A different attr would be more apt.
<Lionel_Wolberger> Sample: <label> Address: <textarea name=ba
autocomplete="section-blue shipping street-address"></textarea>
</label>
<Lionel_Wolberger> Sample: autocomplete="section-blue shipping
address-level2"
CharlesL: @autocomplete I agree is a red herring, but it has a
number of values that it uses to indicate common purposes.
Those values are what we want to replicate, but we didn't want
to duplicate things (or duplicate them, with new value names).
Becky: But how are we completing something if it's not a field?
CharlesL: Agree the name autocomplete doesn't make full sense
here, but if these are all the same values, there is something
in common there.
Becky: Why would we put any of these _values_ on a <div>
(e.g.)?
CharlesL: We want to be able to convey the same "purpose"
semantics as @autocomplete uses. E.g. the address in the footer
is your street address. We don't necessarily want to call it
"autocomplete" but we don't want to independently duplicate the
values.
Becky: So we're not saying we should call it "autocomplete"?
matatk: The name isn't quite right (not even for what it's
being used for now); I _was_ actually suggesting we consider
asking to make the attr more widely appilcable to avoid
duplication. Maybe we just link to the WHATWG spec for our
adapt-purpose values though?
Becky: One confusing thing about this is that "autocomplete"
implies the info is being filled in from somewhere. Wouldn't
this cause confusion if, for example
… the address in the footer _didn't_ match the stored address
for the user?
matatk: Agree that could be confusing.
Lionel_Wolberger: "autocomplete" has multiple different
mantles; an anchor one, and an autofill expectation one.
… We're talking about extending that to other elements.
Lionel_Wolberger: Thanks for the discussion; have to wrap now.
Summary of resolutions
1. [17]Subject to the CfC for the AAC Registry's First Public
Working Draft (FPWD) being successful, the WAI-Adapt TF
will request a transition to Candidate Recommendation (CR)
for the Symbols Module 1.0 specification.
Minutes manually created (not a transcript), formatted by
[18]scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).
[18] 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 03/12/2022, 14:19, "Sharon D Snider" <snidersd@us.ibm.com> wrote:
CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.
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
* Draft CR resolution
* Adapt Symbols Module Status
* Readiness of Explainers
* BCI Registry Specification
* Due Diligence regarding our attributes vs existing alternatives (CSS Media Queries, @autocomplete, microformats, DPub, etc.)
* Recruiting
* Review open issues
* Symbol Module Implementations Status, focus on new candidates
* Test to show rendering symbols do not 'break' existing pages
The teleconference information is at: call info - adapt <https://www.w3.org/2017/08/telecon-info_adapt>
Time:
* 10:00 a.m. Eastern
* 05:00 p.m. IS
* 03:00 p.m. UK
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://lists.w3.org/Archives/Public/public-adapt/>
* 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, 5 December 2022 16:52:57 UTC