WAI Curricula Task Force Teleconference

Setting up meeting, choosing scribe

<scribe> scribe: sloandr

Designer Modules not speaking to Designers EOWG discussion

<dmontalvo> https://www.w3.org/2002/09/wbs/35532/curricula-designers-starfish/results

<dmontalvo> https://github.com/w3c/wai-curricula/issues/384

<dmontalvo> Dave: Concerned about the comments, thought the module titles made sense

<dmontalvo> ... Module 1 does not cover what the title says

<dmontalvo> ... Making module title more descriptive of its content would help

<Howard> +1 to David's comments

Module 1 covers key visual design topics like use of colour and text styling, but doesn't reflect this in the module title. Could we extend the module title?

Howard: Agree to expand module title to more accurately describe the module topics

Splitting module "Flexible Layout and Design"

<dmontalvo> https://github.com/w3c/wai-curricula/issues/370

Daniel: Discussing suggestion of whether colour (including contrast) should be treated in its own module, splitting Module 1 into two modules

Gerhard: colour is a very important topic, could increase coverage in Module 1, but unsure if it's enough for a separate module

Howard: uncertain if there's enough on colour for a separate module

<dmontalvo> Dave: Potentially there is enough material to treat color accessibility on its own module, but it would be more detailed than some of the others

Daniel: in summary, we need to be careful about separating out a Colour module, with implications on increasing number of modules and also detail that the Colour module would need to go into. Need to discuss more with original commenter in EOWG

Moving focus indicators to the "Navigation" module.

<dmontalvo> https://github.com/w3c/wai-curricula/issues/390

Daniel: some concern that focus indicators should be covered in Navigation, and not (just) in Module 1's Landmarks and Cues topic

Howard: Feels it's okay covered in Cues

Donal: Also concern about limiting focus indication to navigation, when it covers other interactive elements where focus indication is relevant. But multiple things can be treated in multiple places, so may be helpful to cross reference focus indication in the Navigation module

Gerhard: Module 1 is a good place for focus indication, could be treated in a more prominent way

+1 to providing more prominence to focus indication within Module 1

<dmontalvo> Dave: +1 to that idea, probably having a specific topic on focus indicators and then cross referencing from other places would help communicate that focus is much more than navigation

Daniel: Will feedback to commenter, explaining rationale, looking at strengthening module 1's topic structure to draw attention to focus indication, and finding other places to cross reference back to the focus indication topic

Splitting "Interaction and Feedback" into "Forms" and "Interaction".

<dmontalvo> https://github.com/w3c/wai-curricula/issues/392

Daniel: another survey comment on the module structure, noting that the current interaction and feedback module doesn't sufficiently cover key design needs, and suggesting that form design is complex enough to warrant its own module

Howard: Could add forms to the module title and/or topic title? Can see forms being a separate module, but still unsure we should do this

Donal: it is good when navigating a list of topics to find the topic you're looking for, so if "forms" isn't explicitly covered in a module title or topics, that's an issue. Seems like it should be explicitly covered, maybe as a standalone topic in Module 6, and also mentioned in the module title. Forms are a major application of Interaction and Feedback, so seem to be naturally are covered in this module
... unsure about adding a separate module just for forms

+1 to Donal's comments

<Howard> +1 to Donal's comments

<gn> +1 to Donal's comments

Daniel: will respond to commenter with these thoughts

Overall module numbering

<dmontalvo> https://github.com/w3c/wai-curricula/issues/385

Daniel: feedback received that due to current naming and numbering approach, it can get complicated to distinguish modules from different curricula when looking at references of modules e.g. list prerequisites
... could use a mix of abbreviations and full names of a module, depending on context in which the module name appears
... what ways might we reduce complexity of module names, given the different contexts in which they appear?

Donal: on a different project, have used an approach distinguishing designer, developer, content provider modules using prefix DES, DEV and CP respectively.
... this prefix is always used when cross-referencing a module. Also included in page title and URL. Also each module has a number, used in combination with the prefix
... Have not researched this or received feedback, but chose it as a solution to a similar problem discussed in this agendum

+1 to Donal's approach

<gn> +1 to Donal's comments

Design user interfaces phrase

Daniel: has received feedback that use of "design" as a verb could be considered with more context when used in learning outcomes and other content
... example—some learning outcomes in Module 1 start with "design user interfaces with…", and maybe these could be shortened to focus on what the outcome addresses

Howard: not sure about the problem—can see there is some redundant use of the "design user interfaces with", but otherwise not clear what the issue is

Daniel: will think more about a proposal to address the concern, and bring back to the group

Howard: use of the verb "design" emphasises this as a design module