diff --git a/assets/css/style.scss b/assets/css/style.scss
index c95a32bf96427d1b0fdabbdf32ae3dc03d545e5d..37f8ba666cc2349bbd21a76e42498c6848e3527c 100644
--- a/assets/css/style.scss
+++ b/assets/css/style.scss
@@ -5,15 +5,15 @@ $navbar-color: #3a1c6f;
 $dark-color: #3a1c6f;
 $gradient-dark: #3a1c6f;
 $gradient-light:  #006666;
-$link-color: #338585;
-$link-visited-color: #607386;
+$link-color: #2a6f6f;
+$link-visited-color:  #556677;
 $link-hover-color: #3a1c6f;
 $lecture-background: #164756 ;
-$lab-background:#d8e6c9;
-$background: #d8e6c9;
-$highlight-dark: red;
-$highlight-light: lightcoral;
-$break-color: #ddeeee;
+$lab-background:  #e6efdc;
+$background: #e6efdc;
+$highlight-dark: #cc0003;
+$highlight-light: #fad1d1;
+$break-color:  #eef6f6;
 $topic-color:   #EAE4EE;
 $activity-color:   #f0f4f2;
 $highlight-darkest: #660000;
@@ -260,7 +260,7 @@ table.schedule {
    background-color: $highlight-light;
    border: 0.15em solid $highlight-dark;
    border-radius: 0.5em;
-   color: $white;
+   color: $highlight-dark;
    font-size: large;
    padding: 0.25em 0.5em;
    margin-bottom: 1em;
diff --git a/assignments/website.md b/assignments/website.md
index 79eabd7dab662e5c0fe5ce033b135fe134617e79..959a9494eeb2ae4ba5ed15c62941f583ad54dea8 100644
--- a/assignments/website.md
+++ b/assignments/website.md
@@ -1,6 +1,6 @@
 ---
 layout: assignment
-published: draft
+published: true
 
 title: Website/App Accessibility UARS (Individual)
 description: Learn to assess website/app accessibility using a variety of technologies
diff --git a/slides/assessment.html b/slides/assessment.html
index 33c86e28f6ccbf29397900eaa0320334ca9d38c6..85d9e285585fd31652e4ee4239524bbacacb1dd9 100644
--- a/slides/assessment.html
+++ b/slides/assessment.html
@@ -348,6 +348,9 @@ Understandable live & recorded video for people who are not able to see the scre
 
 Other factors such as avoiding seizures & so on
 
+???
+delete avoiding seizures next year
+
 ---
 # Captioning Videos
 
diff --git a/slides/assessment2.html b/slides/assessment2.html
index d4f300a58cd14349efa6658b5647c6f687f2f3d9..9b1f2e23e2c8e3ed300845ca0e3514e9e81f0627 100644
--- a/slides/assessment2.html
+++ b/slides/assessment2.html
@@ -22,6 +22,33 @@ class:
 ## This is an important reminder
 ## Make sure zoom is running and recording!!!
 
+---
+# Announcements (1/3)
+- Ed posts getting lost: 
+
+  - We'll try to use pinning more! 
+  - Also, quick tour of how we organized [Ed]({{site.discussion}}).
+
+--
+- Contrast: Thank you Kirsten! Fixed (I hope!). 
+  - Maybe we can add the class website to next year's assignment :). 
+
+---
+# Announcements (2/3)
+
+- Presentations as an assignment: We received feedback that this is very stressful. This is an important concern to unpack. 
+
+  - Would be happy to talk about this more 1:1 with anyone
+  - Have started an [Ed discussion on ideas around presenting]({{site.discussion}}/458634}}) for those interested.
+  
+---
+# Announcements (3/3)
+
+- Could there be a ed post each week of a summary of assignments that are due that week? 
+
+  - Let's try, please let us know if it is helpful. 
+  - Also, [Canvas]({{site.canvas}}) has assignments with due dates for everything due each week: Reading questions, assignment, and weekly participation survey. 
+
 ---
 [//]: # (Outline Slide)
 # Learning Goals for Today
@@ -32,7 +59,7 @@ class:
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.1
+## Guideline 2.1 (1/5)
 Keyboard Accessible
 ]
 .right-column[
@@ -40,34 +67,31 @@ Keyboard Accessible
 No other input form has this flexibility or is universally supported and operable by people with different disabilities, as long as the keyboard input is not time-dependent.
 
 Examples of who benefits
-- screen reader users
-  - blind users 
-  - reading disabilities
-  - ...
+- screen reader users (e.g. blind users, reading disabilities)
 - speech input users
 - switch input users
 
 ]
 
 
----
-# POUR: Operable: Guidelines 2.1-2.5
+<!-- --- -->
+<!-- # POUR: Operable: Guidelines 2.1-2.5 -->
 
-.left-column[
-## Guideline 2.1
-Keyboard Accessible
+<!-- .left-column[ -->
+<!-- ## Guideline 2.1 -->
+<!-- Keyboard Accessible -->
 
-Discuss with your neighbor and post
-]
-.right-column[
-<iframe src="https://embed.polleverywhere.com/free_text_polls/zXxJ9XBdJQPaUsFM1ie5J?controls=none&short_poll=true" width="800px" height="600px"></iframe>
-]
+<!-- Discuss with your neighbor and post -->
+<!-- ] -->
+<!-- .right-column[ -->
+<!-- <iframe src="https://embed.polleverywhere.com/free_text_polls/SHF2YF26NRUApLALP0WHj?controls=none&short_poll=true" width="800px" height="600px"></iframe> -->
+<!-- ] -->
 
 ---
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.1
+## Guideline 2.1 (2/5)
 Keyboard Accessible
 ]
 .right-column[
@@ -82,27 +106,52 @@ Keyboard Accessible
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.1
+## Guideline 2.1 (3/5)
 Keyboard Accessible
 ]
 .right-column[
 Some common pitfalls:
 
 - Keyboard Traps. Content should not "trap" keyboard focus within subsections of content on a Web page. This is a common problem when multiple formats are combined within a page and rendered using plug-ins or embedded applications.
+]
+---
+# POUR: Operable: Guidelines 2.1-2.5
+
+.left-column[
+## Guideline 2.1 (4/5) 
+Keyboard Accessible
+]
+.right-column[
+Some common pitfalls:
+
+- Keyboard Traps.
 - Invisible Content. Some parts of a web page can never be reached
-- Lack of Control. Users should be able to reconfigure or remove shortcuts
+]
+---
+# POUR: Operable: Guidelines 2.1-2.5
 
-Note: Not in guidelines (that I know of) but a "reverse trap" is whether you can reach text that *doesn't* have links or headers when using switch input. How would you do this?
+.left-column[
+## Guideline 2.1 (5/5) 
+Keyboard Accessible
+]
+.right-column[
+Some common pitfalls:
+
+- Keyboard Traps.
+- Invisible Content. Some parts of a web page can never be reached
+- Lack of Control. Users should be able to reconfigure or remove shortcuts
 ]
 
 ???
+Note: Not in guidelines (that I know of) but a "reverse trap" is whether you can reach text that *doesn't* have links or headers when using switch input. How would you do this?
+
 Character key shortcuts work well for many keyboard users, but are inappropriate and frustrating for speech input users — whose means of input is strings of letters — and for keyboard users who are prone to accidentally hit keys. To rectify this issue, authors need to allow users to turn off or reconfigure shortcuts that are made up of only character keys.
 
 ---
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.2
+## Guideline 2.2 (1/2)
 
 Enough Time
 ]
@@ -118,7 +167,7 @@ Many users who have disabilities need more time to complete tasks than the major
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.2
+## Guideline 2.2 (2/2)
 
 Enough Time
 ]
@@ -133,26 +182,25 @@ Enough Time
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.3
+## Guideline 2.3 (1/2)
 
 Seizures and Physical Reactions
 ]
 .right-column[
- Some people with seizure disorders can have a seizure triggered by flashing visual content, even for a second or two.
- - Most people are unaware that they have this disorder until it strikes. 
+In 1997, a cartoon on television in Japan sent over 700 children to the hospital, including about 500 who had seizures.
+ - Most people are unaware that they are triggered until it strikes. 
  - Warnings do not work well because they are often missed, especially by children who may in fact not be able to read them.
-
-It is possible to avoid these types of flashes and still create appealing apps/websites
 ]
 
 ???
-In 1997, a cartoon on television in Japan sent over 700 children to the hospital, including about 500 who had seizures.
+It is possible to avoid these types of flashes and still create appealing apps/websites
+
 
 ---
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.3
+## Guideline 2.3 (2/2)
 
 Seizures and Physical Reactions
 ]
@@ -165,23 +213,22 @@ Seizures and Physical Reactions
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.4
+## Guideline 2.4 (1/5)
 
 Navigable
 ]
 .right-column[
-This guideline ensure that users can: 
-- Find the content they need / go somewhere they want to go
-- Keep track of their location. 
-- Orient themselves within a website or app
+- Can users find the content they need / go somewhere they want to go?
+- Can users keep track of their location?
+- Can users orient themselves within a website or app?
 
-This guideline works closely with Guideline 1.3, which ensures that any structure in the content can be perceived, a key to navigation as well.  Headings (1.3.1) are particularly important mechanisms for helping users orient themselves within content and navigate through it. 
+Connections: Guideline 1.3 (any structure in the content can be perceived).  Headings (1.3.1) are an important example of structure that supports navigation and orientation.
 ]
 ---
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.4
+## Guideline 2.4  (2/5)
 
 Navigable
 ]
@@ -194,63 +241,130 @@ examples: Navigation (that is the same on every page on a site); Anything that i
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.4
+## Guideline 2.4 (3/5)
 
 Navigable
 ]
 .right-column[
 - Can jump over uninteresting content
 - Each web page has a descriptive title; Links have link text that is clear about their purpose; Headings and labels describe topic and purpose
+]
+---
+
+# POUR: Operable: Guidelines 2.1-2.5
+
+.left-column[
+## Guideline 2.4 (4/5)
+
+Navigable
+]
+.right-column[
+- Can jump over uninteresting content
+- Titles; Links; and Headings are clear and descriptive
 - Focus order makes sense. This can be problematic in any web page, and is requires special support when navigating trees and tables.
 - Focus is visible (A) and perceivable (AA) and not obscured by other content (A)
+]
+---
+
+# POUR: Operable: Guidelines 2.1-2.5
+
+.left-column[
+## Guideline 2.4 (4/5)
+
+Navigable
+]
+.right-column[
+- Can jump over uninteresting content
+- Titles; Links; and Headings are clear and descriptive
+- Focus order makes sense and focus is visible and perceivable 
 - Users should be able to locate a web page, and orient themselves, within a website
-- Section headings are used to organize the content, styling is handled through CSS not heading level
+- Section headings are used to organize the content, styling is handled through CSS, not heading level
 ]
 ---
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.5
+## Guideline 2.5 (1/5)
 
 Pointers, just like Keyboards, should be able to access everything
 ]
 .right-column[
 
-All functionality should be accessible via pointer input devices. 
+- All functionality should be accessible via pointer input devices. 
+- People operating pointer input devices may not be able to carry out timed or complex gestures. Examples 
+  - drag-and-drop gestures and on touch screens
+  - swiping gestures
+  - split taps
+  - long presses. 
+- They may also have trouble selecting small targets, or with precision (i.e. due to tremor)
+]
 
-People operating pointer input devices may not be able to carry out timed or complex gestures. Examples 
-- drag-and-drop gestures and on touch screens
-- swiping gestures
-- split taps
-- long presses. 
+---
+# POUR: Operable: Guidelines 2.1-2.5
+
+.left-column[
+## Guideline 2.5 (2/5)
+
+Pointers, just like Keyboards, should be able to access everything
+]
+.right-column[
+- Support a variety of input options including a single pointer; offer alternatives to gestures and other physical actions
+   - avoid path based gestures when possible; 
+   - offer alternatives to path based gestures or multi-finger gestures
+   - provide programmatic alternatives to shaking or tilting or dragging based interaction
+   - **overall goal**: allow users to use multiple possible types of input (keyboard, pointer, on-screen keyboard, stylus, etc)
 
-They may also have trouble selecting small targets, or with precision (i.e. due to tremor)
 ]
 
 ---
 # POUR: Operable: Guidelines 2.1-2.5
 
 .left-column[
-## Guideline 2.5
+## Guideline 2.5 (3/5)
+
+Pointers, just like Keyboards, should be able to access everything
+]
+.right-column[
+- Support a variety of input options; a single pointer; offer alternatives to gestures and other physical actions
+- Trigger content only on *up* events (after a complete click)
+]
+---
+# POUR: Operable: Guidelines 2.1-2.5
+
+.left-column[
+## Guideline 2.5 (4/5)
 
 Pointers, just like Keyboards, should be able to access everything
 ]
 .right-column[
-- Support a single pointer without path based gestures when possible; When not, offer alternatives to path based gestures or multi-finger gestures
-- Ideally trigger content only on *up* events
-- Make sure that the *accessible name* for a component matches the visual one to better support programmatic access provided by accessibility tools. 
-- Provide programmatic alternatives to shaking or tilting or dragging based interaction
-- Make targets at least 24x24 CSS Pixels (AA) or 44x44 CSS Pixels (AAA) to make selection easier
-- Allow users to use multiple possible types of input (keyboard, pointer, on-screen keyboard, stylus, etc)
+- Support a variety of input options; a single pointer; offer alternatives to gestures
+- Trigger content only on *up* events
+- Make the *accessible name* and visual name for components match
+  - better supports programmatic access provided by accessibility tools. 
+]
+
+---
+# POUR: Operable: Guidelines 2.1-2.5
+
+.left-column[
+## Guideline 2.5 (5/5)
+
+Pointers, just like Keyboards, should be able to access everything
+]
+.right-column[
+- Support a variety of input options; a single pointer; offer alternatives to gestures
+- Trigger content only on *up* events
+- Make the *accessible name* and visual name for components match
+- Targets of: 24x24 CSS Pixels (AA) or 44x44 CSS Pixels (AAA) make selection easier
 ]
 
 ---
 # More on Size
 
+.left-column40[
 Especially hard on mobile devices
 
-.left-column40[
-![:img An arrow vs arrow and label make very different target sizes ,90%, width](img/assessment/targets.png) 
+![:img An arrow vs arrow and label make very different target sizes ,80%, width](img/assessment/targets.png) 
 ]
 
 .right-column60[
@@ -268,7 +382,7 @@ Trying to hit a small button with one hand while standing on a moving, crowded b
 # POUR: Adaptable: Guidelines 3.1-3.3
 
 .left-column[
-## Guideline 3.1
+## Guideline 3.1 (1/4)
 Readable
 ]
 .right-column[
@@ -281,15 +395,48 @@ Readability mean supporting people with all sorts of reading disabilities/readin
 # POUR: Adaptable: Guidelines 3.1-3.3
 
 .left-column[
-## Guideline 3.1
+## Guideline 3.1 (2/4)
+Readable
+]
+.right-column[
+Provide meta data language
+ - Including parts of a page if the language switches). 
+ - Also provide pronunciation information when needed to read aloud properly
+
+]
+
+---
+# POUR: Adaptable: Guidelines 3.1-3.3
+
+.left-column[
+## Guideline 3.1 (3/4)
+Readable
+]
+.right-column[
+Provide meta data language
+
+Provide a dictionary
+   - easy to find & well organized 
+   - include jargon, abbreviations, and other unusual words
+
+]
+
+---
+# POUR: Adaptable: Guidelines 3.1-3.3
+
+.left-column[
+## Guideline 3.1 (4/4)
 Readable
 ]
 .right-column[
-Provide meta data about the language of a page (or parts of a page if the language switches).  Also provide pronunciation information when needed to read aloud properly
+Provide meta data language
 
-Provide a well organized, easy to find glossary or dictionary for jargon, abbreviations, and other unusual words
+Provide a dictionary
 
-Use clear and simple language at an appropriate reading level for the audience whenever possible; when not include clear and simple summaries. Possibly provide an audio or sign language version of content
+Aim for clarity & simplicity
+   - Use clear and simple language at an appropriate reading level
+   - If not possible, include  clear and simple summaries. 
+   - If possible provide an audio or sign language version of content
 
 ]
 
@@ -297,7 +444,7 @@ Use clear and simple language at an appropriate reading level for the audience w
 # POUR: Adaptable: Guidelines 3.1-3.3
 
 .left-column[
-## Guideline 3.2
+## Guideline 3.2 (1/4)
 
 Predictable
 ]
@@ -314,23 +461,55 @@ Present content in a predictable order that is consistent across an app or websi
 # POUR: Adaptable: Guidelines 3.1-3.3
 
 .left-column[
-## Guideline 3.2
+## Guideline 3.2 (2/4)
 
 Predictable
 ]
 .right-column[
-- Don't trigger events that change context *just due to focus* (e.g. don't submit a form; launch a dialog; etc on focus), whether on page elements or inputs. Describe what will happen before a change to a form control. 
-- Locate navigation menus, search fields, skip to navigation links and so on in the same 2D onscreen position and logical (linear ordering) position throughout a site.
+- Focus alone shouldn't trigger events: provide control over content changes
+  - don't submit a form; launch a dialog; change layout, etc on focus
+  - instead provide an "update now" button; "submit" button; etc
+  - same for page elements or inputs. 
+  - Describe what will happen before a change to a form control. 
+
+]
+
+---
+# POUR: Adaptable: Guidelines 3.1-3.3
+
+.left-column[
+## Guideline 3.2 (3/4)
+
+Predictable
+]
+.right-column[
+- Focus alone shouldn't trigger events: provide control over content changes
+- Locate repeating elements consistently throughout site
+   - navigation menus, search fields, skip to navigation links; help and so on
+   - same 2D position
+   - same logical linear ordering
+   
+]
+
+---
+# POUR: Adaptable: Guidelines 3.1-3.3
+
+.left-column[
+## Guideline 3.2 (4/4)
+
+Predictable
+]
+.right-column[
+- Focus alone shouldn't trigger events: provide control over content changes 
+- Locate repeating elements consistently throughout site
 - Use familiar names and icons for things. As much as possible be consistent with global standards, not just within the app/site.
-- Provide control over content changes (e.g. an "update now" button; "submit" button)
-- Provide consistent access to help 
 ]
 
 ---
 # POUR: Adaptable: Guidelines 3.1-3.3
 
 .left-column[
-## Guideline 3.3
+## Guideline 3.3 (1/5)
 
 Input Assistance
 ]
@@ -346,16 +525,63 @@ Try to reduce the number of serious or irreversible errors that are made
 # POUR: Adaptable: Guidelines 3.1-3.3
 
 .left-column[
-## Guideline 3.3
+## Guideline 3.3 (2/5)
 
 Input Assistance
 ]
 .right-column[
-- Forms should support error identification with specific and easily found text error descriptions that provide appropriate suggestions for correcting errors.
-- Provide clear instructions and labels for form inputs, along with context-sensitive help 
-- Provide  an ability to review information before final purchase or submission of information. This is especially important when the consequences may be serious (such as an expensive purchase)
-- Don't require people to re-enter redundant information (automate instead)
-- Make sure authentication techniques are accessible 
+- Support form validation
+   - forms should support error identification with specific and easily found text error descriptions 
+   - provide appropriate suggestions for correcting errors
+]
+
+---
+# POUR: Adaptable: Guidelines 3.1-3.3
+
+.left-column[
+## Guideline 3.3 (3/5)
+
+Input Assistance
+]
+.right-column[
+- Support form validation
+- Make forms clear
+  - Provide clear instructions and labels for form inputs
+  - Provide context-sensitive help 
+]
+
+---
+# POUR: Adaptable: Guidelines 3.1-3.3
+
+.left-column[
+## Guideline 3.3 (4/5)
+
+Input Assistance
+]
+.right-column[
+- Support form validation
+- Make forms clear
+- Support review
+  - Support review before final purchase or submission of information. 
+  - Especially when the consequences may be serious (such as an expensive purchase) or hard to undo
+
+]
+
+---
+# POUR: Adaptable: Guidelines 3.1-3.3
+
+.left-column[
+## Guideline 3.3 (5/5)
+
+Input Assistance
+]
+.right-column[
+- Support form validation
+- Make forms clear
+- Support review
+- Simplify authentication
+  - Don't require people to re-enter redundant information (automate instead)
+  - Make sure authentication techniques are accessible 
 ]
 
 ---
@@ -369,8 +595,14 @@ Commonly used security method
 - Designed to be hard for computers and easy for humans
 - Require vision
 
+No good accessible alternatives -- [audio CAPTCHA are easy to crack](https://arstechnica.com/information-technology/2008/12/computer-scientists-find-audio-captchas-easy-to-crack/) and hard to use ([video with more info](https://www.youtube.com/watch?v=raFXfU7_fkg)).
+
 ]
 
+???
+Pointer to later 2nd wave accessibility topic: Accessibility and computer security
+
+
 ---
 # Audio CAPTCHA Accessibility
 
@@ -387,30 +619,17 @@ Commonly used security method
 Answer: 
 ]
 
----
-# Audio CAPTCHA Accessibility
-
-No good accessible alternatives -- [audio CAPTCHA are easy to crack](https://arstechnica.com/information-technology/2008/12/computer-scientists-find-audio-captchas-easy-to-crack/) 
-
---
-...and hard to use: 
-
-![:youtube Example impossible audio CAPTCHA, raFXfU7_fkg]
-
-???
-Pointer to later 2nd wave accessibility topic: Accessibility and computer security
 
 
 ---
 # POUR: Robust: Guideline 4.1
 
 .left-column[
-## Guideline 4.1
+## Guideline 4.1 (1/3)
 
 Compatible
 ]
 .right-column[
-This was already a running theme but let's make it explicit:
 
 Don't break user accessibility technologies (AT) with things like poorly formed markup
 
@@ -422,22 +641,31 @@ Follow conventions and be compatible with APIs as much as possible
 
 ]
 
+???
+This was already a running theme but let's make it explicit
+
+
 ---
 # POUR: Robust: Guideline 4.1
 
 .left-column[
-## Guideline 4.1
+## Guideline 4.1 (2/3)
 
 Compatible
 ]
 .right-column[
-Example strategies to do this
 - Use standard and complete start and end tags on web pages
 - Use standard types of status messages to announce changes in content that are not user initiated (e.g. "18 results returned" from an asynchronous search task)
 - Provide name, role, and value custom controls
 
-[ARIA](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA) is a key standard used to do this for **A**ccessible **R**ich **I**nternet **A**pplications, read up on it if you are trying to build an accessible website
 ]
 
+---
+# ARIA
+
+[ARIA](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA) is a key standard used to do this for **A**ccessible **R**ich **I**nternet **A**pplications
+
+- Read up on it if you are trying to build an accessible website
+- You'll see it in WAVE results