Re: EOWG presents: Personalization -> Adapt

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"