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
BHeading Hierarchy3 headingsREVIEW
- H2 News at FinCEN
- H2 FinCEN Publications & Actions
- H2 I need information on...
Every page should have one H1 that describes the page content.
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
BAlt Text Quality3 of 20 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 3 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
C404 Error PageActionCould not testREVIEW
404 page quality check not available.
CColor Contrast (Screenshot)Action20 text elements analyzed, 2 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 |
|---|---|---|---|---|---|
| h2 News at FinCEN | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 FinCEN Publications … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 I need information o… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title United States Depart… | 18.43:1 | 4.5:1 | #000000 | #F0F0F0 | Pass |
| a Skip to main content | 7.76:1 | 4.5:1 | #000000 | #909FAE | Pass |
| p An official website … | 1.38:1 | 4.5:1 | #000000 | #00264C | Fail |
| p Here’s how you kno… | 1.38:1 | 4.5:1 | #000000 | #00264C | Fail |
| span Here’s how you kno… | 15.14:1 | 4.5:1 | #000000 | #B7E1F8 | Pass |
| strong The .gov means it’… | 13.66:1 | 3.0:1 | #000000 | #A1D8F5 | Pass |
| p Federal government w… | 13.64:1 | 4.5:1 | #000000 | #A0D8F5 | Pass |
| strong The site is secure. | 11.19:1 | 3.0:1 | #000000 | #93C4DE | Pass |
| p The | 8.26:1 | 4.5:1 | #000000 | #80A8BE | Pass |
| strong https:// | 8.94:1 | 3.0:1 | #000000 | #85AFC6 | Pass |
| p ensures that you are… | 9.23:1 | 4.5:1 | #000000 | #86B2C9 | Pass |
| span Financial Crimes Enf… | 8.65:1 | 4.5:1 | #000000 | #83ACC3 | Pass |
| span Menu | 8.07:1 | 4.5:1 | #000000 | #7EA6BC | Pass |
| span About FinCEN | 12.31:1 | 4.5:1 | #000000 | #ABCBDC | Pass |
| span About FinCEN | 16.21:1 | 4.5:1 | #000000 | #C7E7F8 | Pass |
| span Mission | 14.97:1 | 4.5:1 | #000000 | #B5E0F7 | Pass |
| span What We Do | 14.97:1 | 4.5:1 | #000000 | #B5E0F7 | 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.
A+Landmark Structure6 landmarksPASS
AForm Accessibility1 of 2 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #query | text | Enter Search Term(s): | for/id |
| commit | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" name="commit">
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
ALink & Button Quality2 issue(s) across 71 links and 9 buttonsPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /news | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: News | |||
| <button> | (empty) | empty | Add button text or aria-label |
Generic link text like 'click here' doesn't describe the destination.
/news ("Read More")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Icon-only buttons need an aria-label so screen readers can announce them.
button.usa-nav__close (#78 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
ALighthouse Accessibility AuditsScore 94/100 — 1 failing, 23 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 |
|---|
div.usa-card__container > div.usa-card__media > div.usa-card__img > img div.usa-card__container > div.usa-card__media > div.usa-card__img > img |
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.