Date / Time
|Time||Links / Notes||Coordinator|
|Accessible Survey tools||Workshop||David, Gloria|
Aug. 4, 2020
|2 - 3:30pm ET|
Agenda and notes (Google Doc)
|GSoC 2020: Controller Input Project||Crit||Tony Atkins|
Aug. 11, 2020
|10 - 11am ET||Jonathan Hung|
|IDRC Website||Crit||Cheryl Li||Aug. 18, 2020||2 - 3:30pm ET||Jonathan Hung|
|Community Meeting: Care for the Future (AMC Plenary screening)||Workshop||Cheryl Li||TBD||TBD|
Workshops from previous years can be seen on the Previous Community Workshop Topics page. Video recordings may not have captions. If you would like to contribute to captioning any of the videos, please reach out to us through the fluid-work mailing list.
|Links / Notes|
|Fable Introduction||Abid||Tuesday May 26 ( 2 - 3pm ET)||Video Recording|
|DEEP 2020 - brainstorming||Gloria, Vera||May 19|
|Problems Machine Learning can Solve||Ted||April 1|
|MyL3||Sepideh, Dana, and Philip||March 25|
|Designing and Programming with Multiplicity||Philip Tchernavskij||March 18||Meeting Notes|
Skills Development: Remote collaboration strategies
|Justin||March 11||Notes (Google Doc)|
|Assessment Process||Lorna Lo||February 26||Video|
|Skills Development: Accessible web design, implementation, and validation tools and techniques||Jon Hung||February 19|
Notes (Google doc)
|Making OCAD You - Passport||IDRC||February 12|
|Discussion about Irisbond||Eduardo Jauregui||February 5||Irisbond|
|Kindle Accessibility||JoAnna Hunt||January 28||Special date and time (10am ET)|
|Machine Learning: What it can and can't do|
|Google Summer of Code 2020 planning & brainstorming||January 8||Google Summer of Code 2020 with the Fluid Project|
Agile development: planning
|Teacher to talk about education plans (EP)||Guest?|
|Students with learning disabilities to talk about their experiences||Guest?|
|People working with students on mindfulness and mental health||Guest?|
|Talk to people who teach children to program||Lighthouse Labs?|
|Someone from able gamers to talk about how people with various disabilities interact with games||Guest?|
|People working with young adults with autism||Guest?|
|Rose? How people engage in social connections and relationships||Guest?|
|Engage with OCAD students to talk about their projects and/or areas of study. ( MDes and others)||Guest?|
|Someone who has developed software for older adults|
|Someone who works with brain sensing tech||Muse?|
Someone to talk about entrepreneurship and marketing ( how to reach people to use our software and services e.g. P4A, Outside-in, hack-a-thons, etc.)
|Latest A11y models and principles to follow, and language to use ( e.g. things that the MDes students are taught )||Jutta?|
|Accessibility in the Toronto Public Library||Guest?|
Case Studies of User Creativity in Computing (Monthly)
Skills Development workshops (Monthly?) Below are some examples of topics that could be covered.
|Offsite Visit: Location||Topic||Contact|
|Underground Hack Lab?|
|Blooorview Research Institute|
|IDI Partners (e.g. UofT, Ryerson, etc)|
|KidsLearningCode/GirlsLearningCode||Teaching children to program|
|Challenges / Hack Session / Workshop||Facilitator|
A critique (or more informally a "crit") is an opportunity for us to come together as a small group and examine and discuss a creative artifact - a design wireframe, a persona, a newly-implemented UI or software component, etc.
These design crits are informal, constructive, specific, and respectful. It's a forum where anyone from the community can bring their designs and receive feedback.
The idea is to focus on tangibles, not on abstract plans:
Since these meetings are participant driven, there will be occasions when the crit will not meet. Meetings will be announced in the schedule above, and to the relevant mailing lists (i.e. inclusive design community list, and fluid-work).
Techniques like UX Walkthroughs, Inclusive Design Mapping Tool ("Petals & Flowers"), or User States and Contexts will help us concretely assess and discuss an artifact from different perspectives. It's based on the idea that creative work gets stronger when it is discussed amongst peers and diverse ideas are considered.
Crits help us to:
We try to keep design crits very informal and casual on purpose. This makes it easier for participants to share designs (requiring less time preparing formal presentations), and opens up more time for organic conversations. A formal presentation of your project or design is not required, and we encourage a more conversational approach.
Design crits are a great opportunity to discuss designs, refine ideas, ask questions, and get feedback. To get the most out of a design crit: