Desktop
Use space intentionally, avoid excessive line length, preserve hierarchy and ensure high-density layouts remain readable.
Tablet
Check grid collapse, navigation behavior, touch targets, sticky elements and horizontal overflow.
Mobile
Prioritize the next action, readable type, accessible controls, compact menus and fast-loading media.
Keyboard
Interactive controls should be reachable and operable without a mouse.
Focus
Users need visible focus states and predictable navigation order.
Contrast
Text and controls must remain readable across backgrounds and states.
Meaning
Labels, alt text, headings and errors should communicate purpose clearly.
Images & media
Use appropriately sized assets, responsive images, lazy loading where useful and avoid massive decorative media above the fold.
JavaScript
Do not ship large frameworks or motion libraries just to create effects CSS can handle more cheaply.
Fonts
Limit families/weights, preload critical assets deliberately and avoid blocking page rendering unnecessarily.
Caching
Public content, static assets and repeatable responses should use sensible cache behavior and invalidation.
Third-party scripts
Analytics, chat, ads and widgets should justify their cost on page performance.
Critical path
The first meaningful view and primary action should not wait on non-essential functionality.
Message clarity
Can a qualified visitor understand what you build and for whom within seconds?
Proof
Do claims link to real products, screenshots, methodology, technical depth or case studies?
Next action
Does every important page offer a logical next step—learn, inspect, diagnose, plan or contact?
Trust
Are limitations, location, security posture and case-study status communicated honestly?
Friction
Are forms asking only for information needed at that stage?
Follow-through
Do successful submissions, downloads and actions provide clear confirmation and next steps?
Submission integrity
Confirm actual server delivery, visible success/error states, spam handling and the correct destination—not just that the button animates.
Validation
Errors should explain what needs fixing, preserve entered data and focus attention on the failed field.
Analytics
Track meaningful events such as qualified project starts and successful enquiries, not vanity clicks everywhere.
Privacy
Collect only the information needed and explain how submissions are used.
Crawl
Robots, sitemap, status codes and internal links.
Index
Canonical, noindex, duplication and page usefulness.
Understand
Semantic headings, entity clarity, structured answers and schema where appropriate.
Believe
Evidence, sources, real media, case studies and consistent claims.
Acquisition
Know where qualified visitors are coming from, not just total traffic.
Engagement
Track whether users inspect work, use Labs, start the planner and reach meaningful sections.
Conversion
Measure successful project starts and enquiries with duplicate tracking avoided.
Want this QA standard applied to your website or web app?
Astackra can redesign, rebuild or audit the experience from product UX through WordPress, performance, forms, search and analytics.
Related