Starting meeting, choosing scribe

<scribe> scribe: Estella

Appropriate balance between benefits for people with disabilities and benefits for all

<dmontalvo> https://www.w3.org/2002/09/wbs/35532/curricula-author-starfish/results#xoverall

<dmontalvo> https://www.w3.org/2002/09/wbs/35532/curricula-author-starfish/results#xm2

Daniel: First goes to question module 1 and second question is related to module 2. There seems to be much mentions on benefits all users...
... for instance in clear content and structure related to headings and navigation...
... maybe we need to fix more on benefits to people with disabilities...
... Shawn highlights that maybe we should have 2 different types of LO one for people with disabilities and another to benefits for all. My response is that the curricula should focus primarily to people with disabilities...
... how do you think that this should be addressed?

Sarah: This is challenging. But we should focus on people with disabilities but also use benefits in the notes for teachers...
... I think that this is difficult.

Daniel: I also see the need for discussion. From your comments I see that LO should focus on peoples with disabilities and then in teaching ideas give more freedom to teachers.

Carlos: I agree with Sarah's views and I see this as a balanced approach.

Howard: I agree about talking to the benefits for everyone. I do not understand how do you want to approach this?

Daniel: I would try to focus in the LO about the benefits for peoples with disabilities. And in the teaching ideas more on benefits for everyone.

Brent: I don't have much to add.

Daniel: This applies to different modules and I will make a pass on that. We are going to try to fix LOs related to people with disabilities and then in the teaching ideas benefits for all.

Scalability and flexibility of font sizes https://github.com/w3c/wai-curricula/issues/513#issuecomment-1134471994

Daniel: Shawn mentioned the issues related to scalability and flexibility. Apart from easy to read font types and sizes there is also a need to render the content resizable...
... if you go into the last bullet of the clear content module. I have added a sentence to cross post with the designers module...
... authors should not focus on style but on content. What do you think?

<Brent> Estella: Trying to understand. I believe that content authors sometimes have responsibilities even though they are not the main role responsible.

Daniel: We can discuss this issue as I see that sometimes content authors can be responsible for that.

Howard: I wouldn't see as primary responsibiltiy for content authors. This would be the designer. But they should be aware of that. It seems that is not on the scope of the content author.

Carlos: I agree with the views of Howard and see the views of Estella we need to clarify the roles as in some cases authors are actually responsible for that...
... it is good for the user to be aware about contrast ratio, flexibility (etc...)...
... as this is for teachers we should have a some note for them informing the issues that are covering and relating to designers and developers.

Daniel: Yes I see the point but I would try to be conservative in what we add here...
... sometimes content authors will not have the technical expertise to solve this issue.
... for content types and sizes I agree to add the information, when it comes to layouts and configurations I see this as problematic.
... It is difficult to define the limits between the content authors and designers. Content authors will surelly have a say on font type and size, but in terms of layout this will not follow on their own responsibility.

Howard: I agree with Daniel's take on layout which might be out of the scope for content authors.

Brent: When talking about contrast ratio authors might be aware of some issues and collaboration with designers is needed...
... if there is a clear responsibility for content authors we need to make sure that it is mentioned in the curricula.
... depending on the cases content authors are responsible for choosing the background but in other situation they might not be responsible.

Daniel: It seems to me that this will lead us to possible teaching ideas on fonts, contrasts, and other requirements...
... what should we say to teachers? Should we cross reference to dsigners?
... We could add some cross reference between content authors and designers.

Brent: A good instructor will make a mention on that. Instructors should be aware of that.

Daniel: I will put some LOs and complement it in teaching ideas and get back to you.

Should descriptions list be mentioned? https://github.com/w3c/wai-curricula/issues/513#issuecomment-1134471994

<dmontalvo> https://github.com/w3c/wai-curricula/issues/537

Daniel: We have a paragraph on lists but we do not get into much detail. If you want to create a definition list is not easy to implemented properly...
... this was my rational for not including definition lists. We mention html tags and elements in the developers. Mark up structures might be out of scope for the content authors.

Howard: It seems something that is not used very often and I think that should not be included.

+1 to not include it

Brent: To me a content author writes and is in the scope of the designer or a developer.

Daniel: Now we have it under module 2 structure. Creating the definition list is more related to developers and designers.

Brent: Content authors should make sure that the content is listed.
... the developer/designer should need to know how to implement it.

Daniel: It is about providing an ordered list, numbered list.

Brent: I see the importance for that.

Daniel: I will add it in the taching ideas.

+1 to Brent

Daniel: It is important that content authors provide annotations for designers/developers for content lists.

Carlos: I alos agree.

Daniel: Now I have added content to this module. And I may ask you to read this module and provide feedback.

Brent: In the multimedia section you added the topic and teaching ideas as new content?

Daniel: Teaching Ideas and assessment are new for you to review.

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)

Present: CarlosD, eoncins, Brent, Howard
No ScribeNick specified.  Guessing ScribeNick: eoncins
Found Scribe: Estella

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

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.)