Website/App Group Report
- Due Oct 28, 2024 by 10pm
- Points 0
- Submitting a text entry box or a file upload
Rubric
Keep in mind that 48 students have already been assessed using this rubric. Changing it will affect their evaluations.
Criteria | Ratings | Pts | ||||
---|---|---|---|---|---|---|
This criterion is linked to a Learning Outcome
24au Accessible Documents
This applies to presentations, word documents, and pdfs. You’ll need to demonstrate this on at least one presentation and one assignment writeup that is long and complex enough to have headers and structure to achieve competency. Best practices:
Avoid visual clutter (e.g. use San serif fonts (for digital viewing), don’t have too many things on the page)
Use headers appropriately. Headers should be nested like they are in HTML (e.g., H2 after and H1). For example, in Microsoft Word these are built-in “styles” and in Google Docs you can see these under “Format -> Paragraph Styles.”
Use proper color contrast.
Write alt text for all non-decorative photos, diagrams and videos.
Use meaningful hyperlink text (e.g., "check out my web page" instead of "click here")
Properly mark up tables
Screen reader order is correct (in documents where it applies, such as Powerpoint) \
Slides have room for captions
Videos on slides are captioned
Document/slide is not overly cluttered
Font sizes are large enough (above 20 ideally for slides; above 11 for documents)
How to demonstrate this competency: You will be assessed on this any time you turn in a required document.
threshold:
3.0 pts
|
|
pts
--
|
||||
This criterion is linked to a Learning Outcome
24au Accessibility Rules
Accessibility problem reports are assessed by looking at UARS. A high quality UAR should
Clearly describe the problem or success
Correctly assigned 1 or more WCAG guidelines to the problem or success
Provide a good rationale for the severity of the problem / importance of the success
(If a problem) Articulate an actionable path for addressing the problem found
In addition, UARS form a group that together represent an assesssment. As such, they should
Reflect the most important potential issues with the system being assessed
Include web page or app accessibility problems that are not found with an automated accessibility checker
Address at least two of the four areas of POUR (perceivable; operable; understandable; robust).
If there are no problems, or problems in only one area, positive UARs without fixes are permitted (with approval of the course staff).
How this will be assessed: You should turn in a reflection stating what app or website you were assessing, which tasks you were assessing, and which AT and/or automated tools you used to generate the UARS.
threshold:
3.0 pts
|
|
pts
--
|
||||
Completion
threshold:
pts
|
|
pts
--
|
||||
Total Points:
11
out of 11
|