Merge branch 'UACCESS-23fa' of...

Merge branch 'UACCESS-23fa' of gitlab.cs.washington.edu:teaching-materials/undergrad-accessibility-website into week4-changes

assignments/index.md

@@ -22,7 +22,7 @@ questions or run into issue, please contact the course staff.
 | HW1: [Finding AT around us](finding-accessibility.html)                      | [Canvas HW1]({{site.canvas}}/assignments/8443510) | 10/3     |
 | HW2: [Disability Justice](disabilityjustice.html)                            | [Canvas HW2]({{site.canvas}}/assignments/8443521) | 10/9     |
 | HW3: [Web/App Access UARS](website.html)                                     | [Canvas HW3]({{site.canvas}}/assignments/8443528) | 10/16    |
-| HW4: [Web/App Access Report](website-report.html)                            | [Canvas HW4]({{site.canvas}}/assignments/8712208) | 10/21    |
+| HW4: [Web/App Access Report](website-report.html)                            | [Canvas HW4]({{site.canvas}}/assignments/8712208) | 10/23    |
 | HW5: [Post GUI Accessibility](technology-review.html)                        | [Canvas HW5]({{site.canvas}}/assignments/8712482) | 10/30    |
 | HW6: [Post GUI Accessibility Implementation](technology-implementation.html) | [Canvas HW6]({{site.canvas}}/assignments/8712492)  | 11/6     |
 | HW7: [Final Project Proposal](project-proposals.html)                        | TBD                                               | TBD      |

assignments/website-report.md

@@ -8,17 +8,19 @@ code: hw4
 
 assigned: Assigned October 18, 2023
 due: 
-   - Due on October 23, 2023
-   - Two day grace period, October 25, 2023
+   - Due on October 30, 2023
+   - Two day grace period, November 1, 2023
    
-revised: Sep 28, 2023
+revised: Oct 17, 2023
 
 ---
 * TOC
 {: toc}
 
 # Overview
-The goal of this homework is to learn about basics of website accessibility and how to assess. In part 1, you: Learn how to use automated tools (and their limitations); Learn how to address the limitations of automated tools using accessibility tools; In part 2, you: Learn how to write up an assessment and prioritize what problems to fix; Practice identifying paths to fixing problems. You will also have the opportunity to practice UI image description. 
+The goal of this homework is to learn how to report your UARs and present them in an actionable form a stakeholder.
+ In Assignment 3, you: learned how to use automated tools (and learned their limitations); and learned how to address the limitations of automated tools using accessibility tools. 
+ In this assignment, you will: Learn how to write up an assessment and prioritize what problems to fix; Practice identifying paths to fixing problems. You will also have the opportunity to practice UI image description. 
 
 Please note that *plain language* is *not* required (or expected) for this assignment. 
 
@@ -30,11 +32,13 @@ This homework may contribute to your competency grade on
 - Your participation grade, as a percentage of completeness (are all the required parts present)
 
 ## Length & Difficulty
-Students in the past have reported that taken together, part 1 and part 2 of this assignment require a median of 20 hours (mode=6). A challenge that multiple students faced is summarizing the WCAG guidelines in their own words. Please be sure to do so, *or* to quote and reference WCAG guidelines according to our [course policy on academic conduct]({{site.baseurl}}/academic-conduct.html). Some things that students have told us about this assignment:
+Students in the past have reported that taken together, Assignment 3 and Assignment 4 require a median of 20 hours (mode=6). A challenge that multiple students faced is summarizing the WCAG guidelines in their own words. Please be sure to do so, *or* to quote and reference WCAG guidelines according to our [course policy on academic conduct]({{site.baseurl}}/academic-conduct.html). Some things that students have told us about this assignment:
 - It helps to use the [UAR template](webegs/UAR_Template.doc) when filling out the UARS.
 - It was very motivating to do this for a real client
 
 # Details 
+For this assignment, you will be given the option to work in a group of up to 4 students who evaluated the same website as you in Assignment 3. However, you are welcome to opt to complete this assignment individually if preferred. There will be time in Section on 10/19 to collaborate with groupmates if desired.
+
 For your report please do the following. To help you understand these requirements, here are is an example prior year's report that is a [good example](webegs/DigitalDefense.docx) of what you are aiming for (note that small details of requirements may have changed from year to year). Your report should be about 8 pages long, single spaced, with 12 point font. Your report should be accessible (including proper use of headings, ALT text, table markup and so on). If you directly quote anything when describing the issue (for example) include a footnote linking to your source, and put it in quotes.
 
 ## 1. Introduce what you did
@@ -49,7 +53,7 @@ Introduce the site or app, its purpose, and the task you assessed and state whic
 
 Write an executive summary highlighting the biggest (most frequent, severe) problems, and your recommendations for fixing them. Keep this  to 1-2 paragraphs.
 
-You should also fill in the following overview table and put it in this section
+You should also fill in the following overview table and put it in this section:
 
 | WCAG # | # Severe problems | # Moderate problems | Minor problems |
 |:-------|:------------------|:--------------------|:---------------|
@@ -58,9 +62,9 @@ You should also fill in the following overview table and put it in this section
 
 ## 3. Provide details on what needs to be done to fix the site or app
 
-The remainder of your report should provide an overview, and detail, on the problems found, grouped by WCAG #. This is a good section of the report to divide and conquer in your group.
+The remainder of your report should provide an overview, and detail, on the problems found, grouped by WCAG #. This is a good section of the report to divide and conquer if working in a group.
 
-For each WCAG # 
+For each WCAG #: 
 - summarize the issue of concern 
 - summarize the UAR(s) found if any
 - give an example of a typical case