@@ -75,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
-**Good or Bad Feature***If your website as very accessible* you may include UARS for particularly good features
-**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)
@@ -87,10 +88,18 @@ For example, consider this view of the the WebAIM automated accessibility checke
# Turnin
(1) You will turn in your UARs on the problems you found **in one week** on Ed, including images *with ALT text*
(1) You will turn in your UARs on the problems you found **in one week** on Ed, including images *with ALT text*. Be sure to include at least on UAR from a switch, screen reader and automated tool. If your website is *very* accessible you may include a "good UAR" highlighting someting good you found, to demonstrate that you tested with a variety of tools.
(2) In two weeks you will write up 5 page report documenting problems **that you and others found** on your website and suggesting solutions. Here are is an example prior year's report that is a [good example](example-webaccess-report.docx) of what you are aiming for (note that small details of requirements may have changed from year to year).
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. It should include an overview table that looks something like this.
| Task | Type (Web/Mobile/etc) | Testing Method | # UARS found | Who Contributed |
(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.
