Meeting minutes
Rewriting Topic Visual Appearance https://content-author-modules--wai-curricula.netlify.app/curricula/content-author-modules/clear-content/#topic-visual-appearance
Brian: Maybe move "grouping" to the end
Howard: Content grouping makes it clear
Daniel: We are going to use "content grouping" and we will move this to the end so that it's clearer
Brian: LOs 3 bullet, maybe split these into two
… Overall grouping would be oen bullet and the other inner space, fonts, and alignment would be the other one
Daniel: Will do these changes
Module 3: Forms -- Breaking down the responsibilities of each of the roles involved in labels, instructions, and error messages https://github.com/w3c/wai-curricula/issues/637
https://
Brian: MAybe instead of says who does what, we should explain why we are saying that these elements require collaboration between different team members
Module 3: Forms -- Referencing placeholder https://github.com/w3c/wai-curricula/issues/636 ]
https://
Brian: It could be added a references that labels should be persistently visible, mentioning that if text disappears that's an issue for many people
Howard: I consider placeholders text placed in the field, as long as it's in the field, that's a placeholder
Brian: That word is an HTML attribute but it is also a word in common language, I think we can use it for purposes different than the code meaning
Spanning on layout tables explanation
https://
Howard: More important message is "try to avoid them"
… "identify situations ..." we should not have that sentence because it may imply that there are situations where layout tables are allowed
Brian: Maybe "explain why tables should ont be used for layout purpose"
Howard: The specific example of emails is wordy. The approach is not to give too many examples when we are talking about exceptions
Daniel: Change to "explain the accessibility problems of layout tables and avoid them where possible" kind of formulation. Explore if we should mention the email example ,but not get too much into details