heydon / inclusive-design-checklist Goto Github PK

Why?

I know it is ironic, but the name of the checklist implies that it is about all design, where you are really just talking about web-site (and perhaps app) design, and excluding everything else. For example, compare the scope of this list to The Design of Everyday Things.

That limited scope should be reflected in the title.

Authors should consider using common security headers to mitigate the evil of the web and to take control of application behavior.

• Content-Security-Policy (probably the biggest win)
• Cross-Origin-Resource-Policy
• Expect-CT
• Feature-Policy
• Referrer-Policy
• Strict-Transport-Security
• X-Content-Type-Options
• X-Frame-Options
• X-Powered-By
• X-XSS-Protection

Not sure if you have mentioned 'using srcsets over css for different mobile desktop images'. Apologies if you have.

Thoughts on this typography article by NNG, which is somewhat contradictory to "avoid all caps":
https://www.nngroup.com/articles/glanceable-fonts/

An acceptable exception?

I’ve pulled this discussion here to keep things focused.

We discussed as part of the generator that converts “checklist.json” into “README.md” that we should make a pre-commit hook that would automatically run the generator for us. (See #1 & #22)

The script

I’ve already put a little idea together for the script, which I’ve already pasted into #1. Here it is for reference:

#!/bin/sh
# Check if this is the initial commit
if git rev-parse --verify HEAD >/dev/null 2>&1
then
node generator/index.js
git add README.md
exit 0
else 
exit 0

I guess we need to think of a solution that doesn’t over complicate things for a potential contributor.

@peter-mouland has already kicked the ideas off in #1 by suggesting husky

Specifically what bad practices does this address? Or what problems for accessibility should we be trying to avoid here?