Accessibility Quadrants for Browserstack <break> Point

I've just recorded a session on Riverside for BrowserStack's conference Breakpoint. Had a wonderful host in Jenna Charlton and shared my Accessibility Quadrants visual heuristic. 

The quality might not be the best, so I'm writing them out too, rather than adding alt-text. They are written as team rules or as entries in definitions of ready or done. 

Readability
No all capitals in menus or headings 
Multistep flows will show what step the user is on, e.g. 1 of 4 
The Plain English Guide will be used 
If acronyms are used, they will be explained 
The site can be used and read when zoomed to 200 and 400% 

Inclusive language
Information capture will have title and gender optional 
For clients who insist on pronoun capture, and 'other' text field will be provided 
All text will be gender neutral 

User experience 
Designs will include a keyboard flow order 
Mobile first design will be used to ensure it works on screens of all sizes 
Keyboard and screen reader testing will be included in each sprint 

Compliance 
One person on each team will become familiar with the legislation and share knowledge with the wider team 
Bi-annual VPATs (Voluntary Product Assessment Template report) will be commissioned from an external provider 
The team will use WebAIMs WCAG 2 checklist as a reference