Accessibility Checklist

The checklist is from Shift Nudge, series of online learning courses. Workshop: Designing Beautiful Interfaces

Layout

Have you used standardized controls and components in a very intentional way?
If you haven't used standardized controls, do you have a very good reason? And have you talked to your developer about implementing it in an accessible way? (Example, auto-suggest lists have a specific way of being implemented to be screen-reader friendly)
Can a user visually navigate a page in a logical way?
Is there a clear page title that states the purpose of the page?
Do the headers accurately convey the structure of information?
Does the visual order match the reading order? (Left to right, top to bottom)
Do the interface elements have appropriate labels? (Inputs, checkboxes, radio buttons, etc.)
Do the clickable actions have clear action-oriented labels? (Download, Sign Up, Log Out, etc.
Developer - Don't put status text or other non-interactive elements into the tab order
Developer - Are you using the <a> and <button> tags appropriately? (They can both be triggered by Enter, whereas the <button> element can additionally be triggered with the Spacebar)
Developer - Can a screen reader scan your project's interface? (A screen reader will announce headers, specific areas, links, buttons, and controls along the way)
Developer - Do keyboard controls provide a logical and predictable order for navigation