Personalization -> WAI-Adapt specifications ?

[shawna-slh]

[updated 6 April]
Proposal under consideration is:

"WAI-Adapt specifications"

• WAI-Adapt: Content Module
• WAI-Adapt: Help and Support Module
• WAI-Adapt: Tools Module
• ... etc.

Please at least skim:

• Adapt Specifications Overview | Adapt Overview - rough example of Adapt specifications in use
• issue 7 with context, links to minutes, previous ideas
• e-mail thread starting 12 March with different perspectives

[iadawn]

+1

[daniel-montalvo]

+1

[becka11y]

Since branding personalization work, #7 , is closed, I am commenting here. Some members of personalization had concerns with Adapt. Another suggestion has been put forward, APT – Adaptable Personalisation Techniques. Is this something that can be considered?

[KimPatch]

Just heard about this – here are a couple of thoughts.

• One difference between personalization and adapt is it's obvious that you're personalizing for a person, but with adapt it's not clear if the person or the technology is adapting. This might be confusing to folks.
• Personalization is a description, and so is the phrase associated with APT – Adaptable Personalisation Technique, while adapt is an imperative, which makes for a more difficult label.
• It's also tough to use a single word that's not a description because you might employ that word when you're talking about the thing itself. I'm picturing it getting confusing in a "Who's on First" sort of way trying to explain "adapt" the standard without using adapt the word. For instance, the phrase "adapt the standard" becomes ambiguous…

[shawna-slh]

Hi @KimPatch "Personalization" didn't work. Janina and others explain why in some of the minutes or comment available from #7

I think if we go with "WAI-Adapt", it makes sense for people to use the word adapt when talking about it. Below are more options...

[shawna-slh]

6 April 2022 WAI Coordination Call minutes

Agreement on:

• "WAI-Adapt" or "WAI-ADAPT"

Open:

• ? capitalization— "WAI-Adapt" or "WAI-ADAPT"
• ? short phrase — "Adaptable Personalisation Techniques" and "Adaptable Personalizable Technologies" is complex

[shawna-slh]

"WAI-Adapt" lowercase seemed the stronger case. I updated draft WAI-Adapt Overview to see how that might work in context.*

• Draft first sentence of the Introduction:

  WAI-Adapt specifications enable users to personalize how content is presented in order to meet their needs and preferences.

• Summary has a little more info in short simple sentencs, including "why Adapt".

I don't think we want "Adaptable Personalizable Techniques|Technologies". It's complex, hard to say, and not very explanatory. I think we can convey the point more simply. Some ideas are in the draft:

• Enabling users to adapt content
• Enabling users to adapt content presentation
• Enabling users to change content presentation
• Enabling users to personalize content presentation

I wonder about the issues with "change", "adapt", "personalize" for the simple description for the lay-person (a person without professional or specialized knowledge in a particular subject)?

*Note: Anyone can do a pull request on draft edit or current page to get a Netlify preview to see how different options would work in context

[KimPatch]

I understand that the goal is for an alternative to personalization – my comment was that I think
WAI APT – Adaptable Personalization Techniques
works better than
WAI Adapt
because it avoids the Who's responsible, Imperative, and Who's-on-first issues (details above). I guess that was buried in my longer explanation.