Why Design QA should not be an afterthought

Why Design QA should not be an afterthought

Practical notes

1 min read

Why Design QA should not be an afterthought

Compare typography, spacing, images and states as components are implemented. Test mobile and long English copy separately before release.

Why Design QA should not be an afterthought

Putting visual design and experience into practice

Visual hierarchy should match information priority. Typography, imagery and spacing determine what visitors notice first and how they understand the next information.

Why Design QA should not be an afterthought

Checking the result

Compare home and detail pages at the same scale, including long headings, real imagery and mobile order. Connect observations to concrete areas and tasks.

Why Design QA should not be an afterthought
Why Design QA should not be an afterthought
Why Design QA should not be an afterthought

Why Design QA should not be an afterthought · Working details

Contact OXOAK