Brent: We'll start by reading the updates to the discussions that have been ongoing for the last few days https://github.com/w3c/wai-personalization-standards/issues/7#issuecomment-1046058557
<Lionel_Wolberger> present?
<shawn> refresh https://www.w3.org/2017/08/01-eowg-info.html
Brent: The name we will provide will be the overall name of the series and there will sub sections of this. My question is if it will it become the attribute name within the code as well?
KrisAnne: That was my understanding yes
Lionel: I thought we determined that was NOT true.
Shawn: Janina led me to believe that it was still open, we may end up using this in HTML, if possible. I see no reason not to do it if it is possible.
<shawn> TITLE prefix and HTML prefix
Lionel: It is not actually an
attribute but a tag. We need to distingusih between the
popularly used prefix and an HTML tag or attribute.
... I would like to remind us that as Shawn said, whatever we
come with as the prefix has to live comfortably with the
various modules. I took that into consideration as I thought
about the naming. We have tried to think about the semantics
content module as we name this, since that is the only one up for CR.
<shawn> Prefix: Semantics Content Module
<shawn> Prefix: Help and Support Module
<shawn> Prefix: Tools Module
Brent: The purpose of our conversation today is to develop a couple or few names and their rationale to send along as recommendations to the TF.
Kevin: I reacted strongly against anything where we require a long explanation of why we chose that word. My view is to step back and avoid those where there is too much to explain why it was chosen.
Laura: I agree with Kevin and for that reason don't really like ADAPTATION either
Howard: I like personalized design, it is the closest to what it is. While I like ARROW you need too much contortion to make sense of it - the words within the acronym don't really relate.
Shawn: My understanding is that this is adapting the content itself, not the design. And for Laura, why is the word adaptation not working for you?
Laura: As a developer it is vague.
Shawn: What about the words 'customizable' or 'individual'
<kevin> -1 to customisable
<shawn> adaptable -- personal -- individual
Lionel: What about 'experience'
<kevin> Quite liked "Enabling content" as a phrase
Lionel: Let's look at the experience for a minute. (shares his screen)The purpose is to simplify content, the user agent will be able to filter and embelish the content with symbols or varied presentation of content that is individualized by user preferences.
Brent: I think the power of you talking about this was listening as you tried to use the terms when explaining that users can simplify the content. The word segue seems to make sense in that context. It is more difficult to understand when you use the markup term than to use the example of the user.
<shawn> [ Shawn also notes Jade's point the people will likely use acronyms sometimes even if only 2 words ]
Lionel: It is interesting that
ARIA is a word used all the time and people use it in
referencing the code and don't necessarily think about what it
means.
... distraction is one of the conditions that we consdiered
early on. We needed to use adaptable HTML to avoid distracting
- that is for Module 1. Modules 2 and 3 are more difficult but
will help and support, providing more options.
Kevin: I would not be saying AHA, sounds silly, every time I hear these long phrases I think it must be shortened. ARIA is widely used because it trips easily off the tongue. I can't come up with it yet but thinking that 'users adapt an interface' is what this is about but the letter 'u' is a bear to come with an acroymn.
KrisAnne: I agree
Lionel: But sometimes U works - look at USA
SHawn: UEC
KrisAnne: UAC
Kevin: Customizing, adapting, enabling, all say about the same. Maybe attributes could be in there
<eoncins> Could stand E if stands for "easy" instead of "enabling"
Lionel: Clarity is a word that occurs to me as that is a goal. There is beauty to the simplification
Kevin: I agree with the direction of that - wondering about the implementation that is a bit removed from the experience.
KrisAnne: I am asked about ARIA and often reply that it does not matter what the acronym is, I don't expand it for my developers. It doesn't even explain itself or define what it does when you DO expand it.
Howard: But please remember that when it first was published it DID lead you in the direction of what it was doing.
<Laura> Personal Simplified Interface
Shawn: Pulling it all together what if we try to come up with a word that does both - a word in itself and then when expanded, make that a good explanation of what it actually does.
Sharron: +1
Lionel: If we find a word we like like segue or clarity we could do some gymnastics to make it work.
Howard: I was going to argue against that, but Lionel's rationale makes sense.
<shawn> CLARA - Content Language Rich Adapation
Kevin: I am not really in favor of that approach. CAPTCHA for example is a horrible acronym because of the verbal contortion needed. Adapt is the word I would think is essential and would be a word to shoot for but it has 2 of the letter 'a'.
<Lionel_Wolberger> Content Language Adaptation Rich Applications
Lionel: Content language adaptive
rich applications
... CLARA
<kevin> CARA: Content adaptive rich applications?
Howard: The thing about adaptive is something that the user does. It seems we now have two schools of thought - one is the short phrase, the other an acronym. I kind of like something with personalized.
Shawn: There is a p in ADAPT and seems to be perfectly suited to be self explaining and as noted, people often forget the elements of the acronym anyway.
<dmontalvo> Adapt: Accessible Definition of Adaptable and Personalized Technology
<kevin> ADAPT: Adaptive Digital Attributes for Personalised T(something)
<Lionel_Wolberger> Lionel also tries ADAPT: Adaptive Data Aiding Personalizable Technology
<Lionel_Wolberger> Lionel tries SEGUE: Semantic Extensions Guiding User Experience
Laura: I may be getting hung up on the personalization. As the developer will I be building alternative content such as when people used to turn off their style sheets?
Shawn: You don't need to do more designs but put code (like ARIA) that will enable that personalization.
Laura: But in that context, the word personalized might be misleading.
<Lionel_Wolberger> +1 to Individual
Shawn: The tie in to personalization is that the user chooses
Laura: So a certain attribute will trigger my own presentation preferences?
Lionel: Reaching out to more people - use the 'reach out' spec, perhaps
<Sylvie> suggest having enabling in the word and to propose Enabling Content Adaptation For User' Needs, ECAFUN
<Lionel_Wolberger> Lionel adds the ideas of reach out, include more people, expand our reach to the mix
Sylvie: I like the term and found a word that has FUN in it, have put it in the IRC
Brent: We are at time, suggest we move along to next topics and let this percolate a bit.
Kevin: Before we move on, is it worth spending the
time to at least agree on principles - do we want one word? an acronym? a meaningful
set of words? what is the priority? Can we at least define the route we
want to go?
... for example say we like to find acronyms for ADAPT,
Shawn: Good idea to do that but before we say OK let's agree on a word that fits by itself and is actually an acroymn for something that we are actually defining...INDIVIDUAL, etc?
<kevin> [ADAPT works for me if we can get the acronym to work]
Brent: I agree with that in principle if we can make it work. I strongly am leaning away from the short phrase because they just did not work and people will shorten them anyway.
<kevin> WAI-ADAPT
<eoncins> +1 to ADAPT that works as a word. ARIA is a term that belongs to opera but people have come to understand it.
<shawn> CLEAR
Kevin: Does it need to be an acronym? We can just call it adapt with no further need for expansion. it is self expanatory enough on its own.
Shawn: mic drop!
<Laura> +1 to Kevin's comments and "adapt"
<krisanne> +1
<MarkPalmer> +1 to WAI-ADAPT
<Howard> -1
<eoncins> +1
Kevin: skip that part of expanding into a series of words, and call it the adapt spec - period.
<shawn> Adapt: Semantics Content Module
<shawn> Adapt: Help and Support Module
<shawn> Adapt: Tools Module
Howard: I think people will want to know what it means, should have some explanation of what it means
Shawn: It is the title of a concept, not an acronym.
Howard: My own view is that it must mean something
<shawn> Adapt specifications, it means what it says.
<eoncins> ADAPT can also be considered an abbreviation.
<shawn> and HTML prefix (like aria-) could be adapt-
<kevin> +1
Howard: I think when something is newly introduced, it needs more explanation.
<CarlosD> +1 to WAI-Adapt
<Lionel_Wolberger> +1 to ADAPT, it's looking good
<Brent> +1 to "Adapt" (not all caps)
<Sylvie> Would have preferred an acronym but don't find one for ADAPT, but as the word speaks for itself, +1 for ADAPT.
Sharron: It should be written in sentence case to be sure the acronym is not expected or anticipated. I understand and agree with Howard's reminder that new tech terms need explanation but feel that we can explain it without turning it into an acronyms
Kris Anne: I agree
Daniel: I agree
Michelle: I agree
<shawn> I'm looking at revising the [Personalization Overview](https://www.w3.org/WAI/personalization/
<shawn> "The Adapt specifications enable tailoring the user experience to meet the needs and preferences of the individual user."
Estella: I think it as more of an abbreviation for something like Adaptable Personal Interface with Adapt being the abbreviation.
Shawn: If you look at the personalization page , the naming it fits quite well.
<scribe> Scribe: Laura
Brent:Next we want to consider a new page about our current work. We need to come up with a good title so we can push it out at CSUN next week
<Brent> https://github.com/w3c/wai-about-wai/issues/127
<shawn> latest nearly final fisrt iteration of the page: https://deploy-preview-126--wai-about-wai.netlify.app/about/new-work/
<shawn> tries out "Advancing Accessibility at W3C WAI -- March 2020 Activities and Upcoming Publications"
Brent: With this option, the thing that caught my attention most was "what are we working on"
...what is happening right now, the section will be updated. Advancing Accessibility could be an article.
<kevin> +1 to Brent's comment on it just being an article
<dmontalvo> shawn: +1 to Brent.
Carlos:what works better is action and implies constant changes. objectives and summary - attract more people. I support Kevin's suggestion to get involved at W3C. We're trying to bring other "new" people in
Shawn: But it is not the ONLY objective to bring people in. Other purpose doesn't seem to come through in the requirements
Brent: my worry about get involved is that I want to know what WAI is working on so I can bring what's new to my company. Get involved may not be enough to get people to come to the page.
Kevin: I wonder about - what we're working on. Does the context of the page being within the WAI site, can we just have it "What we're working on"
Daniel: WAI would be in the title
Kevin: can we drop a lot of the redundant wording because of the page context?
Brent: ways to join are there as well
Laura: I do like "What we are working on" I don't think we need don't need WAI W3C in the h1
Michelle: not everyone knows what WAI is. If this is for people who may not know what WAI or accessibility is, keywords like accessibility may be helpful
<dmontalvo> Like "What we're working on" and don't need WAI W3C in heading/Likes "What we're working on" and don't need "WAI W3C" in h1/
Shawn: We actually do need "accessibility". We could have a subtitle. How would we use this?Think of Brent's boss - what accessibility specifications do we need to pay attention to? or you're at some accessibility meetup - I'd like to volunteer. - go look at this page...
Michelle: post on Twitter - needs more description in the title. Introducing WAI to people
Shawn: The goal is not to introduce WAI. It's really to tell people what we're working on currently and to get people to help us with the good work
Michelle: what we're working on - who's "we"? Going back to posting on social media and how that will work
Brent: this is a page full of information - not content on our homepage. Where is it located on the homepage.
Shawn: The first link you are right is about news and we will want to promote it heavily.
Brent: would the link say "what we're working on"? or be more descriptive?
Shawn: wondering about subtitles
Daniel: maybe shorten to say "What WAI is working on"? then add a subtitle. instead of "What we are working on". That may help the referencing issue.
Shawn: some people know WAI - this is not about teaching. Our target audience are people who know WCAG but may not know WAI.
Michelle: In that case a subtitle is a good idea
Estella: I agree with Michelle - not knowing what "we" references and what areas of accessibility. Use of "working" without referring to any specific field or area of interest. "working" sounds generic.
Shawn: what would we say instead?
Estella: find something more comprehensive
Shawn: I agree I just can't come up with anything. Anyone have other ideas ? What We're Working On <subtitle>
Estella: "working" is like "we" too general
Shawn: thoughts on a date?
<shawn> What We're Working On in March 2022
Krisanne: it'll force that it's updated
Shawn: I don't want to do it unless there's a good reason to do it. Date is important and I can do it ahead of time. I don't mind the maintenance.
<kevin> +1 to including date... agree that I don't like not knowing how up to date information is
Daniel: I would support a date up front.
I would favor a date
<dmontalvo> Maybe quarter-based
Michelle: I'm ok with a date but the month was jarring. something that let's me know that it's for the year.
Shawn: Ideally it would have an updated link. I don't want all edits listed in changelog
Carlos: I don't think page needs a changelog. Can we have dated entries on the page?
Brent: how detailed will the entries be? for example WCAG3. When that is published WCAG3 comes off the list? Do we need to specify only active work?
Shawn: in between - we wouldn't wait for it to be publish. As soon as it goes to "we're done" it would drop down to publications. A lot of completed EO work is not listed. We're trying to communicate better what we're actively working on. What we're working on + subtitle.
Carlos: more friendly - for people not native speakers - stick to more formal description
<dmontalvo> +1 to Carlos comments, I just edited one of these sub titles but probably the others need a pass to
<eoncins> +1 Carlos comments
<kevin> +1 to 'upcoming publications' if only to avoid the metaphor
Shawn: several people are encouraging a more casual tone - I want to be careful of phrases that cause confusion.
Brent: If any other thoughts, add to github issue
Brent: daylight savings this weekend in the US
<dmontalvo> That's an hour earlier in Europe
Brent: Reminder to update survey for face to face and remember that we will also make it virtual for people who cannot attend.
Shawn: The meeting will be more like a hybrid event- f2f in person with and remote access provided. Even if you can't make it in person - give preference in the survey for virtual attendance
Brent: For the weekly survey - there will be minutes to read and open issues in github for more participation. Anyone have anything else to share?