<scribe> scribe: eoncins
Daniel: The first item was raised
by Michelle in distinguishing good practices and requirements
in accessibility. Maybe we can make language stronger in this
sense.
... do you feel that is difficult from an instructor
perspective between requirements and best practices=?
Howard: What is the proposed solution? If it is not a WCAG requirement should we mention that? To me it is not workable. Not everything is a WCAG requirement...
<dmontalvo> https://content-author-modules--wai-curricula.netlify.app/curricula/content-author-modules/structure/
Howard: if we were doing a section to assess that would be different. I do not understand that this is a problem.
+1 to Howard
Daniel: I also agree. For
instance in headings WCAG provide guidance but it is not
compulsory. Maybe we can reword some sections to make it more
explicit...
... we could address this with languages.
Carlos: I agree with Howard.
While I was reading the curricula I did not distinguished
between requirements and best practices. If the content was on
evaluation I have done that...
... but for this module and other modules I did not went
through this issue.
<GN> +1 to Howard
Daniel: I will get back to Michelle and mention that out aim is to help teacher to develop materials and not making a distinction on what is requirement and what is a best practice.
Estella.: If needed it can be included as a teaching idea but we are not assessing activities.
Daniel: I would avoid that because it is out of the scope of the curricula. I would contact Michele and see needed adjustments.
<dmontalvo> Estella: Requirements and best practice zakim, zakim, take up next
<dmontalvo> https://content-author-modules--wai-curricula.netlify.app/curricula/content-author-modules/clear-content/
Daniel: This is about a learning
outcome from the "Clear content" module and my proposal is to
move it to the image modules to complement the text..
... proposal is to take it out of this module and added to the
images. Would people agree with that?
Howard: I am leaning towards agreeing but open to other opinions. It seems good practice and otherwise might be confusing.
Daniel: We have teaching ideas at a topic level but not at a module level.
Howard: I would agree to move it but open to other opinions.
<Howard> +1 to Carlos
Carlos: I am not against to move
it to images module but I would like to hear Estella arguments.
To me having it here makes sense. I do not see the need to move
it to the images module...
... to me it makes more sense to have it here.
<GN> +1 to Carlos
Estella: The comment it was not to remove it but to leave it here and make a link to the images module.
Howard: I see the link and you would also put something under teaching ideas and give some examples to complement.
Daniel: I see that there is a basic alignment on how deal with that and it might be a cross reference between clear content and images module
<dmontalvo> https://github.com/w3c/wai-curricula/issues/607
Daniel: This is either a language
issue. Kevin mentioned that it is not clear what table data is
in the definition...
... the suggestion is to say that "Table data cells contain the
individual pieces of data that make up the content of the
table"...
... I would say that the current structure works but I would
like to discuss it with this TF. Should we clarify the
scope?
... should we take the suggestion from Kevin or take another
approach and definition? What do people think?
Carlos: I like the distinction between data table header and data table cells. I agree with Kevin that the definition is not easy. I agree with the definition provided by Kevin and changing it.
Howard: I agree with Carlos. The wording is a bit difficult I think it needs a bit rewording.
Daniel: I see that there is a
need of rewording here. Instead of making reference to specific
type of data we should make reference to individual pieces of
information or data.
... Also about the multimedia module. We had several issues
about "governmental regulations" and now we have "government
regulations" we make explicit that there are policies and
regulations in different countries...
... now we have the accessibility requirements covering the
issues.
Estella: I do agree with the new rewording as far a mention is made to existing regulations.
Daniel: Just for context we had a
provided redundancy for sensory characteristics and we tried to
look for something more simple like match audio and video
content were possible but a flag was made that we were missing
some information...
... I propose to go back to what we had and include again the
sensory characteristics.
<dmontalvo> https://www.w3.org/WAI/media/av/av-content/#sensory
<dmontalvo> https://wai-curricula.netlify.app/curricula/content-author-modules/multimedia/#learning-outcomes-for-module
`+1 to include mention to sensory characteristics
<slewth> +1 to Howards point
Howard: I see the importance of
adding this. Maybe we can elaborate on the definition of
sensory characteristics.
... we should make sure that students kbow what is meant
here.
<CarlosD> +1 to Howard
+1 to Howard on adding a clear explanation of what sensory characteristic are.
Daniel: If you have any suggestions you are welcome to come back to me.
Daniel: As instructor you have to
be aware about which authoring tools are
accessible/inaccessible. Carlos raised this issue...
... should we say this given the fact that instructors should
already be aware of that?
<dmontalvo> https://content-author-modules--wai-curricula.netlify.app/curricula/content-author-modules/
Carlos: I don't feel strongly as
we are requireing that instructirs have knowledge of this, but
my argument for keeping it in the overview page...
... is that we do not have the requirements in the overview
page. Also because not only instructors will read this page but
also other users...
... for me it would be a good point to make.
Daniel: I am not happy with the current porposal maybe we need to worn instructors that authoring tools should be accessible. Any suggestions?
Estella: To me the author module is about creating accessible content but I do understand the importance of an accessible authoring tool.
Daniel: Yes this is an impirtant aspects and I will surely get back to you.