B-80%
Quality Score
7
Pages
128
Issues
8.1
Avg Confidence
8.0
Avg Priority
51 Critical63 High13 Medium1 Low
>_ Testers.AI
AI Analysis
Anthropic was tested and 128 issues were detected across the site. The most critical finding was: No primary call-to-action in hero section. Issues span A11y, Legal, Performance, Other categories. Persona feedback rated Visual highest (8/10) and Accessibility lowest (5/10).
Qualitative Quality
Anthropic
Category Avg
Best in Category
Pages Tested · 7 screenshots
Homepage
anthropic.com
anthropic.com
anthropic.com
anthropic.com
anthropic.com
anthropic.com
Detected Issues · 128 total
1
No primary call-to-action in hero section
CRIT P9
Prompt to Fix
In the hero section, insert a prominent primary action button next to the heading. Example: 'Explore AI safety' with accessible contrast (minimum WCAG AA 4.5:1 against background). Ensure focus state is visible and keyboard accessible, and place the button in a layout that remains visually prominent across all screen sizes.
Why it's a bug
The hero area presents the value proposition but lacks a clearly visible primary action, leaving users without a clear next step to engage or explore further.
Why it might not be a bug
Some users may scroll to other sections to find actions, but the absence of a prominent CTA in the hero reduces immediate engagement and task completion.
Suggested Fix
Add a high-contrast primary button in the hero area (e.g., 'Explore AI Safety' or 'Learn More') placed near the heading. Ensure it is keyboard focusable, has a visible focus ring, and uses consistent button styling with accessible color contrast.
Why Fix
A clear CTA in the hero guides users to take a concrete action, improving engagement, task success, and perceived value of the site.
Route To
Product Designer / Frontend Engineer
Page
Tester
Mia · Usability TesterTechnical Evidence
Elements:
Hero section with heading and descriptive paragraph; missing CTA buttonConsole:
None visible; console logs shown CSP-related errors but not directly about hero CTA.Page Text:
Hero heading: "AI research and products that put safety at the frontier"; no visible primary action button in the hero.2
Generic link text 'Read More' lacks descriptive context
CRIT P9
Prompt to Fix
In the content cards, ensure all anchor text clearly describes the destination. Replace every 'Read More' with descriptive text that references the specific article or content (e.g., 'Read more: What 81,000 people want from AI'). Ensure the link text forms a meaningful, self-contained phrase when read out of context. Maintain accessible names via visible text and, if necessary, aria-labelledby to reinforce context for screen readers. Respect WCAG 2.4.4 and 1.1.1 (text alternatives for non-text content).
Why it's a bug
Multiple instances of 'Read More' across content blocks do not describe the destination or purpose of the link. Screen readers rely on link text to convey where a user will land or what content will be revealed. This fails WCAG 2.4.4 (Link Purpose) and can hinder task completion for keyboard and screen reader users.
Why it might not be a bug
If surrounding context clearly identifies the target content, it could be acceptable. However, the repeated use of non-descriptive text without explicit context makes the links unclear for assistive technologies.
Suggested Fix
Replace generic link text with descriptive phrases that refer to the target content, e.g., 'Read more about What 81,000 people want from AI' or 'Read more: What 81,000 people want from AI' on each card.
Why Fix
Descriptive link text improves accessibility by conveying the purpose of each link to screen readers and reduces navigation errors for users relying on AT.
Route To
Frontend/Accessibility Engineer
Page
Tester
Alejandro · Accessibility SpecialistTechnical Evidence
Console:
[ERROR] Loading the script 'https://googleads.g.doubleclick.net/pagead/viewthroughconversion/16632748715/?random=1773967954541&cv=11&fst=1773967954541&bg=ffffff&guid=ON&async=1&en=gtag.config>m=45be63i0v9196940227za200zd9196940227xec&gcd=13t3t3t3t5l1&dma=0&tag_exp=103116026~103200004~115938466~115938468~116024733~117484252&u_w=800&u_h=600&url=https%3A%2F%2Fwww.anthropic.com%2F&frm=0&tiba=Home%20%5C%20Anthropic&hn=www.googleadservices.com&npa=0&pscdl=noapi&auid=822014336.1773967955&uaa=&uab=&uafvl=&uamb=0&uam=&uap=&uapv=&uaw=0&data=event%3Dgtag.config&rfmt=3&fmt=4' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' https://cdn.intellimize.co https://cdnjs.cloudflare.com https://d3e54v103j8qbb.cloudfront.net https://cdn.prod.website-files.com https://hubspotonwebflow.com https://www.googletagmanager.com https://a-cdn.anthropic.com https://connect.facebook.net https://www.youtube.com https://cdn.jsdelivr.net https://cdn.finsweet.com https://maps.googleapis.com https://js.hsforms.net https://player.vimeo.com". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.3
Empty anchor link lacks accessible text
CRIT P9
Prompt to Fix
Find all anchor tags (<a href=...>) that have empty inner text. Replace them with anchors that have meaningful visible text or, if the anchor is decorative, remove it or add aria-label with a descriptive name. Ensure the fix complies with WCAG 2.4.4 (Link Purpose).
Why it's a bug
An anchor element with empty text cannot be announced by screen readers, making it invisible to users of assistive technologies. This violates link accessibility expectations (WCAG 2.4.4 Link Purpose) and can confuse keyboard users relying on text cues.
Why it might not be a bug
If the anchor is intended as a purely decorative control with an aria-label that communicates its purpose, it could be acceptable. However, the data shows text is empty and there is no aria-label provided.
Suggested Fix
Remove the empty anchor or provide meaningful visible text. If the link must be image-based, add a descriptive aria-label (e.g., aria-label="Anthropic home") or ensure there is visible text that conveys the link purpose.
Why Fix
Ensures all users, including those using screen readers, can understand and navigate links, improving overall navigability and compliance with WCAG 2.4.4.
Route To
Frontend Accessibility Engineer
Page
Tester
Alejandro · Accessibility SpecialistTechnical Evidence
Console:
[ERROR] Loading the image 'https://www.google.com/ccm/collect?frm=0&en=page_view&dl=https%3A%2F%2Fwww.anthropic.com%2F&scrsrc=www.googletagmanager.com&rnd=533316318.1773967976&dt=Home%20%5C%20Anthropic&auid=822014336.1773967955&navt=n&npa=0>m=45be63i0v9196940227za200zd9196940227xec&gcs=G111&gcd=13t3t3t3t5l1&dma=0&tag_exp=103116026~103200004~115938466~115938468~116024733~117484252&apve=1&apvf=f&apvc=1&tids=AW-16632748715&tid=AW-16632748715&tft=1773967976127&tfd=3255' violates the following Content Security Policy directive: "img-src 'self' data: https://cdn.sanity.io https://www-cdn.anthropic.com https://cdn.prod.website-files.com https://img.youtube.com https://i.ytimg.com https://www.facebook.com https://maps.googleapis.com https://maps.gstatic.com https://www.googletagmanager.com https://forms-na1.hsforms.com"