- From: Daniel Montalvo <dmontalvo@w3.org>
- Date: Mon, 8 Feb 2021 09:03:55 +0100
- To: <public-wai-curricula@w3.org>
- Message-ID: <000a01d6fdf0$f3f70980$dbe51c80$@w3.org>
[Correcting date -- I meant February 9, not 16]. --- Hello all, Tuesday February 9 we are going to have another WAI Curricula Task Force teleconference. Topic: WAI Curricula Task Force Weekly Meeting Time: February 9, 2021, 5:00 PM CET (Central Europe Time) Teleconference link and password: <https://www.w3.org/2017/08/01-eowg-info.html> https://www.w3.org/2017/08/01-eowg-info.html IRC: <http://irc.w3.org?channels=#wai-curricula> http://irc.w3.org?channels=#wai-curricula Port 6665. Channel #wai-curricula --- We will be discussing first ideas on designer modules at <https://github.com/w3c/wai-curricula/wiki/designer-modules-outline> https://github.com/w3c/wai-curricula/wiki/designer-modules-outline Please note we may tweak the agenda. If so, I will send a follow-up email. Agenda: agenda+ Overall structure and contents Anything missing? Anything should not be there? Agenda+ Visual design vs UX design This curriculum will likely be called "Designer Modules" and intends to address both visual and UX design. In which ways could we better communicate this distinction? Should we have a specific module on visual design for instructors who build courses for visual designers only? Agenda+ Cross-posting designer and developer shared responsibilities Currently there are some developer-centric concepts, together with strong assumptions for designers to provide indications to developers about how to implement accessibility features. Should we keep these assumptions? Can these assumptions be counter-productive for some instructors who may perceive these curricula as very skilled for the average designer? Best. -- Daniel Montalvo Accessibility Education and Training Specialist W3C/WAI
Received on Monday, 8 February 2021 08:03:58 UTC