evaluation correction

schedule-ugrad.md

@@ -86,7 +86,7 @@ description: Class schedule and links to lectures, readings and assignments
 {: .week}
 # Week 5 (10/20 - 10/26): Accessible In Industry
 
-## Monday: Accessibility and Software Engineering 
+## Monday: {% include slide.html title="Accessibility and Software Engineering" loc="software-engineering.html" %}
 - <i class="fa-solid fa-house-laptop" aria-hidden="true"/>  [Accessibility Implementation](assignments/technology-implementation.html) Due
 
 ## Wednesday:  Industry perspectives on accessible

slides/evaluation.html

 ---
 layout: presentation
-title: Evaluation  --Week 5--
+title: Evaluation  --Week 4--
 description: Accessibility Needfinding and Evaluation
 class: middle, center, inverse
 ---
 background-image: url(img/people.png)
 
 .left-column50[
-# Week 5: Accessible Evaluation
+# Week 4: Accessible Evaluation
 
 {{site.classnum}}, {{site.quarter}}
 ]
@@ -376,5 +376,4 @@ You read about Alexa's use by people with disabilities in class. Form small grou
 - Write down a list of accessibility assessment goals (metrics)
 - Identify potential accessibility concerns 
 
-Post on [Ed](https://edstem.org/us/courses/31170/discussion/2427390)
 

slides/software-engineering.html

+---
+layout: presentation
+title: FOOBAR  --Week N--
+description: Accessibility
+class: middle, center, inverse
+---
+background-image: url(img/people.png)
+
+.left-column50[
+# Welcome to the Future of Access Technologies
+
+Week N, FOOBAR
+
+{{site.classnum}}, {{site.quarter}}
+]
+---
+name: normal
+layout: true
+class:
+
+---
+# Important Reminder
+
+.left-column[
+![:qrhere](nil)]
+
+## Make sure zoom is running and recording!!!
+## Check on zoom buddies
+## Make sure captioning is turned on
+
+---
+[//]: # (Outline Slide)
+# Learning Goals for today
+
+
+---
+
+# Why isn't the World Already Accessible?
+
+Designing for accessibility is hard
+
+Implementing accessibility is hard
+
+Testing accessibility is also hard!
+
+---
+# Who Creates Accessibility?
+
+**Organizations impact accessibility**
+
+ 
+---
+# Who Creates Accessibility?
+
+Organizations impact accessibility
+
+**Designs have a big role in what is accessible**
+
+
+---
+# How might UX Designers address Accessibility
+
+Include it in design requirements
+
+Provide ALT text for images and buttons
+
+Provide guidance for both nonvisual and visual structure (e.g. proper linear order)
+
+---
+# Who Creates Accessibility?
+
+Organizations impact accessibility
+
+Designs have a big role in what is accessible
+
+**Developers also of course very important**
+- Need to understand the expectations of APIs and accessibility technologies
+- Need to understand screen readers
+
+
+---
+# How do practitioners enact accessibility in practice?
+
+[Accessibility in Software Practice](https://dl.acm.org/doi/pdf/10.1145/3503508)
+
+- data from 15 interviews and 365 survey respondents from 26 countries across five continents --> 120+ unique codes
+- followed up with a survey --> 44 statements grouped into eight topics on accessibility from practitioners’ viewpoints and different software development stages. 
+
+
+---
+# Organizational & People Challenges 
+
+.quote[Before making any decisions about “Accessibility”: stakeholders (e.g., designers, architects, developers, testers, and clients) in a project should
+reach a consensus on accessibility development and design]
+
+| Challenge                              | Recommendation                                     |
+|----------------------------------------|----------------------------------------------------|
+| Lack of resources                      | Long-term organizational buy-in and budget         |
+| Culture                                | Cooperative Culture                                |
+| Size (too small)                       | Work with customers & teams to prioritize access   |
+| Inadequate expertise & education       | Include accessibility expertise among team members |
+| Lack of QA to go with developer effort | Include accessibility on testing team              |
+
+---
+# Process Challenges (technical)
+
+Notice details of WCAG guidelines low on this list!
+
+| Challenge                                 | Recommendation                                       |
+|-------------------------------------------|------------------------------------------------------|
+| Unclear requirements & planning           | Include accessibility at all stages                  |
+| Unclear scope & architecture requirements | Engage with relevant end users                       |
+| Difficulty testing                        | Use appropriate testing suites & integration testing |
+| Lack of complete access practices         | Rigorous refactoring                                 |
+| Inappropriate tools                       | Well-designed documentation    & training            |
+| Domain-dependent issues                   | Appropriate end user engagement and testing                                                     |
+
+---
+# Who Creates Accessibility?
+
+Organizations impact accessibility
+
+Designs have a big role in what is accessible
+
+Developers also of course very important
+
+**These days, a lot of it is created by end users**
+- This means that you have to think about *indirect* impacts on content creation too (i.e. what do you expose to end users in authoring tools)?
+