bonsai.finance Website Audit

## Role
Act as a focused web accessibility remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve bonsai.finance at https://www.bonsai.finance.
- Scanner check ID: accessibility_contrast.
- Fix title: Improve detectable color contrast.
- Scanner check: Basic contrast.
- Category: Accessibility.
- Status: fail.
- Severity: medium.
- Priority: 20; lower numbers are more urgent.
- Score impact: 8 of 8 rule points lost.
- Evidence: 13 of 84 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.4.
- What needs attention: The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
- Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: CSS variables, design tokens, theme config, text/background combinations, buttons, links, badges, and disabled states; semantic markup, labels, landmarks, headings, focus states, image rendering, form controls, and browser-rendered accessibility output; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Affected Elements
### /100
- Source: FreeScan rendered contrast check.
- Selector: div.landing-demo-score.landing-demo-step:nth-of-type(8) > div.landing-demo-score-meter:nth-of-type(2) > p.landing-demo-score-value > span.
- Current colors: foreground rgb(82, 82, 91) on background rgb(12, 21, 18).
- Contrast: 2.4:1 measured; 4.5:1 required.
- Suggested foreground: #7D7D83, which measures 4.54:1 on the current background.
### Bonsai Compass
- Source: FreeScan rendered contrast check.
- Selector: div.landing-container.landing-container--tight > div.landing-demo-card.landing-demo-card--animated > div.landing-demo-chrome:nth-of-type(1) > span.landing-demo-chrome-label:nth-of-type(1).
- Current colors: foreground rgb(82, 82, 91) on background rgb(16, 16, 18).
- Contrast: 2.46:1 measured; 4.5:1 required.
- Suggested foreground: #7B7B81, which measures 4.52:1 on the current background.
### Your thesis
- Source: FreeScan rendered contrast check.
- Selector: div.landing-demo-card.landing-demo-card--animated > div.landing-demo-body:nth-of-type(2) > div.landing-demo-step.landing-demo-step--thesis:nth-of-type(1) > p.landing-demo-label.
- Current colors: foreground rgb(82, 82, 91) on background rgb(16, 16, 18).
- Contrast: 2.46:1 measured; 4.5:1 required.
- Suggested foreground: #7B7B81, which measures 4.52:1 on the current background.
### © 2026 Bonsai Compass. All rights reserved.
- Source: FreeScan rendered contrast check.
- Selector: div.landing-page:nth-of-type(2) > footer.landing-footer > div.landing-container > p.landing-footer-copy:nth-of-type(4).
- Current colors: foreground rgb(82, 82, 92) on background rgb(9, 9, 11).
- Contrast: 2.58:1 measured; 4.5:1 required.
- Suggested foreground: #78787F, which measures 4.54:1 on the current background.
### Early access pricing may change for future users. No trade alerts. No financial
- Source: FreeScan rendered contrast check.
- Selector: section#pricing > div.landing-container > p.landing-pricing-footnote.landing-reveal.
- Current colors: foreground rgb(101, 101, 110) on background rgb(9, 9, 11).
- Contrast: 3.45:1 measured; 4.5:1 required.
- Suggested foreground: #78787F, which measures 4.54:1 on the current background.
### Private beta.
- Source: FreeScan rendered contrast check.
- Selector: div.landing-page:nth-of-type(2) > footer.landing-footer > div.landing-container > p.landing-footer-note:nth-of-type(2).
- Current colors: foreground rgb(101, 101, 110) on background rgb(9, 9, 11).
- Contrast: 3.45:1 measured; 4.5:1 required.
- Suggested foreground: #78787F, which measures 4.54:1 on the current background.
### Bonsai Compass is not financial advice. It helps investors structure and challen
- Source: FreeScan rendered contrast check.
- Selector: div.landing-page:nth-of-type(2) > footer.landing-footer > div.landing-container > p.landing-footer-disclaimer:nth-of-type(3).
- Current colors: foreground rgb(101, 101, 110) on background rgb(9, 9, 11).
- Contrast: 3.45:1 measured; 4.5:1 required.
- Suggested foreground: #78787F, which measures 4.54:1 on the current background.
### Challenging thesis
- Source: FreeScan rendered contrast check.
- Selector: div.landing-container.landing-container--tight > div.landing-demo-card.landing-demo-card--animated > div.landing-demo-chrome:nth-of-type(1) > span.landing-demo-status:nth-of-type(2).
- Current colors: foreground rgb(113, 113, 122) on background rgb(16, 16, 18).
- Contrast: 3.93:1 measured; 4.5:1 required.
- Suggested foreground: #7B7B83, which measures 4.53:1 on the current background.
## Task
Use the provided context to safely complete this workflow: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Adjust foreground/background colors or font treatment where contrast is too low.
- Preserve brand feel while making text readable in real viewport states.
- Fix the semantic or interaction source of the issue rather than hiding warnings with ARIA or visual-only workarounds.
- Keep keyboard, screen reader, and touch users in the verification path.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Important text and controls meet reasonable contrast targets in rendered states.
- No new low-contrast states are introduced.
- The affected UI remains usable by keyboard and assistive technology and does not introduce heading, label, focus, or contrast regressions.
- The change can be checked in the browser or with an accessibility audit tool when available.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role
Act as a focused web accessibility remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve bonsai.finance at https://www.bonsai.finance.
- Scanner check ID: accessibility_axe_violations.
- Fix title: Fix rendered axe accessibility violations.
- Scanner check: Rendered axe accessibility violations.
- Category: Accessibility.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 18 of 18 rule points lost.
- Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (8).
- What needs attention: The rendered page has accessibility rule violations detected by axe-core.
- Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: axe violation details, affected selectors, rendered DOM, component source, and interaction state that triggered the issue; semantic markup, labels, landmarks, headings, focus states, image rendering, form controls, and browser-rendered accessibility output; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Affected Elements
### Elements must meet minimum color contrast ratio thresholds
- Source: axe rule color-contrast.
- Selector: a[aria-label="Bonsai Compass home"] > .landing-logo-text > .landing-logo-sub.
- Current colors: foreground #71717a on background #09090b.
- Contrast: 4.11:1 measured; 4.5:1 required.
- Suggested foreground: #787880, which measures 4.54:1 on the current background.
### Elements must meet minimum color contrast ratio thresholds
- Source: axe rule color-contrast.
- Selector: .landing-demo-chrome-label.
- Current colors: foreground #3c3c43 on background #0e0e10.
- Contrast: 1.76:1 measured; 4.5:1 required.
- Suggested foreground: #7A7A7E, which measures 4.51:1 on the current background.
### Elements must meet minimum color contrast ratio thresholds
- Source: axe rule color-contrast.
- Selector: .landing-demo-status.
- Current colors: foreground #525259 on background #0e0e10.
- Contrast: 2.48:1 measured; 4.5:1 required.
- Suggested foreground: #7A7A7F, which measures 4.52:1 on the current background.
## Task
Use the provided context to safely complete this workflow: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Fix each reported accessibility violation at the semantic source.
- Avoid suppressing automated checks unless there is a documented false positive.
- Fix the semantic or interaction source of the issue rather than hiding warnings with ARIA or visual-only workarounds.
- Keep keyboard, screen reader, and touch users in the verification path.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Critical and serious axe issues tied to this page are resolved or clearly documented as non-reproducible.
- Fixes do not introduce new keyboard, label, contrast, or landmark regressions.
- The affected UI remains usable by keyboard and assistive technology and does not introduce heading, label, focus, or contrast regressions.
- The change can be checked in the browser or with an accessibility audit tool when available.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role
Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve bonsai.finance at https://www.bonsai.finance.
- Scanner check ID: design_spacing_consistency.
- Fix title: Make spacing more consistent.
- Scanner check: Spacing consistency.
- Category: Design.
- Status: fail.
- Severity: low.
- Priority: 25; lower numbers are more urgent.
- Score impact: 7 of 7 rule points lost.
- Evidence: Detected 0 spacing class/style signal(s).
- What needs attention: The page exposes few consistent spacing signals in class or inline styles.
- Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: layout spacing tokens, component padding, section gaps, card grids, mobile breakpoints, and repeated patterns; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Use consistent section padding, gaps, and margins across repeated content blocks.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Normalize spacing using existing tokens or local conventions.
- Avoid one-off spacing hacks that create new breakpoints or layout shifts.
- Improve the actual rendered page at mobile and desktop sizes, not only the source code shape.
- Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Spacing feels consistent across related sections and viewport sizes.
- No important UI shifts or overlaps after the change.
- The rendered page is visually stable and usable on mobile and desktop viewports.
- The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.