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

Re: EOWG presents: Personalization -> Adapt

From: John Foliot <john@foliot.ca>
Date: Mon, 14 Mar 2022 11:27:04 -0400
Message-ID: <CAFmg2sVMrqOjCKDE2sqHTa=i+yxLw348BpohDYgDbg8S03D-Dw@mail.gmail.com>
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>
Hi Janina,

> WAI-Adapt

I'll note that we actually took that naming convention with ARIA when it
was released, by referencing it as WAI-ARIA
<https://www.w3.org/TR/wai-aria-1.1/> in the normative Recommendation, and
yet interestingly most folks drop the WAI part when referencing ARIA today.
So I think that would very quickly bring us back to Adapt as the 'common'
term. Is that what we want?

JF

On Mon, Mar 14, 2022 at 11:10 AM Janina Sajka <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> 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
>
>

-- 
*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"
Received on Monday, 14 March 2022 15:27:42 UTC

This archive was generated by hypermail 2.4.0 : Monday, 14 March 2022 15:27:43 UTC