is-aesthetic

All checks

Code order matches the screen

Inclusion and adaptation · essential check · measured from the page’s layout and styles · C168.1

Blocks should come in the same order in the markup as they appear on screen.

When it fails
The order on screen differs from the order in the code: order differs within instructions, or at least three blocks are reordered in one region
Warns when
One or two reordered blocks outside sequential content
Passes when
Visual and DOM reading order agree within content regions
How to fix it
Reorder the markup to match the layout instead of moving blocks with order, row-reverse or grid placement. This matters most in steps and instructions.

On the public reports

fails on 4warns on 1passes on 2of 7 sites

is-aesthetic.com1026 reordered blocks · scores 72
  • Flagged element on is-aesthetic.com at 1440 px1440 px
  • Flagged element on is-aesthetic.com at 390 px390 px
  • Flagged element on is-aesthetic.com at 390 px390 px
www.python.org61 reordered blocks · scores 71

No element pictures were kept for this result.

vercel.com12 reordered blocks · scores 73

No element pictures were kept for this result.

www.benchflow.ai30 reordered blocks · scores 50

No element pictures were kept for this result.

www.wikipedia.org2 reordered blocks · scores 79
  • Flagged element on www.wikipedia.org at 390 px390 px
  • Flagged element on www.wikipedia.org at 390 px390 px

Passes on figma.com and www.gov.uk.

Public reports are the sites listed on the home page, each as last scanned. Pasted pages are never included.