From 8bde09882d3687a89f7b9cc185924f7d2da81dbe Mon Sep 17 00:00:00 2001
From: Jen Mankoff <jmankoff@cs.washington.edu>
Date: Fri, 18 Oct 2024 14:33:47 -0400
Subject: [PATCH 1/3] updated table of contents

---
 _config.yml            |  5 +++--
 _config_production.yml |  5 +++--
 assets/css/style.scss  | 12 ++++++++----
 3 files changed, 14 insertions(+), 8 deletions(-)

diff --git a/_config.yml b/_config.yml
index 3f9f3be5..7f7cac6e 100644
--- a/_config.yml
+++ b/_config.yml
@@ -68,8 +68,9 @@ sass:
   sass_dir: "./_scss"
   style: compressed
 
-kramdown:
-  toc_levels: '1'
+toc:
+  min_level: 1
+  max_level: 2
 
 mermaid: 'https://cdn.jsdelivr.net/npm/mermaid@10.5.0/dist/mermaid.min.js'
 
diff --git a/_config_production.yml b/_config_production.yml
index 3f9f3be5..7f7cac6e 100644
--- a/_config_production.yml
+++ b/_config_production.yml
@@ -68,8 +68,9 @@ sass:
   sass_dir: "./_scss"
   style: compressed
 
-kramdown:
-  toc_levels: '1'
+toc:
+  min_level: 1
+  max_level: 2
 
 mermaid: 'https://cdn.jsdelivr.net/npm/mermaid@10.5.0/dist/mermaid.min.js'
 
diff --git a/assets/css/style.scss b/assets/css/style.scss
index 24e1b812..ac75952f 100644
--- a/assets/css/style.scss
+++ b/assets/css/style.scss
@@ -110,15 +110,19 @@ a:hover, a:active, a:focus {
 
 ul#markdown-toc {
     min-width: 696px;
-    list-style: none;
-    padding-top: 20px;
+    font-size: .75em;
+    columns: 2;
+    -webkit-columns: 2;
+    -moz-columns: 2;
+    //list-style: none;
+    //padding-top: 20px;
 }
 
 ul#markdown-toc li{
-    display: inline;
+    //display: inline;
     padding: 5px;
     background-color: $background;
-    style: bold;
+    //style: bold;
 }
 
 ul li.tbd {
-- 
GitLab


From e8512010828f1ca19c5983cb581dd0ef2f4aa1e4 Mon Sep 17 00:00:00 2001
From: Jen Mankoff <jmankoff@cs.washington.edu>
Date: Tue, 22 Oct 2024 06:46:11 -0700
Subject: [PATCH 2/3] updates to week four branch

---
 assignments/technology-implementation.md | 8 ++++----
 schedule-ugrad.md                        | 3 ++-
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/assignments/technology-implementation.md b/assignments/technology-implementation.md
index 3131d31d..6e21ff61 100644
--- a/assignments/technology-implementation.md
+++ b/assignments/technology-implementation.md
@@ -34,10 +34,10 @@ To complete this assignment, please do the following
 You should identify a technology you have implemented *for general use* (i.e. not an accessibility technology). Ideally this should be an interactive technology (some kind of user interface, app, etc). If you have no such thing, you can ask to approve using a website or other static content that you have generated as an alternative. 
 
 {% details Possible examples (this list is still unders construction) %}
-- A class assignment that has an interface (web, mobile or other)
-- A web app
-- A mobile app (class projects are ok)
-- Your personal website
+- A class assignment that has an interface (web, mobile or other). If you've built a mobile app for 340, built a website for 154, or taken 331 (such as the campus map website) these are all things you could use.
+- A web or mobile app you built yourself
+- A profile of yourself on linked in, tiktok, or any other site where you've posted content.
+- Your personal website (even if it's hosted somewhere else like wordpress)
 - An interface wrapped around some machine learning program
 - An educational game for young children 
 - Tools for learning programming 
diff --git a/schedule-ugrad.md b/schedule-ugrad.md
index 6f742c36..f996e3f6 100644
--- a/schedule-ugrad.md
+++ b/schedule-ugrad.md
@@ -44,7 +44,8 @@ description: Class schedule and links to lectures, readings and assignments
 - <i class="fa-solid fa-house-laptop" aria-hidden="true"/> Preparation for next week: 
   - Read [The Importance of Manual Accessibility Testing](https://www.smashingmagazine.com/2018/09/importance-manual-accessibility-testing/) 
   - Read [Creating accessible images and diagrams](https://dis.acm.org/2023/creating-accessible-figures-and-tables/) 
-  - *Optional*: If you want to dig deeper, read [Dungeons and Dragons taught me how to write ALT text](https://ericwbailey.website/published/dungeons-and-dragons-taught-me-how-to-write-alt-text/) or read about [Making numbers accessible](https://www.tpgi.com/making-numbers-in-web-content-accessible/)
+  - *Optional*: If you want to dig deeper, read [Dungeons and Dragons taught me how to write ALT text](https://ericwbailey.website/published/dungeons-and-dragons-taught-me-how-to-write-alt-text/) or read about [Making numbers accessible](https://www.tpgi.com/making-numbers-in-web-content-accessible/) 
+  <!-- check this list too https://web-a11y.slack.com/archives/C4YFER329/p1729259893347819 -->
 
 
 {: .week}
-- 
GitLab


From c63cbc14b6ab3f01fc8e4b834e760cf806a962ed Mon Sep 17 00:00:00 2001
From: Jen Mankoff <jmankoff@cs.washington.edu>
Date: Tue, 22 Oct 2024 06:56:20 -0700
Subject: [PATCH 3/3] updated slides

---
 slides/industry-panel.html | 52 ++++++++++----------------------------
 1 file changed, 14 insertions(+), 38 deletions(-)

diff --git a/slides/industry-panel.html b/slides/industry-panel.html
index 71df5ab5..e7acc1a0 100644
--- a/slides/industry-panel.html
+++ b/slides/industry-panel.html
@@ -26,19 +26,6 @@ class:
 ## Check on zoom buddies
 ## Make sure captioning is turned on
 
----
-# Announcements
-
-UARS: How many -- one per tech minimum; give an example of a success if you find no problems. 
-
-Reminder: what to do if you miss a class 
-
-Reminder: regrades
-
-Summary: We'll keep doing it and add some more details to it as requested
-
-Visual calendar: We've heard this a few times. But I'm not sure where to put it or why canvas doesn't work. Can someone who's asking for this help us out with some user-centered design after class? :) 
-
 ---
 [//]: # (Outline Slide)
 # Learning Goals for today
@@ -48,50 +35,39 @@ Visual calendar: We've heard this a few times. But I'm not sure where to put it
 
 ---
 # First, Introducing your Website Report
-
-We modified the assignment a bit 
-- It's now two weeks long
-- It's optionally a group assignment (with others who reviewed the same website)
-
----
-# Introduction
-- What is the site or app for
-- How did you assess it (what accessibility tool did you use)
-- What task did you assess?
+## Introduction - purpose of site or app
+## Overview of assessment
+- Tasks your group assessed
+- What automated and ATs did you use
 - Overview table
 
-| Type (Web/Mobile/etc) | Testing Method | UARS found | Who Contributed |
-|-----------------------|----------------|--------------|-----------------|
-| ...                   | ...            | ...          |                 |
+| Type (Web/Mobile/etc) | Testing Method | # UARS found | Who Contributed |
 |-----------------------|----------------|--------------|-----------------|
+| ...                   | ...            | ...          | ...             |
 
 
 ---
-# Executive Summary
-
-Summarize biggest problems (1-2 paragraphs)
+# Next Sections
+## Summary of most severe problems
+Brief written summary
 
-| WCAG | Severe problems | Moderate problems | Minor problems |
+| WCAG # | # Severe problems | # Moderate problems | Minor problems |
 |------|-----------------|-------------------|----------------|
 | ...  | ...             | ...               | ...            |
-|------|-----------------|-------------------|----------------|
 
+## Details on Violations
 
 ---
 # Details
-More detail on what needs to be done sorted by WCAG # 
+More detail on what needs to be done sorted by POUR category
 
 Include both problems and remedies
 
 Easy to split this up among a group
 
 ---
-# Make the report accessible
-- Use headers
-- Use proper color contrast
-- Write alt text for photos
-- Use meaningful hyperlinks
-- Turn in a word or google doc on Canvas
+# Appendix
+All your UARS
 
 
     
-- 
GitLab