www.python.org

Scanned 24 Oct 2026, 04:55 UTC · 2 pages scanned · 1440, 390 and 320 px · 1 min 3 s

1 additional page not scanned

Not scanned (time limit): https://www.python.org/jobs/

Visit site Markdown JSON

70.6 /100

Grade C

4 fail2 warnings11 pass10 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

105 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/ · 1440 px viewport

No image saved

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

Element 524 × 39 px · x 164, y 1040

Repeated component comparison

Element 2/ · 1440 px viewport

No image saved

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

Element 524 × 39 px · x 164, y 1079

Repeated component comparison

Element 3/ · 1440 px viewport

No image saved

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

Element 524 × 39 px · x 164, y 1117

Repeated component comparison

Failing check · Visual communication · C019.1

Text or controls overlap

On /

1 confirmed overlapping pair

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 2 element records

Element 1/ · 390 px viewport

No image saved

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(4) > div:nth-of-type(1) > div > div > table > tbody > tr > td > p > a

Element 279 × 39 px · x 32, y 2876

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(4) > div:nth-of-type(1) > div > div > table > tbody > tr > td > p > a is covered by html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(4) > div:nth-of-type(1) > div > div > table > tbody > tr > td > p > em over 100% of the smaller painted box

Element 1/ · 320 px viewport

No image saved

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(4) > div:nth-of-type(1) > div > div > table > tbody > tr > td > p > a

Element 248 × 39 px · x 32, y 3118

On /psf-landing/

2 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/psf-landing/ · 390 px viewport

No image saved

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(2) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > p > a:nth-of-type(3)

Element 225 × 44 px · x 86, y 1456

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(2) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > p > a:nth-of-type(3) is covered by html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(2) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > p > a:nth-of-type(2) over 96.3% of the smaller painted box

Element 1/psf-landing/ · 320 px viewport

No image saved

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(2) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > p > a:nth-of-type(2)

Element 155 × 44 px · x 85, y 1470

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(2) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > p > a:nth-of-type(2) is covered by html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(2) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > p > a:nth-of-type(1) over 94.7% of the smaller painted box

Element 2/psf-landing/ · 320 px viewport

No image saved

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(2) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > p > a:nth-of-type(2)

Element 155 × 44 px · x 85, y 1470

Failing check · Findability · C078.3

Links with the same text lead to different places

On /psf-landing/

4 link texts with two destinations

Links with the same text should lead to the same address.

Passes when: No identical link label points to conflicting destinations
Fails when: At least three conflicting link-label groups

How to fix it

Give links to different places different words ("Team pricing", "Enterprise pricing"), or point links that share their text at one destination.

Saved evidence 3 element records

Element 1/psf-landing/ · 1440 px viewport

html > body > div > div:nth-of-type(2) > nav > ul > li:nth-of-type(3) > a

Element 198 × 42 px · x 521, y 3

Conflicting link name/destination group

Element 2/psf-landing/ · 1440 px viewport

html > body > div > header > div > div:nth-of-type(2) > a

Element 75 × 32 px · x 705, y 94

Conflicting link name/destination group

Element 3/psf-landing/ · 1440 px viewport

html > body > div > header > div > nav > ul > li:nth-of-type(1) > a

Element 92 × 53 px · x 155, y 162

Conflicting link name/destination group

On /

2 link texts with two destinations

Links with the same text should lead to the same address.

Passes when: No identical link label points to conflicting destinations
Warns when: One or two conflicting link-label groups

How to fix it

Give links to different places different words ("Team pricing", "Enterprise pricing"), or point links that share their text at one destination.

Saved evidence 2 element records

Element 1/ · 1440 px viewport

html > body > div > div:nth-of-type(2) > nav > ul > li:nth-of-type(3) > a

Element 198 × 42 px · x 521, y 3

Conflicting link name/destination group

Element 2/ · 1440 px viewport

No image saved

html > body > div > div:nth-of-type(3) > div > section > div:nth-of-type(5) > h2 > a

Element 253 × 29 px · x 211, y 1821

Conflicting link name/destination group

Failing check · Inclusion · C168.1

The order on screen differs from the order in the code

On /

61 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/ · 1440 px viewport

No image saved

html > body > div > footer > div:nth-of-type(1) > div > ul > li:nth-of-type(2) > a

Element 196 × 41 px · x 328, y 2087

DOM rank differs from visual rank

Element 2/ · 1440 px viewport

No image saved

html > body > div > footer > div:nth-of-type(1) > div > ul > li:nth-of-type(3) > a

Element 196 × 41 px · x 524, y 2087

DOM rank differs from visual rank

Element 3/ · 1440 px viewport

No image saved

html > body > div > footer > div:nth-of-type(1) > div > ul > li:nth-of-type(4) > a

Element 196 × 41 px · x 720, y 2087

DOM rank differs from visual rank

On /psf-landing/

61 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/psf-landing/ · 1440 px viewport

No image saved

html > body > div > footer > div:nth-of-type(1) > div > ul > li:nth-of-type(2) > a

Element 196 × 41 px · x 328, y 1586

DOM rank differs from visual rank

Element 2/psf-landing/ · 1440 px viewport

No image saved

html > body > div > footer > div:nth-of-type(1) > div > ul > li:nth-of-type(3) > a

Element 196 × 41 px · x 524, y 1586

DOM rank differs from visual rank

Element 3/psf-landing/ · 1440 px viewport

No image saved

html > body > div > footer > div:nth-of-type(1) > div > ul > li:nth-of-type(4) > a

Element 196 × 41 px · x 720, y 1586

DOM rank differs from visual rank

Warnings (2)

Warning · Findability · C077.1

The navigation doesn’t mark the current page

On /

2 navigation groups without a current marker

The nav item for the page you're on should carry aria-current, once per navigation group.

Passes when: Each relevant navigation group identifies one current item
Warns when: No current marker, but a distinct current item is visible

How to fix it

Add aria-current="page" to the link for the current page, exactly once in each nav, and style that state so it is visible too.

Saved evidence 2 element records

Element 1/ · 1440 px viewport

html > body > div > div:nth-of-type(2) > nav

Element 1200 × 45 px · x 120, y 0

Current marker count

Element 1/ · 390 px viewport

html > body > div > div:nth-of-type(2) > nav

Element 390 × 357 px · x 0, y 0

Current marker count

On /psf-landing/

2 navigation groups without a current marker

The nav item for the page you're on should carry aria-current, once per navigation group.

Passes when: Each relevant navigation group identifies one current item
Warns when: No current marker, but a distinct current item is visible

How to fix it

Add aria-current="page" to the link for the current page, exactly once in each nav, and style that state so it is visible too.

Saved evidence 2 element records

Element 1/psf-landing/ · 1440 px viewport

html > body > div > div:nth-of-type(2) > nav

Element 1200 × 45 px · x 120, y 0

Current marker count

Element 1/psf-landing/ · 390 px viewport

html > body > div > div:nth-of-type(2) > nav

Element 390 × 357 px · x 0, y 0

Current marker count

Warning · Interaction · C108.1

Controls have no visible label

On /

1 control without a visible label

Fields need visible labels, and icon-only buttons should be few and use familiar icons.

Passes when: Fields are visibly identified and standalone icon controls are clear
Warns when: A nonstandard standalone icon control needs a label

How to fix it

Give every field a visible label, since placeholders vanish while typing. Add text to icon-only buttons, or keep them to familiar icons (search, close, menu) with an accessible name and a tooltip.

Saved evidence 1 element record

Element 1/ · 1440 px viewport

html > body > div > header > div > div:nth-of-type(1) > a

Element 290 × 82 px · x 136, y 63

On /psf-landing/

1 control without a visible label

Fields need visible labels, and icon-only buttons should be few and use familiar icons.

Passes when: Fields are visibly identified and standalone icon controls are clear
Warns when: A nonstandard standalone icon control needs a label

How to fix it

Give every field a visible label, since placeholders vanish while typing. Add text to icon-only buttons, or keep them to familiar icons (search, close, menu) with an accessible name and a tooltip.

Saved evidence 1 element record

Element 1/psf-landing/ · 1440 px viewport

html > body > div > header > div > div:nth-of-type(1) > a

Element 334 × 82 px · x 136, y 63

Passed (11)Show

Not evaluated (10)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 3 checks to fix33 /100

Information and findability2 of 4 checks to fix63 /100

Functional and interaction support1 of 1 check to fix50 /100

Inclusion and adaptation1 of 9 checks to fix89 /100

Visual expressionNot measured—

Transparency and agencyNot measured—

Essential: 70.6 of 100 points, 17 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.