The fourth week

1. The fourth week
2. Here's what we're going today
3. Would you like to participate in a test? We have been asked to use this site and fill out this survey.
4. OCAS is a great case study in requirements
5. Let`s see what some people missed... ...last week
6. Dark Patterns Dark patterns are design patterns that are meant to manipulate the user. Dark patterns are not bad design - they are good design for bad reasons.
7. Psychological Insight Applied Honestly (benefits users) Applied Deceptively (benefits business) “We don’t read pages. We scan them” —Steve Krug Aid rapid comprehension: ensure key content is shown in headings, subheadings (etc), using a strong visual hierarchy. Hide key information: Bury facts within paragraphs of text, so some users will proceed without fully understanding the transaction. “People tend to stick to the defaults” —Jakob Nielsen Prevent mistakes: Default to the option that’s safest for the user. In important contexts, don’t use defaults and require the user to make an explicit choice. Benefit from mistakes: Ensure default options benefit the business, even if this means some users convert without meaning to. “People will do things that they see other people are doing” —Robert Cialdini Show unedited feedback: Allow real customers to share their experiences, so they can make accurate pre-purchase evaluations. Bury negative feedback: Hand-pick positive feedback and display it prominently. Bury negative feedback so it is hard to find. https://alistapart.com/article/dark-patterns-deception-vs.-honesty-in-ui-design
8. Amorality Dark patterns test really well. Dark patterns could be in legacy code, they could be given to you to develop, or they could even come from you.
9. Hooray for linting! Clone https://github.com/simonborer/a11y-linting
10. We will be looking at both an html linter (htmllint) and a command line auditing tool (lighthouse).
11. HTMLLint Open the project in your text editor Look at package.json under "dependencies" and "devDependencies" Open your command line client Go to the project folder Run npm install
12. Look at package.json under "scripts" - this is where we define the node scripts the will get called by npm run npm run build htmllint options are defined in .htmllintrc - try getting rid of one of the tag bans to clear an error Now try fixing the html to clear the rest Tell me why we put htmllint under the "build" script
13. Lighthouse CLI Look at package.json under "scripts", at the "audit" script. Read me this script in non-technical terms. Run npm run audit and view the output file.
14. Exercise: an accessible accordion Build an accessible accordion and submit it as a pull request. Feel free to pair-program.

The fourth week

Psychological Insight	Applied Honestly (benefits users)	Applied Deceptively (benefits business)
“We don’t read pages. We scan them” —Steve Krug	Aid rapid comprehension: ensure key content is shown in headings, subheadings (etc), using a strong visual hierarchy.	Hide key information: Bury facts within paragraphs of text, so some users will proceed without fully understanding the transaction.
“People tend to stick to the defaults” —Jakob Nielsen	Prevent mistakes: Default to the option that’s safest for the user. In important contexts, don’t use defaults and require the user to make an explicit choice.	Benefit from mistakes: Ensure default options benefit the business, even if this means some users convert without meaning to.
“People will do things that they see other people are doing” —Robert Cialdini	Show unedited feedback: Allow real customers to share their experiences, so they can make accurate pre-purchase evaluations.	Bury negative feedback: Hand-pick positive feedback and display it prominently. Bury negative feedback so it is hard to find.