Meeting minutes
Setting up meeting, choosing scribe https://www.w3.org/WAI/EO/wiki/WAI_Curricula/WAI_Curricula_Task_Force_Meetings#Scribe_Rotation_List
FYIs -- actions on my part based on survey results
<Daniel> https:
Daniel: feedback - don't use 'ensure'. Use another verb.
… Topic "enough time" should be split into other parts, such as interaction and feedback.
… Fonts and sizes need to be balanced and improved contrast ratios.
Cross references to developers and authors
Daniel: current state of cross-reference may imply that ...
designers and content authors need to do these.
Are these instructions to designers for what to tell other roles what to do going too far?
<Daniel> https://
Daniel: these cross-references are spread through entire curriculum.
Roberto: does not think this is going to far. In fact, it's necessary.
Carlos: agrees with Roberto - not going to far.
… Similar requirement in the other modules, including developer modules.
Dave: Concurs with Roberto and Carlos. Critical part of designer curricula that ...
… they understand the requirements they have - i.e. include designing interactions ...
… that can be implemented in an accessible way. Need to emphasize this.
Roberto: Designer needs to provide the need for an accessible label even ...
… if they are not doing the coding to implement it.
Estella: agrees with above but questions use of 'ensure' to explain it. Verb ...
… is too strong.
Daniel: 'ensure' will be replaced.
"Informational Design" Correct scope? Correct terminology?
Daniel: some pointed out this topic name may not be the most accurate, or best terminology ...
… for example, the cover things like multimedia.
Daniel: for example, in this module forms, tables are covered. Also headings are covered.
Some have said other items should be included that are not there.
Carlos: Does find what's included there as important. But should have other ...
… topics such as graphic design. Maybe moving other topics from other modules ...
… to this one but graphic design is key.
… Graphic design might include appropriate alternate text for images.
Perhaps drop the module on images and include that content here.
Carlos: did suggest in his feedback which modules to move various ...
… image topics to.
Roberto: Perhaps we should include more on 'data visualization.'
… Includes use of charts, tables and how you convey complex data ...
… in a visual way.
Howard: maybe 'data visualization', because it is so complex and a ...
… specialty, should be addressed elsewhere.
Daniel: value in mentioning 'data visualization' at least.
Shadi: A la wikipedia, information design derives from 'graphic design.'
… Agrees that 'Informational Design' is probably much broader than what ...
… we cover but no clear definitions as to the meaning of 'informational Design.'
Daniel: ID is usually covered broader in other courses he has reviewed: i.e. how ...
information is represented, graphics, images.
Estella: using text/language that is easy to understand should also be included...
… I.e. avoid complex language.
Shadi: placement of text, color of headings, make a difference of how readable ...
… and usable a page/site is.
Daniel: Hears that group is not quite on agreement on whether module topics should be broadened.
He will come up with a proposal to address the general feedback on this.
David: noticed that subjects such as 'error messages' are not included.
… Is it the responsibility of designers for areas such as 'error messages'?
… Or just how these messages are laid out?
David: may want to expand what we have with the ...
… expectation that we will have to reorganize it later.
Roberto: there's another project where responsibilities are assigned ...
… by role.
Daniel: existing project on mapping responsibilities to roles. Includes...
… a decision tree and set of definitions for these roles.
… Reminder that we will be developing modules for content authors.
Brings up broader question of how much of this curricula belongs to just ...
… informational designer and how much to other roles.
Carlos: agrees with David suggestion to get as much content in this ...
… module as we can and then perhaps to place it on other sections ...
… that address other roles.
Carlos: to classify, not suggesting to put the actual content for other ...
… roles in this module but just not these are topics that have to be addressed in ...
… other roles.
Shadi: perhaps we make cross-references to other modules instead of ...
… including all the topics that come up.
Daniel: will try to expand the scope of this module.
zakin, take up item 5
Merging current "Page Layout" and "Navigation and Orientation"
Daniel: considering merging 'page layout' and 'navigation and orientation.'
Could add 'font size' to Page Layout', for example.
David: makes him nervous when looks at the topics currently in each module.
… Worries that we lose some content if we combine these modules.
… Looking at some text books to see how these topics are addressed...
… elsewhere. For example, in a 'A Web for Everyone' they use the term ...
… 'Wayfinding.' Maybe this would be a better term.
Daniel: will take a look at this change of terms.
<sloandr> Here's the table of contents for "A Web for Everyone", as an example of organisation of content: https://
Carlos: shares David's perspective on being reluctant to combining 2 modules.
… Believes the scope would become too broad if we combine these two.
Roberto: for now, agrees with the separation. Merging would hurt ...
… one of the two.
Shadi: right now a lot of overlap. Likes Roberto's suggestion.
Roberto: perhaps the emphasis could be that 'page layout' refers ...
… to one specific page as opposed to 'navigation and orientation.'
Daniel: will work on clarifying each topic area.
David: One specific suggestion: Rename 'responsive design' to ...
… 'flexible design.' Latter could include text enlargement by user.
Daniel: will consider this.
Everyone: kudos to Daniel for covering a broad topic.