evaluation.pdf - sample evaluation (deliberately incomplete). Some points in reflection of this sample:
• Not all refinements and recommendations will be made against criteria - that's great.
• Some criteria may only have anecdotal data with which to justify - that's OK.
• This is not a prescribed methodology for evaluating, nor is it offered as the best solution. Your evaluation may be structured differently - that's good.
The key is to make refinements and recommendations justified by data:
The remainder of this webpage details methods to attain data (aka 'testing') for justification:
Heat Map Datatemplates\template.html
Speed Throttling (Chrome Developer Tools)
Check the markup of your HTML templates with the W3C Markup Validation Service.
Measure conformance standard against the Consistent User Experience Standard (Queensland Goverment). The latest version contains modules with the requirements listed as 'checkpoints'. The conformance categories are listed as mandatory, desirable or optional:
Toggle Device (Chrome Developer Tools)
More ideas for testing include anything that can determine results for:
Testing is an ongoing process throughout the development (e.g. responding to errors), refinements (e.g. improving the UX) or recommendations (e.g. future directions):