<scribe> Scribe: Sharron
Brent: There is a summary of the issue in GitHub
<brent> https://github.com/w3c/wai-personalization-standards/issues/7
Janina: We're looking for something to name what we expect to be transformative technology, Personalization is currently associated with marketing and so we need to more clearly ID the accessibility aspect of what we are doing. Using ARIA as a model. Iti is a recommendation about to go the CR and look for implementations. That's the overview.
Brent: EO hisotrically has been part of naming conveetnions and comeup with something that works well - so let's jump in.
Matthew: Happy to be here and wondering if you need any further background - have people seen the video, slides, etc?
Brent: Yes we have provided links to the background materials and last week's minutes.
Steve: Comparing this to Morphic and the personalization it does, this seems to be author driven rather than through the external Morphic activity. I think this could be a game changer beyond accessibility. Thinking that the word "content" should be in the title to indicate that it will allow the user to select. Arrow may be confused with ARIA.
Janian: Contnet is only as subset.
Kevin: What do you mean?
Janina: Content is only one
module, there is more to come, so we are looking for a schema
that we can use xxxx: Moduile name. So it is content yes but
more - in the current spec there are 8 possible modules.
... highly specialized, inclusing symbols rather than text for
example.
Steve: That still all seems very content oriented to me. Various elements of presenting content adaptation.
Kevin: And I would agree with what Steve said. My understanding is that it was framing content in a way that suits the user.
<brent> CASE: Content Adaptation & Semantic Elements
Matthew: I agree and want to point out that 'content' is so broad that we may have to focus on whether it is all semantics, all content or a bit of both. So far some aspects are loosely defined (related to tools) Adding smenatic data at the element level to support the adaptations. I think 'adaptation' is important and can be in the name. And remember that it is a schema that we can use as the
umbrella term for the specific module.
Steve: It is good to think about the fine grain of the element adaptation.
Brent: Today is meant to brainstorm and make suggestions to the group that will allow them to shop names around and have other consdieration.
Janina: The overall grouping name to the left of the colon and the specific module to the right.
Brent: and could that be an acronym?
Janina: Yes
Daniel: All about content, semantics, etc. But the boundaries are not so clear and not sure that either of these terms should be in the title. I woulkd stay with adaptation or personalization.
Kevin: Yes, agree with Daniel.
The modules will provide more detail so the left of the colon
where the key terms are adaptation, communicatiolng that I can
adapt this to the way it best meets my needs. I would avoid
acronymns since in government we have them coming our our ears
and they often mask meaning.
... everyone thinks ARIA is a great acronym but nobody knows
what it means. Rather than finding an acronym and then words to
fit it, we want to lead with the meaning.
Janina: There is reason why acronyms proliferate, even though we ahd not previously thought of them.
KrisAnne: This is for the user. ARIA lacks that idea of support for the user and we want to not make that mistake again. The people who benefit from this need to be part of how it is branded - since it is for a person, we forget the end user. Not just specs to memorize or to make thier lives more difficul, it is to support different people and to widen the scope of how you can present content to
different user needs.'
<brent> UPAC: User Personalization of Adaptable Content
<stevelee> says it all
<kevin> +1 to keeping it simple
<Howard> I like Shawn's suggestions from github
<krisannekinney> +1 to simple too.
Shadi: I completely see where
you're going. We try often to build too much into the title.
This is a good excercise. Not everyone needs to know everything
about accessibility. Often it is just a metter of "tell me what
to do and make sure it works" For many developers that is
sufficiant. No one may know what ARIA means but it makes sense
when expanded.
... not sure Sharron's suggestion would make a difference.
Brent: I agree to keeping it simple and if possible stick to words if possible.
Matthew: Lots of this is resonating with me, would love to continue when we have more from our group in the discussion. We wondered if the title should include our goals.
<dmontalvo> +1 to referring to the goal of spec in title
Matthew: I agree that acronyms can be problematic but can also be catchy. I like UPAC but wonder about what the expansion will tell people.
<kevin> +1 to avoiding user responsibility implication, although I think that could be avoided
Howard: I liked the Personaized Adaptation that was in the GitHub. It is short, easy to remember. Or Personaized design, kind of a play on to Responsive design.
Jade: Nothing to add to PAL which I added to GitHub. We may need to rething if we create an acronym with real meaning we should go their, it is a lingusistic considersideration. One with real meaning behind it.
KrisAne: I have the same fear Jade.
<shadi> +1 to Jade
Brent: We will link to the minutes, but don't forgt GitHub
<kevin> *
Matthew: This is great, I wish I had time to join this group, very grateful for all the serious thought you have given. Would like to schedule when we have more of our group to join. Thanks very much for all of this.
Brent: Congratulations to Daniel, the TF, and EO that the Designer Modules are now published, great job.
Daniel: Thank you all so much, it was defintely shared work and your reviews have improved the resource. We hope it will continue with the Author/Writer modules.
Shadi: On record, conratulations to Daniel and the TF.
Daniel: And thanks to you Shadi for your incredible support through the years.
<dmontalvo> https://github.com/w3c/wai-curricula/issues/471
Daniel: Here is the link to the
GitHub issue. Now that we have Foundation, Developer, and
Designer modules, we are turning to the question of what
author/writer. content developer needs to know. In WCAG,
"author" is used to mean many things. We considered "Writer"
but that created confusion in itself. Use cases did not quite
fit.
... We are addressing people who would use tools to write
content. We are proposing to change "Author" to "Writer" and
focus on the aspects that instructors need to teach people who
will be writing for the web
Brent: One of the reasons we invited the ARRM group, they have outlined roles in order to map WCAG to them. So they have "Author" and "Publisher"
<dmontalvo> https://www.w3.org/WAI/tips/writing/
Laura: I agree that writing
implies more about writing for the web but you can write code.
Have to be careful that we don't confuse people.
... I understand the subtlety, in my role at the library, I am
part of the editing team even though I don't write the content,
I am part of the team.
Daniel: We did have that discussion about developers need to udnetand writing related to headings etc. We may need to cross reference.
<CarlosD> +1 to Jade's interpretation
Jade: When I think of the term "writer" I think of things like plain language and it is specific to the language construction. I think it is broader - content or author or something bigger than writing.
<Michele> +1 to Jade as well
Jade: the way peole use the term writer they think of the language itself, not the structure.
<jade> +1 to content author!
Shadi: I agree wih Jade. WCAG and ATAG uses author in a broader sense. The Tutorials talk about content authors to distinguish them fro developers and designers. "Content author" returns many times more results in a search than "content writer"
<kevin_> In Scottish Government we call them Content Designers
Brent: Maybe then "Author" would work in the context of the other modules.
Sharron: "Content Authors"
<shadi> [[recalls some use of "non-technical authors" in some contexts too]]
Laura: Yes we would need a modifying term whether we use author or writer to distinguish about coders.
<dmontalvo> https://www.w3.org/WAI/curricula/designer-modules/
Carlos: Yes content author for me would be the preferred term. Writer is associated with narrative content not all the other aspects of what might be in web page.
<shadi> +1 to CarlosD point on text and media coverage
<brent> +1 to Carlos
Daniel: In the previous modules, we could keep one word and use the intro to distinguish. I want to avoid scope creep that would try to address the different types of CMS or LMS. Instead we will try to let the instructors know that they should become aware of accessibility features in that tools.
Shadi: I recall the term "non-technical authors" has been used. I am not following why the term 'writer' or 'author' would change the scope. There may be a need to point out that some tools have more a11y support without detailing. Or is it about the creation of video and media content?
Daniel: Creating tables and layout features may be needed and students would need to be guided about their use. But when it comes to content authors who are not just writing, we have the anger of overlapping with the design modules.
<shadi> +1 to cross-referencing
Sharron: Web tasks often overlap - I am assuming some cross referencing
Shadi: Cross-referncing is important and we have some aspects of that now. To what degree do authors need to be aware of content styling related to contrast, color use etc. So from a slightly different persepective perhaps the information needs to be within this module.
Daniel: I am hearing to keep the term 'content authors' and that we may need to refer to more than just the language - text alternatives, media, contrast, etc as well as cross referencing for detail.
Brent: Any other comments?
Sharron: Follow up with ARRM?
Daniel: No need this is aligned to what they have now.
<shadi> +1 to how well-organized this group is!
Brent: In the past we had a weekly survey and have lately gotten away from it. Jade's comment reminded us of how useful it was. Thanks for the feedback. Any other comments or suggestions about what would make it more useful?
KrisAnne: We are working on adding calendar invites to the surveys.
Jade: Yes it really does help - work now is carnage so this makes it much more possible for me to find and respond.
<brent> Face-to-face availability survey: https://www.w3.org/2002/09/wbs/35532/f2f2022/
trackbot, end meeting
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/Adadeptation/Adaptation/ Succeeded: s/No one may know what ARIA means but they know to use it./No one may know what ARIA means but it makes sense when expanded./ Succeeded: s/follw/play/ Succeeded: s/maning/meaning/ Succeeded: s/ thinks that ARRM is some sort of military hardware!// Succeeded: s/"non-technical writers"/"non-technical authors"/ Succeeded: s/Curricul:/Curricula:/ Default Present: krisannekinney, stevelee, Michele, Jade, Laura, Sharron, CarlosD, JennC, MarkPalmer, Sylvie, Daniel, Leticia_, Howard, Vicki, shadi, kevin, Matthew_Atkinson Present: krisannekinney, stevelee, Michele, Jade, Laura, Sharron, CarlosD, JennC, MarkPalmer, Sylvie, Daniel, Leticia_, Howard, Vicki, shadi, kevin, Matthew_Atkinson Found Scribe: Sharron Inferring ScribeNick: Sharron Found Date: 18 Feb 2022 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]