<scribe> scribe: Roberto_Perez
Daniel: Not too many people today so it is going to be a short meeting.
Daniel: We did received some comment asking for structural changes. Designer convention and language. We should get back to eog beffore going forward with changes.
Daniel: The proposal is to have
mmodule 1 renamed. The new one would be flexible color, layout
and design.
... The other topics I'll try to keep as they are, but we may
have to do additional changes.
... There was a comment that the language was not design
language. I have considered swapping module 3 and 2.
... There was discission on how to deal with data
representation.
... There is discussion on addding media player design as a
third topic for module 5.
... The title for the last one has also changed. i plan to
cover forms as a more prominent topic with label, instructions
and so on and adding interaction after.
Howard: I like the changes. All this things make sense to me.
<dmontalvo> Roberto: Makes sense, sounds better than whaat we have now
<dmontalvo> Roberto: Last module is a difficult module, difficult to decide what to tell designers and what to tell developers
Roberto: It is understandable that we are having dificulties with this. It is a subject which gives us a lot of headaches when dealing with product teams in real life.
Daniel: There will probably be another survey.
<dmontalvo> Live drat
Daniel: There are a number of wording changes on learning outcomes, for example in module 4. the intent is to simplify the language and better address designer responsability.
Howard: The changes look good. It also makes it easier on the format.
daniel: Here the request is to include designer tips. Tips for developers, writers... etcetera. The original idea was not to include them because they are part of the tutorial. planning to include them now.
<dmontalvo> Getting Started Tips resource
Howard: Will this go to teaching resources? It sounds fine there.
daniel: Adding that suggestion. Tips should go to teaching resources.
<dmontalvo> https://github.com/w3c/wai-curricula/issues/376
<dmontalvo> Roberto: Would be good also to point to the intent for each of the patterns
<dmontalvo> Roberto: What about pointing to the working examples? Maybe that is whaat a designer cares about most
Roberto: regarding aria authoring practices, suggest to point to working examples instead of the more technical sections of the patterns.
Howard: concerned that the technical nature of the aria authoring practices maybe too developer heavy for designers.
<dmontalvo> ARIA Authoring Practices
Daniel: We may open a short survey. If that happens it will be a yes or no format.
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: Howard, Roberto_Perez WARNING: Fewer than 3 people found for Present list! Regrets: Gerhard, Dave Found Scribe: Roberto_Perez Inferring ScribeNick: Roberto_Perez 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.)[End of scribe.perl diagnostic output]