small changes to website assignment

assignments/website.md

@@ -62,7 +62,10 @@ page to get the scanner working on your device. Another option is to install the
 For iOS, you should install the Accessibility Inspector, which is freely available through the App Store. More details on [testing for accessibility in iOS.](https://developer.apple.com/library/archive/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXTestingApps.html)
 
 ### Test it yourself
-Use a screen reader and switch input to assess the website and/or app, and your ability to complete the assigned task using accessibility tools. You may also use other accessibility tools if you feel there are things that does not address.
+Use *multiple approaches*, including at a minimum  **a screen reader** and **switch input** to assess the website
+and/or app, and your ability to complete the assigned task using
+accessibility tools. You may also use other accessibility tools if you
+feel there are things that does not address.
 
 Here are some resources that may help you in gaining comfort with these accessibility technologies 
 - Switch control intro: [Switch Control overview](https://www.youtube.com/watch?v=GQKEE9nI1lk)
@@ -72,6 +75,7 @@ Here are some resources that may help you in gaining comfort with these accessib
 Short (1 page max) report for each group of similar issues you find using this [Usability Aspect Report Template](UAR_Template.doc)
 
 For example, consider this view of the the WebAIM automated accessibility checker. The red mountain with the X indicates that it is missing an image description. To write this up, you would record the
+- **Source** including *your initials*; *the type of AT used*; and a unique ID such as JM-SR-3 (which means, approximately, Jennifer Mankoff Screen Reader UAR # 3)
 - **Name** as "Missing Image ALT Text";
 - **Evidence** Guideline violated: 1.1 ([Text Alternatives](https://www.w3.org/WAI/WCAG22/Understanding/text-alternatives)); 
     - **Screen Shot** as the image and URL ([lib.washington.edu](https://www.lib.washington.edu/)); 
@@ -82,11 +86,12 @@ For example, consider this view of the the WebAIM automated accessibility checke
 - **Relationship to other problems** Since we only have one example UAR here we don't have much to say, but this could mention for example other areas of the website which are missing labels such as form entries or buttons. 
 
 # Turnin
-You will turn in your UARs on the problems you found **in one week** on the Ed discussion thread for your website (To be posted)
 
-In two weeks you will write up 5 page report documenting problems **that you and others found** on your website and suggesting solutions. Your report should be accessible (including proper use of headings, ALT text, table markup and so on) and have the following structure:
-- The first page should introduce the site or app, its purpose, and the task you assessed and state which tools you used in your assessment. 
-- The first page should also have an executive summary of the biggest (most frequent, severe) problems, and your recommendations for fixing them. Keep this brief, you will provide more detail in the following pages.
+(1) You will turn in your UARs on the problems you found **in one week** on  Ed, including images *with ALT text*
+
+(2) In two weeks you will write up 5 page report documenting problems **that you and others found** on your website and suggesting solutions. Your report should be accessible (including proper use of headings, ALT text, table markup and so on) and have the following structure:
+- The first page should introduce the site or app, its purpose, and the task you assessed and state which accessibility tools, both automated and manual, you and others used in your assessment. 
+- The first page should also have an executive summary of the biggest (most frequent, severe) problems, and your recommendations for fixing them. Keep this  to 1-2 paragraphs, you will provide more detail in the following pages.
 - The next section of the report should provide an overview, and detail, on the problems found. 
 	- You should start with an overview table that looks something like this. 
 
@@ -96,14 +101,17 @@ In two weeks you will write up 5 page report documenting problems **that you and
 |:-------|:------------------|:--------------------|:---------------|
 
 - Next, there should be a subsection for each WCAG # 
-	- summarize the issue (s) found if any
+    - summarize the issue of concern 
+	- summarize the UAR(s) found if any
 	- give an example of a typical case
 	- provide details if there are any special cases
 	- list (briefly) all the other places it happens
-- Finally discuss the remedy that is needed
+    - Finally discuss the remedy that is needed
 
 If you directly quote anything when describing the issue (for example) include a footnote linking to your source, and put it in quotes.
 
+(3) You should also turn in a separate document with all of the UARS used in your report (both yours and those of any students who looked at the same website). Clearly label which are yours when you do this. 
+
 ## Accessibility of Deliverable
 We expect your submission to be a Word or Google Doc. We ask that you do four things to make the deliverable accessible:
 - Use headers. In Microsoft Word these are built-in "styles" and in Google Docs you can see these under "Format -> Paragraph Styles." Headers should be nested like they ar in HTML (e.g., H2 after and H1). Read [this for more guidance in how to do styles in Word.](https://support.microsoft.com/en-us/office/make-your-word-documents-accessible-to-people-with-disabilities-d9bf3683-87ac-47ea-b91a-78dcacb3c66d#bkmk_builtinheadings_win)