Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction1 icon(s) detectedFIX
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
BLandmark Structure7 landmarksREVIEW
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
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
CAlt Text QualityAction6 of 9 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 6 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
B404 Error PageHTTP 404, custom pageREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 7 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 |
|---|---|---|---|---|---|
| h1 Your personal | 1.59:1 | 3.0:1 | #000000 | #2C3038 | Fail |
| h1 research assistant | 1.59:1 | 3.0:1 | #000000 | #2C3038 | Fail |
| h1 Meet Zotero. | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Collect with a click… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Organize your way. | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Cite in style. | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Stay in sync. | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Collaborate freely. | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Rest easy. | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Ready to try Zotero? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Zotero | Your person… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Zotero | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Groups | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Documentation | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Forums | 9.25:1 | 4.5:1 | #000000 | #ABACAF | Pass |
| a Get Involved | 1.59:1 | 4.5:1 | #000000 | #2C3038 | Fail |
| a Log In | 1.59:1 | 4.5:1 | #000000 | #2C3038 | Fail |
| a Sign Up | 1.59:1 | 4.5:1 | #000000 | #2C3038 | Fail |
| a Upgrade Storage | 1.59:1 | 4.5:1 | #000000 | #2C3038 | Fail |
| a Groups | 1.59:1 | 4.5:1 | #000000 | #2C3038 | Fail |
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.
AHeading Hierarchy9 headingsPASS
- H1 Your personalresearch assistant
- H1 Meet Zotero. duplicate H1
- H2 Collect with a click.
- H2 Organize your way.
- H2 Cite in style.
- H2 Stay in sync.
- H2 Collaborate freely.
- H2 Rest easy.
- H2 Ready to try Zotero?
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
A+Form AccessibilityNo form controlsPASS
A+Link & Button Quality34 links, 1 buttons — all OKPASS
ALighthouse Accessibility AuditsScore 93/100 — 1 failing, 19 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.
Names and labels
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
section.section-md > div.row > div.feature-col > img.img-fluid section.section-md > div.row > div.feature-col > img.img-fluid |
section.section-md > div.row > div.feature-col > img.img-fluid section.section-md > div.row > div.feature-col > img.img-fluid |
div.row > div.feature-col > picture.illu-sync > img div.row > div.feature-col > picture.illu-sync > img |
section.section-md > div.row > div.feature-col > img.img-fluid section.section-md > div.row > div.feature-col > img.img-fluid |
section.section-md > div.row > div.feature-col > img.img-fluid section.section-md > div.row > div.feature-col > img.img-fluid |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.