is-aesthetic.com

Scanned 24 Oct 2026, 05:06 UTC · 3 pages scanned · 1440, 390 and 320 px · 55 s

Visit site Markdown JSON

71.9 /100

Grade C

4 fail1 warning11 pass11 not evaluatedof 27 checks

Failing checks (4)

Measured results, suggested fixes, and the evidence saved for each check.

Failing check · Visual communication · C014.1

Repeated items, such as cards or list rows, don’t match

10 px largest difference

Cards, buttons and list rows of one kind should share padding, radius, borders, shadow and type.

Passes when: Matching component variants differ by at most 1 px
Fails when: A difference exceeds 4 px, or a compared style attribute differs

How to fix it

Build each repeated element from one component or class and remove one-off overrides, so padding, radius, border, shadow and type match within 1 px.

Saved evidence 3 element records

Element 1/methodology · 1440 px viewport

No image saved

html > body > main > div > article > section:nth-of-type(4) > div:nth-of-type(1) > ul > li:nth-of-type(1)

Element 760 × 79 px · x 452, y 2143

Repeated component comparison

Element 2/methodology · 1440 px viewport

No image saved

html > body > main > div > article > section:nth-of-type(4) > div:nth-of-type(1) > ul > li:nth-of-type(2)

Element 760 × 79 px · x 452, y 2222

Repeated component comparison

Element 3/methodology · 1440 px viewport

No image saved

html > body > main > div > article > section:nth-of-type(4) > div:nth-of-type(1) > ul > li:nth-of-type(3)

Element 760 × 79 px · x 452, y 2302

Repeated component comparison

Failing check · Visual communication · C019.1

Text or controls overlap

On /methodology

23 confirmed overlapping pairs

Text and controls must not cover each other at desktop or phone widths.

Passes when: No confirmed occlusion of painted text or a visible control
Fails when: A painted box covers text or a control by at least 4 px on both axes and 10% of the smaller painted box

How to fix it

Find what covers what at the width shown, then give the layout room: let text wrap, drop fixed heights and negative margins, or stack the items below a breakpoint.

Saved evidence 3 element records

Element 1/methodology · 320 px viewport

html > body > main > div > div > details > nav > ol > li:nth-of-type(1) > a

Element 280 × 40 px · x 20, y 153

html > body > main > div > div > details > nav > ol > li:nth-of-type(1) > a is covered by html > body > main > div > article > header > p:nth-of-type(1) over 62.5% of the smaller painted box

Element 2/methodology · 320 px viewport

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a

Element 127 × 19 px · x 20, y 203

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a is covered by html > body > main > div > article > header > h1 over 35.9% of the smaller painted box

Element 3/methodology · 320 px viewport

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a

Element 280 × 40 px · x 20, y 193

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a is covered by html > body > main > div > article > header > p:nth-of-type(1) over 37.5% of the smaller painted box

On /docs

9 confirmed overlapping pairs

Text and controls must not cover each other at desktop or phone widths.

Passes when: No confirmed occlusion of painted text or a visible control
Fails when: A painted box covers text or a control by at least 4 px on both axes and 10% of the smaller painted box

How to fix it

Find what covers what at the width shown, then give the layout room: let text wrap, drop fixed heights and negative margins, or stack the items below a breakpoint.

Saved evidence 3 element records

Element 1/docs · 320 px viewport

html > body > main > div > div > details > nav > ol > li:nth-of-type(1) > a

Element 280 × 40 px · x 20, y 153

html > body > main > div > div > details > nav > ol > li:nth-of-type(1) > a is covered by html > body > main > div > article > header > p:nth-of-type(1) over 62.5% of the smaller painted box

Element 2/docs · 320 px viewport

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a

Element 94 × 19 px · x 20, y 203

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a is covered by html > body > main > div > article > header > h1 over 35.9% of the smaller painted box

Element 3/docs · 320 px viewport

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a

Element 280 × 40 px · x 20, y 193

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a is covered by html > body > main > div > article > header > p:nth-of-type(1) over 37.5% of the smaller painted box

Failing check · Inclusion · C160.2

A control’s name leaves out the words shown on it

On /

12 names missing their visible label

A control's accessible name should contain the words people see on it.

Passes when: A control’s accessible name contains its visible label
Fails when: A control’s accessible name omits its visible label

How to fix it

Start the aria-label with the visible text, or remove the aria-label so the visible text becomes the name. Voice-control users say what they see.

Saved evidence 3 element records

Element 1/ · 1440 px viewport

html > body > main > section:nth-of-type(2) > div > ol > li:nth-of-type(1) > a

Element 1120 × 56 px · x 160, y 589

Element 2/ · 1440 px viewport

html > body > main > section:nth-of-type(2) > div > ol > li:nth-of-type(2) > a

Element 1120 × 56 px · x 160, y 645

Element 3/ · 1440 px viewport

html > body > main > section:nth-of-type(2) > div > ol > li:nth-of-type(3) > a

Element 1120 × 56 px · x 160, y 701

On /docs

8 names missing their visible label

A control's accessible name should contain the words people see on it.

Passes when: A control’s accessible name contains its visible label
Fails when: A control’s accessible name omits its visible label

How to fix it

Start the aria-label with the visible text, or remove the aria-label so the visible text becomes the name. Voice-control users say what they see.

Saved evidence 3 element records

Element 1/docs · 1440 px viewport

html > body > main > div > article > section:nth-of-type(2) > pre

Element 760 × 58 px · x 452, y 1056

Element 2/docs · 1440 px viewport

html > body > main > div > article > section:nth-of-type(3) > pre

Element 760 × 102 px · x 452, y 1674

Element 3/docs · 1440 px viewport

html > body > main > div > article > section:nth-of-type(4) > pre

Element 760 × 655 px · x 452, y 1934

Failing check · Inclusion · C168.1

The order on screen differs from the order in the code

On /methodology

1026 reordered blocks

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

Passes when: Visual and DOM reading order agree within content regions
Fails when: Order differs within instructions, or at least three blocks are reordered in one region

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.

Saved evidence 3 element records

Element 2/methodology · 1440 px viewport

html > body > main > div > article > section:nth-of-type(4) > div:nth-of-type(1) > ul > li:nth-of-type(1) > details > div > p

Element 654 × 50 px · x 558, y 2221

DOM rank differs from visual rank

Element 1/methodology · 1440 px viewport

No image saved

html > body > main > div > article > section:nth-of-type(4) > div:nth-of-type(1) > ul > li:nth-of-type(2) > details > summary > span:nth-of-type(1)

Element 92 × 26 px · x 452, y 2236

DOM rank differs from visual rank

Element 3/methodology · 1440 px viewport

No image saved

html > body > main > div > article > section:nth-of-type(4) > div:nth-of-type(1) > ul > li:nth-of-type(2) > details > summary > span:nth-of-type(2)

Element 622 × 26 px · x 558, y 2236

DOM rank differs from visual rank

On /docs

10 reordered blocks

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

Passes when: Visual and DOM reading order agree within content regions
Fails when: Order differs within instructions, or at least three blocks are reordered in one region

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.

Saved evidence 3 element records

Element 1/docs · 390 px viewport

html > body > main > div > article > header > p:nth-of-type(1)

Element 350 × 19 px · x 20, y 182

DOM rank differs from visual rank

Element 2/docs · 390 px viewport

html > body > main > div > div > details > nav > ol > li:nth-of-type(2) > a

Element 350 × 40 px · x 20, y 193

DOM rank differs from visual rank

Element 3/docs · 390 px viewport

html > body > main > div > article > header > h1

Element 350 × 132 px · x 20, y 215

DOM rank differs from visual rank

Warnings (1)

Warning · Inclusion · C167.1

Text styled as a heading isn’t marked up as one

3 headings without heading markup

Text styled as a section heading should be marked up as one, h1 to h6.

Passes when: Section-heading appearance is supported by heading semantics
Warns when: A possible heading needs semantic review

How to fix it

Change the element to the right heading level (h2, h3 …) and keep its look with a class. Screen-reader users move through a page by its headings.

Saved evidence 3 element records

Element 1/methodology · 1440 px viewport

No image saved

html > body > main > div > article > section:nth-of-type(5) > div > div:nth-of-type(1) > p:nth-of-type(1)

Element 202 × 46 px · x 473, y 4911

Element 2/methodology · 1440 px viewport

No image saved

html > body > main > div > article > section:nth-of-type(5) > div > div:nth-of-type(2) > p:nth-of-type(1)

Element 202 × 46 px · x 731, y 4911

Element 3/methodology · 1440 px viewport

No image saved

html > body > main > div > article > section:nth-of-type(5) > div > div:nth-of-type(3) > p:nth-of-type(1)

Element 202 × 46 px · x 989, y 4911

Passed (11)Show

Not evaluated (11)Show

The other 506 rules of the source taxonomy aren’t part of today’s scan. See the methodology.

Score by domain

Visual communication2 of 2 checks to fix0 /100

Information and findability4 checks, all pass100 /100

Functional and interaction support1 check, all pass100 /100

Inclusion and adaptation3 of 9 checks to fix72 /100

Visual expressionNot measured—

Transparency and agencyNot measured—

Essential: 71.9 of 100 points, 16 checks · Recommended: none applied · Bonus: none applied

What this doesn’t cover

Aesthetic judgment, brand intent and designer calibration
Text contrast is not measured yet (the vetted contrast rules are not implemented in this pin)
Briefs, specifications, logins and declared design systems
Form submissions, transactions and activated task flows
Closed shadow roots, cross-origin frame contents and other themes
Rules without a vetted implementation or required measurement
Pages or assets refused by robots.txt or the scan limits

How scores are computed: methodology. Is this your site? Ask us to remove this report.