Meeting minutes
Clarifying scope of this curriculum with respect to future curricula.
<Daniel> https://github.com/w3c/wai-curricula/labels/Clarifying%20scope%20of%20different%20curricula
Daniel: question of whether we should include writing of alt text, form styles, color contrast...
Daniel proposes we add a clarifying statement that this curriculum will address that in later curricula but for this one - developer's - we are mostly
interested in coding.
David: would be helpful to signpost who else on the team would be responsible for ...
other success criteria. Is there a way to signpost who is responsible ...
for various areas?
Daniel: Will tweak the sentence to convey that techniques shown here ...
are only a part of the complete toolbox and other people ...
are responsible for other areas.
Carlos: where else will this signpost be placed? Just on the entry page? Probably best to have it...
in various places.
Daniel: thought of making it available in the teaching ideas also.
Carlos: in agreement. Won't just be in the overview page.
Howard: might be nice to have a link to other curricula areas that contain ...
topics outside of scope of this curriculum.
Shadi: thinks that for overview page, one brief sentence - add a sentence to what ...
we already have: "Other curricular address topics for other areas." Then link to the meta pages.
Third piece: don't get too much into "don't forget this, don't forget that."
Be conservative with adding to many references to other success criteria placed inline.
David: likes that idea. Don't want to complicate things. Balance that there are ...
other things besides markup and coding that need to ...
be addressed, letting them know that other members of the ...
team should address this but still want them to be aware of these issues.
Shadi: Looking at intro - getting started with accessibility. Have something on ...
getting started with accessibility.
Maybe refer back to "roles and responsibilities" back in intro module ...
Good to have developers understand these other roles.
Daniel: will look at these suggestions and see how it ...
can be addressed and worded.
Will try to be more concise to avoid resource being to large.
Howard: would it be helpful to have a section that refers to other areas related ...
to this module topic that would be covered by other roles.
Shadi: likes the idea but cautions against doing it too much - i.e. a nudge about ...
alt text. Once concern we often get is that it's too wordy ...
and too many cross links. Some people like this but others ...
find it a challenge. Suggests conservatism in the cross links, cross references.
Carlos: target audience - instructors who create accessibility courses?
Daniel: correct.
Carlos: with that in mind, would not work too hard on addressing ...
areas that need to be covered by other roles. Would expect ...
to be accepting of this approach.
Daniel: will come up with examples of how to address this.
Reorganizing the structure of the curricula
Daniel: been comments that certain topics do not fit well where they ...
are now located. For example, topic of focus, image types, etc., should be mixed ...
together with other topics.
Daniel: in this updated structure, would add navigation to "structure and semantics."
In "menus and submenus," would have single level and multilevel menus...
and then "additional level for menus." (See above links for more info on this reorganization).
David: for topic 2, suggests having navigation and other menus.
Carlos: feels more structured by bringing navigation to structure and semantics.
However, meta information could use reference to what ...
meta information we are talking about.
Also, really miss the types of images as a topic for 3rd module.
Needs topic on the types of images.
Shadi: agree with what David said. Wonder if meta data can be merged with navigation menus.
Shadi: types of images are there but merged under simple images.
Maybe "simple images" should be renamed to indicate it includes types of images.
But does agree that this does look much more streamlined. Forms content needs to be clarified.
Carlos: meta topics move to navigation and orientation proposed by Shadi, he would agree.
Regarding types of images, not aware that there are images that ...
don't have a functional or informational purpose. Important to ...
make clear that there are different types of images.
Carlos: same image can have different roles and therefore would need ...
a different alt element.
David: re: menus and submenus - mechanics of implementing links does ...
not seem to be covered. For example, using a link vs. a button. In the real world...
this gets confused...
Module 2 could talk about links and menus of links.
Shadi: would it fit under forms?
David: buttons would fit under forms but there are questions ...
regarding buttons and anchor links that come up in navigation ...
that could be addressed in second module.
Shadi: see often, divs and spans made into links. Like idea of addressing ...
links vs. buttons. But might fit better in forms.
Shadi: @ David, do people really use buttons for navigation?
David: yes, for example, pagination links. Introducing the fact ...
that this is not necessarily straight-forward might be helpful.
Comes up in audits he conducts.
Daniel: will be sending follow-up emails and putting these issues ...
in GitHub.
Will be meeting next week.