B86%
Quality Score
7
Pages
73
Issues
7.7
Avg Confidence
7.4
Avg Priority
23 Critical30 High20 Medium
>_ Testers.AI
AI Analysis
GitHub was tested and 73 issues were detected across the site. The most critical finding was: Content blocks displayed as glowing placeholders; actual content not visible. Issues span A11y, Performance, Other, UX categories. Persona feedback rated Visual highest (7/10) and Accessibility lowest (6/10).
Qualitative Quality
GitHub
Category Avg
Best in Category
Pages Tested · 7 screenshots
Homepage
github.com
github.com
github.com
github.com
github.com
github.com
Detected Issues · 73 total
1
Content blocks displayed as glowing placeholders; actual content not visible
CRIT P9
Prompt to Fix
The main content area is obstructed by large glowing placeholder blocks. Replace with actual content or clearly label as a loading skeleton and ensure it transitions to real content. Tone down the glow so readable text remains legible behind/around the placeholder.
Why it's a bug
The screenshot shows large glowing placeholder blocks in place of real content, making it impossible for users to read or interact with the main information. This blocks task completion and undermines trust in the page.
Why it might not be a bug
If these are intentional skeletons during loading, they should be clearly labeled as loading states; however the screenshot lacks any indicator that content is loading, so this appears as a non-functional placeholder.
Suggested Fix
Replace placeholders with actual content or ensure skeletons are clearly labeled as loading and transitioned to real content once loaded. Reduce glow intensity and ensure text behind placeholders remains readable in the final state.
Why Fix
Users need to access the core content to complete tasks; placeholders prevent comprehension and decrease trust.
Route To
Frontend Engineer / UI Designer
Page
Tester
Mia · Usability TesterTechnical Evidence
Elements:
Hero section, large glowing decorative blocks, content placeholdersPage Text:
Top hero heading partially obscured by glow; visible text is hard to read due to overlay.2
UI accessibility: Buttons render with empty text labels
CRIT P9
Prompt to Fix
Review the navigation and action buttons rendered by the AI-generated code. Replace all empty button text values with meaningful labels or add ARIA attributes (aria-label/aria-labelledby) to ensure accessibility. Update the component to guarantee labels are present for both visible and icon-only buttons. Add an automated accessibility guard (lint rule) to prevent empty labels in the future.
Why it's a bug
Several button elements in the captured UI render with empty text values, making them invisible to sighted users and screen readers. This appears to be an AI-generated placeholder artifact (missing localization or aria-labels) that directly degrades usability and accessibility.
Why it might not be a bug
If those buttons are icon-only and include proper ARIA labels or accessible titles, this could be intentional. The screenshot shows some labeled buttons, but multiple others lack labels which is problematic unless aria-labels are reliably present.
Suggested Fix
Ensure every button has visible text or a non-empty accessible label (aria-label or aria-labelledby). Replace empty text values with meaningful labels or add descriptive ARIA attributes. Audits should enforce that all interactive elements are accessible.
Why Fix
Improves accessibility and usability, reduces friction for assistive tech users, and stabilizes automated UI tests that depend on element labels.
Route To
Frontend/UX Engineer
Page
Tester
Jason · GenAI Code AnalyzerTechnical Evidence
Console:
No console logs available3
Email signup field lacks an accessible label
CRIT P9
Prompt to Fix
The email signup input has no visible label. Add a visible label element linked to the input (id='email') with text 'Email address'. If keeping placeholder text, ensure it does not substitute for a label and consider adding aria-label for screen readers. Verify contrast and responsive behavior; ensure label remains visible on mobile.
Why it's a bug
The email input only shows placeholder text (Enter your email) and has no associated visible label. This makes it difficult for screen readers and keyboard users to understand what the field is for, violating basic accessibility guidelines and potentially excluding a portion of users.
Why it might not be a bug
Placeholders can be informative, but they should not replace labels. If the visual design relies on placeholders, some assistive tech may not announce the purpose of the field reliably.
Suggested Fix
Add a visible label element (e.g., label for='email') above the input with text 'Email address', and/or include an aria-label attribute on the input. Ensure the label is visible on all breakpoints and that placeholder text remains or is shortened.
Why Fix
Providing proper labeling improves accessibility and makes it clear what information is required, reducing user frustration and drop-offs during signup.
Route To
Frontend Engineer / Accessibility Specialist
Page
Tester
Mia · Usability TesterTechnical Evidence
Elements:
<input type='email'>, <button>Sign up for GitHub</button>Page Text:
Enter your email