W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2022

Re: EOWG presents: Personalization -> Adapt

From: Charles LaPierre <charlesl@benetech.org>
Date: Mon, 14 Mar 2022 16:55:13 +0000
To: Janina Sajka <janina@rednote.net>
CC: John Foliot <john@foliot.ca>, Shawn Henry <shawn@w3.org>, public-personalization-tf <public-personalization-tf@w3.org>, "EOWG (E-mail)" <w3c-wai-eo@w3.org>, "w3t-wai@w3.org" <w3t-wai@w3.org>
Message-ID: <A63DB5A8-26DB-4786-A82B-F6CBBF365866@benetech.org>
I see the point, but I myself am not as concerned if it is a verb/noun, its a word which folks can discuss and understand a common point of reference.

I am fine with "WAI-ADAPT" or even "AUI-ADAPT" as our original "AUI" was nixed due to previous use.
If if gets shortened ultimately to ADAPT as I said previously I was happy with that.

Actually "ADAPT" was the code name Benetech chose for an OSEP award which ultimately we didn't receive but stood for "Accessible Digital Adaptable Personalization for Teaching"


Thanks
EOM

Charles LaPierre
Principal, Accessibility Standards, and Technical Lead, Global Certified Accessible
Benetech
Twitter: @CLaPierreA11Y




On Mar 14, 2022, at 8:10 AM, Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>> wrote:

Thanks, John. I also agree there's no particular reason to "chase the
acronym," i.e. find some seemingly coherent wording to justify the term
as an acronym.

I did notice one email from Lionel where the Subject said: "WAI-Adapt."
I would be far more favorable to this kind of construction, or even to a
W3C-Adapt construction, because either of those turns the construct into
a noun, imo.

Best,

Janina

John Foliot writes:
Hi All,

FWIW, I am very much feeling the same way as Janina... I get the idea, but
struggle with the current implementation: *Adapt *is (as Janina notes) a
verb, whereas I believe we want something closer to a noun (or pronoun).

This leads me to return to "Adaptable" or "Adaptation" as the 'name' of our
family of specifications. This would also be closer to how EO then uses the
concept in their example
<https://deploy-preview-8--wai-personalization-standards.netlify.app/personalization/>,
and specifically, "*Examples of Adaptation to Meet User Needs*".

I also personally think that chasing the acronym rabbit down its hole is
not that useful an exercise - I'd rather see and hear something that is
more illustrative to non-experts of what can be achieved, rather than some
random string of letters that users and content creators need to learn
(shades of having to explain *a11y* to non-experts over and over....)

JF

On Mon, Mar 14, 2022 at 7:55 AM Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>> wrote:

Dear All:

After sitting with this proposal for a few days I find myself wanting to
play devil's advocate.

My concern is that the word is a present tense imperative verb. Is that
really the stance we want to take?

ARIA is a noun. I wish we could have a noun rather than an imperative
verb.

I'm not sure that the demand inherent in an imperative is the attitude
we want to take? I would further note that in the U.S. disability
advocacy context, ADAPT is a fairly millitant organization working for
accessible transportation. They've made mainstream news with their
tactics:

https://adapt.org

At the very least I think we should consider these points before moving
forward--not that I'm desiring to be the wet blanket here.

Best,

Janina

Shawn Henry writes:
Dear Personalization Task Force,

After much collaboration, EOWG has a proposal for "branding"
formerly-known-as personalization. It is simply...
     Adapt

A rough example of how "Adapt" could be used is in this draft preview:

https://deploy-preview-8--wai-personalization-standards.netlify.app/personalization/

(Of course, it might not work -- EOWG doesn't know all the ins-and-outs.)

Many other ideas and considerations are in the minutes and comments of
this GitHub Issue:
     https://github.com/w3c/wai-personalization-standards/issues/7

Let us know what you think...

Regards,
~Your Helpful EO Folks

--
<http://www.w3.org/People/Shawn/>

--

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:       http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa




--
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"

--

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa




Received on Monday, 14 March 2022 16:55:33 UTC

This archive was generated by hypermail 2.4.0 : Monday, 14 March 2022 16:55:35 UTC