Bolt
App Quality Report
Powered by Testers.AI
B86%
Quality Score
6
Pages
70
Issues
8.0
Avg Confidence
8.0
Avg Priority
35 Critical24 High11 Medium
Testers.AI
>_ Testers.AI AI Analysis

Bolt was tested and 70 issues were detected across the site. The most critical finding was: Low contrast header navigation text. Issues span A11y, Performance, Other, UX categories. Persona feedback rated Visual highest (9/10) and Accessibility lowest (6/10).

Qualitative Quality
Bolt
Category Avg
Best in Category
Issue Count by Type
Content
20
A11y
14
UX
13
Security
3
Pages Tested · 6 screenshots
Detected Issues · 70 total
1
Low contrast header navigation text
CRIT P9
Conf 9/10 A11yUX
Prompt to Fix
Increase the header navigation text color contrast to WCAG AA 4.5:1 against the dark header background. Example: change color to #e6e6e6 or adjust background to a slightly lighter shade; ensure a visible focus state (outline) for keyboard navigation.
Why it's a bug
The top navigation items (Community, Enterprise, Resources, Careers, Pricing) are light gray on a near-black header, which can be difficult to read for many users and may fail accessibility guidelines.
Why it might not be a bug
Brand aesthetic may favor a subtle nav; however readability is essential for navigation. Some users in dark themes or low-vision contexts will struggle.
Suggested Fix
Increase the contrast of the header navigation text to meet WCAG AA (at least 4.5:1 against the header background). Consider a slightly lighter background for the header or a brighter text color with a clear hover/focus state.
Why Fix
Improves navigation readability for all users, reducing friction and potential drop-offs during site exploration.
Route To
Frontend Engineer / Accessibility Specialist
Page
Tester
Mia · Usability Tester
Technical Evidence
Elements: Header: <nav> with anchor links; background #111/#0a0a0a; text color is light gray
Page Text: Header navigation items: Community, Enterprise, Resources, Careers, Pricing
2
Empty header navigation buttons (UI placeholders)
CRIT P9
Conf 9/10 OtherUX
Prompt to Fix
In the header component, locate the two buttons with empty text content and either remove them or replace with labelled controls (e.g., 'Docs', 'Community'). Add accessible labels (aria-label) if you keep icon-only buttons. Ensure consistent button styling and that all nav items are keyboard focusable.
Why it's a bug
The header contains two navigation buttons with empty text content, indicating placeholder stubs likely produced by AI-generated code. This breaks clarity, accessibility, and automated UI tests.
Why it might not be a bug
If these are intentionally hidden placeholders for future items, they should be either populated or removed; empty labels will still fail accessibility tests and confuse users.
Suggested Fix
Remove the empty buttons or replace with meaningful labels (and appropriate ARIA labels). Ensure all header actions have visible text or accessible icons with proper aria-labels.
Why Fix
Improves usability, accessibility, and testability; prevents user confusion and test failures due to unlabeled controls.
Route To
Frontend/UI Engineer
Page
Tester
Jason · GenAI Code Analyzer
3
Divider image uses non-empty alt text though decorative
CRIT P9
Conf 9/10 OtherA11y
Prompt to Fix
In the decorative divider image element, remove the descriptive text from the alt attribute or set alt="" and add aria-hidden="true" (or role="presentation") so screen readers skip this image. This ensures the divider is not announced to AT users while preserving layout for sighted users.
Why it's a bug
The image labeled as a 'Divider' appears to be a purely decorative visual separator. Screen readers will read the word 'Divider' which adds unnecessary noise for assistive technology users.
Why it might not be a bug
If the image conveys a meaningful decorative meaning or is essential for layout semantics, a non-empty alt could be justified; however the visual arc divider here is primarily decorative.
Suggested Fix
Mark the image as decorative by removing alt text or setting alt="" and add aria-hidden="true" or role="presentation" to prevent screen readers from announcing it.
Why Fix
Reduces extraneous narration for screen reader users and aligns with WCAG guidance to avoid non-informative images announcing themselves.
Route To
Frontend Accessibility Engineer
Page
Tester
Alejandro · Accessibility Specialist
Technical Evidence
Console: [ERROR] Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Network: https://bolt.new/static/marketing/homepage/feature
+67
67 more issues detected  View all →
Low color contrast in hero heading (Scale your product) agai...
Pricing copy for Teams plan is ambiguous/confusing
Interactive button missing accessible name (empty label)
and 64 more...
Unlock All 70 Issues
You're viewing the top 3 issues for Bolt.
Sign up at Testers.AI to access the full report with all 70 detected issues, detailed fixes, and continuous monitoring.
Sign Up at Testers.AI or let us run the tests for you