Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FForm AccessibilityAction10 of 16 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| tags[] | checkbox | none | |
| tags[] | checkbox | none | |
| tags[] | checkbox | none | |
| tags[] | checkbox | none | |
| tags[] | checkbox | none | |
| tags[] | checkbox | none | |
| q | text | (Search...) | placeholder only |
| #beehiiv-nav-email | (Email Address) | placeholder only | |
| (Email Address) | placeholder only | ||
| q | text | (Search...) | placeholder only |
| (Email Address) | placeholder only | ||
| input | submit | (none) | none |
| subscribe | submit | (none) | none |
| subscribe | submit | (none) | none |
| subscribe | submit | (none) | none |
| input | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit">; <input type="submit" name="subscribe">; <input type="submit">; <input type="submit" name="subscribe">; <input type="submit" name="subscribe">
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2
Placeholder text disappears on focus and is not a reliable label.
<input type="text" name="q">; <input type="email" name="email" id="beehiiv-nav-email">; <input type="text" name="q">; <input type="email" name="email">; <input type="email" name="email">
Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.
Learn more ▾ ▴
Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).
Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading HierarchyNo headingsREVIEW
No headings found
Headings create the document outline for screen reader navigation.
Headings (H1-H6) create the document outline for screen reader navigation.
A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.
Learn more ▾ ▴
Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.
Source: WCAG 1.3.1 / W3C WAI
BLink & Button Quality5 issue(s) across 98 links and 8 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.sciencealert.com/ | (empty) | empty | Add link text or aria-label |
| https://www.facebook.com/ScienceAlert | (empty) | empty | Add link text or aria-label |
| https://twitter.com/ScienceAlert | (empty) | empty | Add link text or aria-label |
| https://www.instagram.com/sciencealert/ | (empty) | empty | Add link text or aria-label |
| https://www.sciencealert.com/feed | (empty) | empty | Add link text or aria-label |
Links without text are announced as raw URLs by screen readers.
https://www.sciencealert.com/; https://www.facebook.com/ScienceAlert; https://twitter.com/ScienceAlert; https://www.instagram.com/sciencealert/; https://www.sciencealert.com/feed
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
C404 Error PageActionHTTP 404, custom pageREVIEW
BFavicon & Branding4 icon(s) detectedREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 1 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| title ScienceAlert : The B… | 3.00:1 | 4.5:1 | #000000 | #595959 | Fail |
| a Space | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Health | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Environment | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Humans | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Tech | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Nature | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Physics | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Society | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Opinion | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Explainer | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a About Us | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Our Team | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Follow Us | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Big breakthroughs. B… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Daily roundup | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Spark: Our top stori… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Contact | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Privacy | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Privacy Manager | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
ALandmark Structure7 landmarksPASS
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
A+Alt Text QualityAll 17 images OKPASS
A+Lighthouse Accessibility AuditsScore 100/100 — 0 failing, 24 passedPASS
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.