From fa5998fd91878267bb4ec6c4267614b3ae89ef6d Mon Sep 17 00:00:00 2001
From: Jennifer Mankoff <jmankoff@cs.washington.edu>
Date: Wed, 27 Sep 2023 21:04:14 -0700
Subject: [PATCH] Week1 jen

---
 assignments/finding-accessibility.md | 11 +++++++----
 schedule.md                          | 20 ++++----------------
 2 files changed, 11 insertions(+), 20 deletions(-)

diff --git a/assignments/finding-accessibility.md b/assignments/finding-accessibility.md
index e514f21a..f1538faa 100644
--- a/assignments/finding-accessibility.md
+++ b/assignments/finding-accessibility.md
@@ -38,6 +38,9 @@ Some things students have told us about this assignment:
 - "I enjoy doing this because I watched a few videos and learned a lot of accessibility technology tools [and why we have them]."
 - "It was surprisingly difficult to find first-person accounts for the tech I chose."
 
+## Example
+An example can be found at the start of [slide deck]({{site.discussion}}/3515497) that you will add your slide to.
+
 # Details
 
 To complete this assignment you will need to do the following: 
@@ -46,9 +49,9 @@ To complete this assignment you will need to do the following:
 
 Watch [a video about presenting
 accessible](https://www.youtube.com/watch?v=L9TxhGv91kc) by Kyle
-Rector and look at [DOIT's](https://www.washington.edu/doit/tips-delivering-accessible-presentation#:~:text=Provide%20attendees%20materials%20(ideally%2C%20ahead,time%20captioners%20materials%20in%20advance.) guidance no accessible presenting. Review information about [describing images](https://webaim.org/techniques/alttext/) and [describing people](https://www.youtube.com/watch?v=By6nzFefcxs) in images verbally (during a presentation) or in text. Finally, make sure you don't use [ableist language](https://www.popsugar.com/fitness/common-phrases-that-are-ableist-48080654). 
+Rector and look at [DOIT's](https://www.washington.edu/doit/tips-delivering-accessible-presentation) guidance no accessible presenting. Review information about [describing images](https://webaim.org/techniques/alttext/) and [describing people](https://www.youtube.com/watch?v=By6nzFefcxs) in images verbally (during a presentation) or in text. Finally, make sure you don't use [ableist language](https://www.popsugar.com/fitness/common-phrases-that-are-ableist-48080654). 
 
-Optional reading [Its complicated: Negotiating Accessibility and
+Optional reading: [Its complicated: Negotiating Accessibility and
 (Mis)Representation in Image Descriptions of Race, Gender and
 Disability](https://guoanhong.com/papers/CHI21-ImageDescriptions.pdf)
 
@@ -114,7 +117,7 @@ If you have a chance to interview users of this technology, what would be one qu
 
 ## 4. Create two slides, one for each technology you found
 
-You will create one accessible slides (per AT) in a shared slide deck posted in the [Class Discussion]({{site.discussion}}) and on [Canvas]({{site.canvas}}). Your slide should include 
+You will create one accessible slides (per AT) in a shared slide deck posted in the [Class Discussion]({{site.discussion}}/3515497). Your slide should include 
 - A summary of the AT you researched 
 - Information about its audience (range of disabilities that use it)
 - A picture of it
@@ -126,6 +129,6 @@ Make sure the slides are accessible.
 # Turnin
 
 1. You will turn the slide in by adding it to the shared slide deck
-2. You will also present at least one of those slides in class. You should be prepared to 
+2. You will also present at one of those slides in class. You should be prepared to 
 - Stay on time (3-4 minutes + 1-2 minutes of questions). This will require you to pick and choose what to focus on when you design your slide, and to practice ahead of class.
 - Present accessibly (you may want to revisit  [presenting accessible](https://www.youtube.com/watch?v=L9TxhGv91kc) by Kyle Rector)
diff --git a/schedule.md b/schedule.md
index 636d6daf..a73345d7 100644
--- a/schedule.md
+++ b/schedule.md
@@ -485,23 +485,11 @@ Work in groups on final projects
 {% enddetails %}
 
 {: .week}
-# Week 9 (11/20-11/24): Group  Checkpoint 1
+# Week 9 (11/20-11/24): Group  Checkpoints (Full Group Required)
 
-{% details Monday 11/20: First Half of Group Presentations %}
-Present in class
-{% enddetails %}
-
-{% details Wednesday 11/22: Second Half of Group Presentations %}
-Present in class
-
-{% enddetails %}
- 
-{% details Thursday: Section %}
-Work in groups on final projects
-
-{% enddetails %}
+Sign up for a meeting slot *with your whole group* (details to be announced; slots will overlap class but also extend beyond class hours)
 
-## Friday 11/24: HOLIDAY
+## Thursday 11/23 and Friday 11/24: HOLIDAY
 {: .holiday}
 
 {: .week}
@@ -515,7 +503,7 @@ TBD
 {% enddetails %}
 
 {: .week}
-# Finals week: Final presentations -- time TBD
+# Finals week: Final presentations -- 12/12, 2:30pm 
 
 {: .lecture} Final project presentations
 : 
-- 
GitLab