The following checklist items are designed to support the review of a user interface on a page-by-page basis.
Can you describe what the page is supposed to accomplish in one sentence?
Does the page provide sufficient information and/or controllers to accomplish the goal?
The organization of information on the page utilizes the “screen real estate” in an appropriate manner at both desktop and mobile sizes.
To check mobile size, there is device mode in Chrome Developer Tools to simulate various screen sizes.
There should be no “easter eggs”, i.e. things you have to hover over to see that they are interactive.
Form controllers should be annotated or documented with appropriate sample values.
When asking for information, consider if some explanation of why the information is being requested should be provided.
Pages for “normal users” should load in less than 3 seconds. It is acceptable for admin users to wait longer under certain circumstances.
When loading and/or interacting with the page with Chrome Developer Tools open, no errors should be generated.