Meeting minutes
First ideas on writer modules https://github.com/w3c/wai-curricula/wiki/writer-modules-outline
Daniel: There are 6 modules. First focus on upfront, then content structure, page, headings, paragraphs. Then links and how to write link text...
… thinks that are under author responsibilities, then alt-text and images and how to write alt-texts. We may want to get into details...
… then much the same with multimedia and the six module talks about instructions, messages for errors. This might be an overlap with a modules from the designers...
… I am looking now for first impressions and what might be overlapping.
Carlos: Not really sure if this is what you are asking for. My first comment would be what the users of this curriculum would be looking for...
… I only found this in multimedia. This is only my initial thought and putting in open. Should we address this?
… I would start with structure and then these. Links are focused on text links and non text links should also be provided by content authors...
… these are only my initial thoughts.
Daniel: The first point is very relevant. Is this the best structure within the modules? That's a good suggestion. We may move to a more content based structure.
Brent: I agree with Carlos. It is important to group thinks together and ask content writers to know how to group the different elements in the modules...
Daniel: I used a UC as an inspiration. For me the first think that they have to know is how to structure a document. That's the rationale behind...
… I see Carlos point and see if we have to group them differently.
Gerhard: +1 to Carlos and Brent. For me an important point missing is E2U.
Daniel: Yes this is something missing that I want to address later on.
… we need to discuss how to approach this. I was thinking on a separate module on this issue.
estella: +1 to Carlos
estella: additionally to the easy to read requirement, it is also needed to consider transcriptions
estella: we are also missing color contrast, which is also relevant to content authors
<estella> Daniel: This is something that we can address later on.
<CarlosD> estella: this module also applies to people who own a personal website... we need to consider these users, that do not work with developers and designers
<CarlosD> ... they will need to know to measure the color contrast
Daniel: Which type of author are we addressing is something that we may have to discuss also.
Brian: To me it makes sense to have an introductory module on how address the language and good writing techniques. From general into specifics.
Daniel: I understand the point of an introduction module.
David: Couple of additional observations it that module and topics are more specific than in other curricula. I am also wondering if we are missing tables or other problematic content...
… text alternative for complex graphics or mathematical content.
Daniel: I was struggling myself with the page titles. Type content based would be a good solution.
<Zakim> shawn, you wanted to ask what different organization might be?
Shawn: I was wondering about the recommendation of content based type and would like to know if anybody has an idea.
Carlos: I should give a thought.
Daniel: I also have a difficulty on this.
Daniel: I would have to give it a thought.
Howard: Making writing understandable should also be explored.
Sarah: I agree with the different points. I wonder also about labelling, maps and other different issues. Maybe grouping content might be useful...
… having an overarching introduction and then go into more detail.
Daniel: We need to restructure. Since we have too many different type of audiences we may need to know how to approach this.
<CarlosD> estella: an issue relevant to content authors is the use of inclusive language
<CarlosD> dmontalvo: That would fall under a module about language
<CarlosD> ... I'm not sure if this is going over the current accessibility requirements we have
Author versus writer
Daniel: Thanks for the thoughts. We will need to see how to address inclusive language and also plain language or easy to read
<dmontalvo> www.w3.org/WAI/curricula/
Daniel: We had different ideas about content authors, should we use this term. In WCAG content authors are different agents.
… let's leave it open for discussion. What do you think?
… something similar with what we did with the designer, and we ended up focusing on visual designers and UX researchers.
… writer emphasizes more on the writing part of what a writer needs to take into account.
Carlos: Writer seems to me to focus on writing and we need to address other types of content authors...
… I would not focus on content writer and I prefer author but I do not have a clear opinion.
… initially I was thinking more on content authors with a team but we should also consider content authors with no teams and working alone.
Daniel: If you do not have the technical knowledge and the CMS do not have the accessible possibilities what should you do then?
Carlos: Well then you should change your tool.
Daniel: Then we properly need to introduce things such as "what the tool can do and can not do"
Brian: If you are a one man team you want to have the knowledge of all the different modules...
<shawn> +1 to Brian on focusing this set on writing (not broader issues like contrast or tools)
Brian: sometimes we need content writers to ensure that a proper alt-text is provided.
… all the challenges that content authors have are very important but it has to be something specific about writing.
Daniel: In the overview page we can say that this is mainly aimed to instructors. The curricula is also designed for that.
<CarlosD> estella: which is your inspirational use case?
<CarlosD> ... even when working in a team, the content author is responsible for the content, not the designer or developer
Daniel: My focus might be mainly on writing content not considering the different CMS.
<CarlosD> estella: so we're not considering the different CMS neither LMS
<shawn> Use case is instructors. Scope -- For this curricula with specific modules, I think this one should focus only on writing words, not on things like contrast that are covered in the designer modules.
Shawn: One of the big things is that is about instructors. Therefore we want to focus on the writing of words...
<shawn> "Author" vs. "Writer" -- complicated by WCAG wording. That alone might 'force' us into writer.
Shawn: the other point is that if you go to WCAG the word "content author" is used for different roles.
Daniel: We can discuss this issue and explain in the overview page.
… I will follow up with you.