We found 4 issueson ledge.shworth fixing.
Watch the inspection.
We navigate your site the way customers would. Idle time is skipped.
How the composite score works
The overall score is a weighted average: Visual 18.75%, Accessibility 25%, Buttons and links 31.25%, Under the hood 12.5%, and Mobile 12.5%. Unassessed categories are excluded and the remaining weights are normalized.
Product categories start at 100. Each distinct verified finding deducts 30 points for a reproduced flow defect, or 18 for critical, 12 for high, 7 for medium, and 3 for low stored detector severity. Scores stop at zero and round to whole numbers. All verified findings count, including those beyond the displayed list. The formula is fixed and versioned, so the same saved evidence always receives the same score.
Five security response headers are missing
The response from https://ledge.sh/ is missing Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, X-Content-Type-Options: nosniff, Referrer-Policy, and Cross-Origin-Resource-Policy.
Try it: Run curl -sI https://ledge.sh/ and check the response for Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Cross-Origin-Resource-Policy.
Small grey text fails AA contrast on the home page
Several small text elements on the home page fall below the WCAG AA contrast minimum of 4.5:1. The "Install Ledge Server" label in the install command bar is at 3.53:1 (#626a4f on #070806, 12px), and the hero meta line listing the platforms ("Free and open source · Apache-2.0 · macOS on Apple Silicon ...") is at 3.47:1 (#626a4f on #0a0b08, 12px). Code block language labels such as the "sql" tag fail the same rule, and axe-core reports the color-contrast violation at serious impact across /, /docs, /android, /privacy and the docs subpages.
Try it: Open ledge.sh on desktop, scroll to the install command bar under the hero copy, and check the "Install Ledge Server" label and the platform meta line against a contrast checker.
The hero code block runs past its container on mobile
On the home page at a 390px wide viewport, the shell code block inside the notebook mockup is wider than its rounded container. All three command lines run past the container's right border and are cut off mid-character, so "curl -sG https://api.stripe.com/v1", the "-d limit=100 -d \"created[gte]=$(" line, and the jq line all end abruptly with no horizontal scroll affordance. The rounded border of the block is visible behind the overflowing text, confirming the text escapes the box rather than being wrapped or scrolled.
Try it: Open ledge.sh on a phone or a 390px wide window and look at the sh code block in the hero notebook mockup: the command lines extend past the rounded border and are clipped mid-character.
The last search result row touches the panel border
On /docs/finding-things at mobile width, the search result panel gives its final row no bottom padding. "Rollout checklist" sits directly on the panel's rounded bottom border, with the descender area of the text meeting the stroke, while the four rows above it have even vertical spacing. The row is legible but the panel looks cut short compared to its top padding.
Try it: Open /docs/finding-things on a phone and scroll to the search result panel, then look at the bottom row against the panel border.
The "A note is a Markdown file" text sits awkwardly
The inline code chip in the first body paragraph of "A note is a Markdown file" breaks across lines with a single character left alone at the right edge of the line, leaving the rest of the chip on th
A rough edge in the layout
The footer tagline text renders in a dark olive tone on the near-black footer background, giving very low contrast compared with the adjacent footer links.
A rough edge in the layout
The two table column headings are misaligned with each other: one wraps to two lines and sits higher while the other is single line and vertically centered, and neither is aligned with the empty leadi
Probie fixes this for you.
This report came from one visit. When installed on your project, Probie watches real sessions, reproduces failures, and opens tested fixes as pull requests.
Sign up and get this fixedFree inspection
What should Probie inspect next?
Enter a project URL. There is nothing to install.
Probie checks every issue twice, respects robots.txt, and backs off at bot challenges.
Enter an address and we will email the report card link.