The Sixth week

Final rubric
Criteria	Presentation	Written
Speaking to the goals	5	10
Talking about the methods	5	10
Walking through the results	10	5
Strong conclusions	5	10
Reasonable recommendations	10	5
Documentation	N/A	20
Responding to questions	10	N/A
Total	40%	60%

Usability	UAT
Meant to determine whether users can learn, understand and use the product efficiently to achieve theirgoals.	Meant to determine whether the client is satisfied that the product meets their requirements.
Can happen before or during development, before or after launch.	Happens after development, but before launch.
Tests whether users can achieve the result they want.	Tests whether the product produces the expected result.
Meant to generate continuous improvements.	Meant to achieve final sign-off.
Run by the software team.	Run by the client.

1. The Sixth week
2. Here's what we're going today
3. Please mark your attendance down.
4. Your final Your final project is a usability study, presented during the final lab. Your presentation should run 5-8 minutes. You will be required to present the findings of your test in person. A slide presentation is acceptable, as is a longform document. Either way though, your report needs to present what you did, why you did it, what the results are, and what your recommendations are based on those results. You must also include all the data that backs up your conclusions (although you don't necessarily need to talk through every single data point, as that would be pretty boring).
5. Final rubric Criteria Presentation Written Speaking to the goals 5 10 Talking about the methods 5 10 Walking through the results 10 5 Strong conclusions 5 10 Reasonable recommendations 10 5 Documentation N/A 20 Responding to questions 10 N/A Total 40% 60%
6. 11:30 At 11:30 today we'll be helping to test the usability of the Humber Career Outlooks web app. Approach it as a participant, but while you're taking part, reflect on their methodology. We'll get to talk about what we thought about their testing in the lab. Would you have taken the same approach? Does this change how you'll interact with your test participants?
7. Unpaid internships https://www.labour.gov.on.ca/english/es/pubs/internships.php The Ministry of Labour is committed to ensuring fairness and protecting young workers. The fact that you are called an “intern” does not determine whether or not you are entitled to the protections of the Employment Standards Act, 2000 (ESA), including the minimum wage....The ESA does not apply to an individual who performs work under a program approved by a college of applied arts and technology or a university....If someone performing work as an unpaid intern is unsure of whether he or she is excluded from the ESA, he or she should call the Employment Standards Information Centre toll-free at 1-800-531-5551 for further information.
8. Reading without peeking How was it using a screenreader?
9. Where are you at? How do you feel about the testing so far? Are you confident that you'll be able to draw meaningful conclusions about the data? Did anything surprise you? What would you like to change going forward? What's difficult? What's easy? What's fun? What's not?
10. Differentiating UAT & Usability testing UAT and usability testing are both kinds of testing. As are regression testing, unit testing and integration testing. Tests have plans, requirements and scenarios.
11. UsabilityUATMeant to determine whether users can learn, understand and use the product efficiently to achieve theirgoals.Meant to determine whether the client is satisfied that the product meets their requirements.Can happen before or during development, before or after launch.Happens after development, but before launch. Tests whether users can achieve the result they want.Tests whether the product produces the expected result. Meant to generate continuous improvements.Meant to achieve final sign-off. Run by the software team.Run by the client.
12. OH NO POP QUIZ Please go to the quiz
13. Mobile accessibility The WCAG has multiple documents on how accessibility standards translate to mobile. It's mostly along the lines of 'don't try to cram your whole desktop site onto mobile', and 'just make sure that you're doing what you do on desktop', but with a few extra cautions.
14. Take special pains to test resizing up to 200%. You definitely still have to have keyboard-only controls Touch targets are at least 9mm x 9mm, with adequate space between them (without magnification) Use mouseup or touchend events so that users can change their minds
15. Gestures should be kept simple, and have alternatives Support either orientation Put important elements above the fold Provide easily discoverable instructions Set the keyboard to the type of data entry required No scrolljacking Show focus
16. Accessible content - page titles Page title should be unique and descriptive. If it's page 2 of 3, say so.
17. Accessible content - headings Headings should structure your document. Think of the way your information is structured - it's very rarely appropriate to have just an h1 and then p tags all the way down. Headings should provide meaning and context.
18. Accessible content - alt text Alternative text should be your best effort to convey all of the relevant information in the image - no more, no less. This gets tricky when you get into things like graphs. Think of how WebAIM approached it in our reading this week.
19. Accessible content - transcripts and captions Audio and video need transcriptions and/or captions. Keep an ear out for sounds that convey relevant information, and make sure they're included - not just the words.
20. Accessible content - form labels, instructions and errors Be very clear about what's expected of a user, and how errors should be resolved. A red asterisk appearing suddenly adjacent to an input isn't helpful to everyone.
21. Accessible content - beware things that look like text Be on the lookout for images with embedded text, or worse - OCR-resistant PDFs.
22. Accessible content - ASCII Think about what this sounds like: ¯\_(ツ)_/¯. For the same reason, write "16 to 17 years old" instead of "16-17 years old".
23. Accessible content - links Via sitepoint Don't say they're links - the screenreader tells you Don't capitalize - screenreaders will read them out letter by letter Don't make the link text the url Keep links short - screenreaders won't skip them. Identify link behaviour - i.e. downloads, new windows, anchor links Don't embed link types identifications in your CSS Don't abuse javascript to do link-ish things with elements that aren't links (anchors or area tags) If an image is inside an anchor tag, it's alt text should refer to the link behaviour, as well as the image's information. Empty or broken links are just mean.

The Sixth week