Accessibility report for capitalforesight.com
Based on an automated WCAG 2.1 Level AA scan on July 10, 2026.
Web accessibility is a legal requirement, not an optional extra. An automated scan of capitalforesight.com found 10 types of barrier, measured against WCAG 2.1 Level AA — the standard U.S. courts apply under the ADA.
On this page, the most frequent barrier is "Some images on this page have no description for screen readers" — found on 5 elements. In total the scan flagged 22 issues across 10 categories of WCAG 2.1 Level AA.
WCAG 2.1 Level AA is the standard U.S. courts apply under the ADA, and the law across the EU under the European Accessibility Act. These barriers block screen-reader, keyboard-only, and low-vision users — and every one of them is fixable. Here's how.
What we found, and how to fix it
Some images on this page have no description for screen readers.
WCAG 1.1.1 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Blind and low-vision users rely on screen readers to read pages aloud. When an image has no description, the screen reader either skips it entirely or reads out the file name — useless. Missing alt text is the #2 lawsuit-magnet category.
How to fix it: In your site editor, click each image and look for an 'Alt text' or 'Image description' field. Write a short sentence describing what the image shows or what it links to. For purely decorative images (dividers, background flourishes), enter empty alt text or check a 'decorative' box if the platform offers one.
Some text on this page is too light to read against its background.
WCAG 1.4.3 (Level AA) EN 301 549 Affects low-vision and colorblind users
Why it matters: People with low vision, older eyes, or anyone reading on a sunny phone screen can't make out faint text. Color blindness affects about 1 in 12 men and 1 in 200 women. Insufficient contrast is the #1 most-common cause of accessibility lawsuits — every Domino's-style ADA suit cites it.
How to fix it: If you use a website builder (Squarespace, Wix, Shopify, WordPress with a theme), open your site styles or theme color settings and pick darker text colors or lighter backgrounds. Aim for very dark text on white, or very light text on dark. Free check at webaim.org/resources/contrastchecker. If you have a developer, ask them to ensure all text meets WCAG AA contrast (4.5:1 for normal text, 3:1 for large text).
This page's title (in the browser tab) is missing or generic.
WCAG 2.4.2 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Tab titles help users who have many tabs open know which one is which. Screen readers also announce the page title when the page loads.
How to fix it: In your platform's page settings or SEO panel, find the 'Page title' field and set it to something descriptive ('Contact Us — YourBusiness', not 'Untitled' or just your business name).
An iframe (embedded content) has no title.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Screen readers announce frame titles when entering them. Without one, users hear 'frame' with no context.
How to fix it: If using a third-party embed (YouTube, Vimeo, Stripe), most platforms set the title automatically. If yours doesn't, look for a 'Title' or 'Description' field on the embed block.
The page doesn't declare what language it's in.
WCAG 3.1.1 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Screen readers use this to pick the right voice and pronunciation rules. Without it, English content might be read with a French accent (or vice versa).
How to fix it: In your platform's site settings, find a 'Site language' option and set it (English = en, Spanish = es, etc.). Most modern platforms do this automatically — if it's missing, ask your developer to add lang='en' to the html element.
Some links have no readable text — usually icon-only links.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Screen-reader users hear 'link' but not where the link goes. Users navigate by listening to a list of links — useless if every entry is just 'link, link, link'.
How to fix it: In your site editor, for icon-only links (social-media icons, navigation arrows), set an 'Aria label' or 'Title' field describing where it goes ('Follow us on Twitter', 'Next page').
This page has no 'main content' region marked.
Affects screen-reader users
Why it matters: Screen-reader users press a single shortcut to jump to the main content, skipping menus and headers. Without a marked main region, they have to tab through everything.
How to fix it: Most modern platforms add this automatically. If yours doesn't, ask your developer to wrap the main content in a <main> element.
The page tells mobile browsers users can't zoom in.
WCAG 1.4.4 (Level AA) EN 301 549 Affects low-vision and colorblind users
Why it matters: People with low vision rely on pinch-zoom to read small text. Disabling zoom is a real WCAG failure and a common lawsuit target.
How to fix it: In platform site settings, look for a 'Mobile zoom' or 'Pinch zoom' option and enable it. If your developer added user-scalable=no in a viewport meta tag, ask them to remove it.
This page is missing a main heading (H1).
Affects screen-reader users
Why it matters: Screen-reader users use the H1 to confirm they landed on the right page. The H1 is also a strong SEO signal — Google uses it to understand what the page is about.
How to fix it: Add a clear, descriptive H1 to the top of the page. In website builders, this is usually the 'Title' or 'Page heading' setting. Each page should have exactly one H1.
Bring this page into compliance — free
The free wcagcheckr browser extension finds every one of these issues on your own pages and gives you the fix recipe for each — at no cost. Run it, fix what it finds, and re-check this page anytime.
Own this site? Fix the issues, then re-scan — this report updates automatically, and comes down entirely once you pass.
Some content on the page isn't inside a recognized region (header, nav, main, footer, aside).
Affects keyboard-only users
Why it matters: Screen-reader users navigate by these regions. Content outside any region can be missed when skimming.
How to fix it: Developer fix: 'wrap orphaned page content in semantic landmark elements (<main>, <aside>, <nav>) so it's reachable via landmark nav'.
This is an automated scan and catches a portion of accessibility barriers; full WCAG 2.1 Level AA conformance also requires manual and assistive-technology testing. See our methodology for what we do and don't claim.
Learn more
How this report was produced
This report is an automated scan of the page as it was publicly served on
,
using [email protected]. The captured page and these results are sealed with a
tamper-evident hash (a2b29883192e7f86…).
We report only what the page publicly returned at that time.
This seal is anchored to a trusted RFC-3161 timestamp via freetsa.org on . Independently verify this receipt →