Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FLink & Button QualityAction9 issue(s) across 96 links and 2 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| (empty) | empty | Add link text or aria-label | |
| https://fpf.org/about/ | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: About | |||
| /about/ | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: About | |||
| https://fpf.org/blog/the-price-is-right-… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: The Price Is Right Responsible Uses Of Personal Data In Pricing | |||
| https://fpf.org/blog/the-rest-of-the-wes… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: The Rest Of The West Oregon And Washington Build On California Chatbot Law | |||
| https://fpf.org/blog/red-lines-under-the… | (empty) | empty | Add link text or aria-label |
| https://fpf.org/blog/red-lines-under-the… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: Red Lines Under The Eu Ai Act Understanding The Prohibition Of Biometric Categorization For Certain Sensitive Characteristics | |||
| https://fpf.org/blog/2026-chatbot-legisl… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: 2026 Chatbot Legislation Tracker | |||
| https://techpolicy.org.il/ | Israel Tech Policy Institute | new tab | Add '(opens in new tab)' to text |
| https://studentprivacycompass.org/ | Student Privacy Compass | new tab | Add '(opens in new tab)' to text |
| https://twitter.com/futureofprivacy | X | new tab | Add '(opens in new tab)' to text |
| https://www.youtube.com/futureofprivacy | Youtube | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/company/the-fut… | new tab | Add '(opens in new tab)' to text | |
| https://www.instagram.com/futureofprivac… | new tab | Add '(opens in new tab)' to text | |
| https://creativecommons.org/licenses/by/… | Creative Commons Attribution | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
a.sub-m-link (#104 on page); https://fpf.org/blog/red-lines-under-the-eu-ai-act-understanding-the-prohibit…
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
Generic link text like 'click here' doesn't describe the destination.
https://fpf.org/about/ ("Learn More"); /about/ ("Learn More"); https://fpf.org/blog/the-price-is-right-responsible-uses-of-personal-data-in-… ("Read More"); https://fpf.org/blog/the-rest-of-the-west-oregon-and-washington-build-on-cali… ("Read More"); https://fpf.org/blog/red-lines-under-the-eu-ai-act-understanding-the-prohibit… ("Read More"); https://fpf.org/blog/2026-chatbot-legislation-tracker/ ("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
Add '(opens in new tab)' to link text or aria-label.
https://techpolicy.org.il/; https://studentprivacycompass.org/; https://twitter.com/futureofprivacy; https://www.youtube.com/futureofprivacy; https://www.linkedin.com/company/the-future-of-privacy-forum; https://www.instagram.com/futureofprivacy/; https://creativecommons.org/licenses/by/4.0/
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
button (#428 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
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
CLandmark StructureAction3 landmarksREVIEW
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
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
BForm Accessibility2 of 3 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| #input_1_1 | text | for/id | |
| s | text | (Search) | placeholder only |
| #gform_submit_button_1 | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" id="gform_submit_button_1">
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="s">
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
B404 Error PageHTTP 404, custom pageREVIEW
BFavicon & Branding4 icon(s) detectedREVIEW
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.
1 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 About FPF | 16.26:1 | 3.0:1 | #FFFFFF | #231F23 | Pass |
| h2 Cornerstone Issues | 1.29:1 | 3.0:1 | #000000 | #231F23 | Fail |
| h2 FPF Spotlight | 1.29:1 | 3.0:1 | #000000 | #231F23 | Fail |
| h3 Stay Up to Date | 1.29:1 | 3.0:1 | #000000 | #231F23 | Fail |
| title The Future of Privac… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Media | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Events | 7.98:1 | 4.5:1 | #000000 | #999FB5 | Pass |
| a Training | 1.19:1 | 4.5:1 | #000000 | #02124A | Fail |
| a FPF Member Training | 1.20:1 | 4.5:1 | #000000 | #02134B | Fail |
| a Private Trainings | 1.23:1 | 4.5:1 | #000000 | #03164E | Fail |
| a FPF Training Faculty | 1.23:1 | 4.5:1 | #000000 | #01164F | Fail |
| a FPF Member Training … | 8.32:1 | 4.5:1 | #000000 | #9AA3BA | Pass |
| a Subscribe | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Contact | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Search | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a About | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a About | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Board of Directors | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Staff | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Advisory Board | 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.
A+Heading Hierarchy4 headingsPASS
- H1 About FPF
- H2 Cornerstone Issues
- H2 FPF Spotlight
- H3 Stay Up to Date
A+Alt Text QualityAll 10 images OKPASS
ALighthouse Accessibility AuditsScore 92/100 — 3 failing, 26 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
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.spotlight__row > div.spotlight__colum--posts > div.spotlight__colum--post > a.spotlight__img div.spotlight__row > div.spotlight__colum--posts > div.spotlight__colum--post > a.spotlight__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.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Privacy Policy div.container > ul#menu-footer > li#menu-item-33 > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.no-js html.no-js |
These items highlight common accessibility best practices.