Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DTabindex Anti-PatternsAction0 positive, 21 -1-on-focusableFIX
FFavicon & BrandingAction2 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
CHeading HierarchyAction7 headings, 2 skip(s)REVIEW
- H1 Immanuel
- H1 Fellowship duplicate H1
- H4 A Gospel-Centered Church in West County, St. Louis skipped
- H4 As Christ Pours into us, Christ pours out of us
- H2 visiting?
- H4 After you check out Immanuel Online skipped
- H4 An In-Person visit is a great next step
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
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
C404 Error PageActionHTTP 404, custom pageREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 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 |
|---|---|---|---|---|---|
| title Immanuel Fellowship … | 1.90:1 | 4.5:1 | #000000 | #682723 | Fail |
| a Skip to Content | 1.90:1 | 4.5:1 | #000000 | #682723 | Fail |
| a Home | 1.90:1 | 4.5:1 | #000000 | #682723 | Fail |
| span About Us | 1.90:1 | 4.5:1 | #000000 | #682723 | Fail |
| span Our Story | 2.44:1 | 4.5:1 | #000000 | #743C37 | Fail |
| span Our Pastors | 2.48:1 | 4.5:1 | #000000 | #753D37 | Fail |
| span Our Beliefs | 2.20:1 | 4.5:1 | #000000 | #6D3531 | Fail |
| span Our Partners | 2.55:1 | 4.5:1 | #000000 | #773F37 | Fail |
| span Our Chairs | 2.67:1 | 4.5:1 | #000000 | #7A423A | Fail |
| span Get Involved | 1.78:1 | 4.5:1 | #000000 | #5D2726 | Fail |
| span Sunday Gatherings | 1.76:1 | 4.5:1 | #000000 | #5C2626 | Fail |
| span Small Groups | 1.81:1 | 4.5:1 | #000000 | #5E2828 | Fail |
| span Discipleship Groups | 1.81:1 | 4.5:1 | #000000 | #5E2829 | Fail |
| span Kid's Ministry | 1.82:1 | 4.5:1 | #000000 | #5E2928 | Fail |
| span Student Ministry | 2.23:1 | 4.5:1 | #000000 | #6D3633 | Fail |
| a Next Steps | 1.79:1 | 4.5:1 | #000000 | #5D2728 | Fail |
| span Resources | 1.74:1 | 4.5:1 | #000000 | #5B2527 | Fail |
| span Contact us | 2.24:1 | 4.5:1 | #000000 | #6E3632 | Fail |
| span Sermons | 2.22:1 | 4.5:1 | #000000 | #6D3631 | Fail |
| span Giving | 2.32:1 | 4.5:1 | #000000 | #703932 | 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.
ALandmark Structure6 landmarksPASS
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
A+Heading Text QualityAll 7 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 6 images OKPASS
A+Form AccessibilityNo form controlsPASS
ALink & Button Quality1 issue(s) across 77 links and 10 buttonsPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /plan-a-visit | (empty) | empty | Add link text or aria-label |
Links without text are announced as raw URLs by screen readers.
/plan-a-visit
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
A+Form Input TypesNo form controls on this pagePASS
A+Form Input QualityNo form controls on this pagePASS
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
A+Document LanguageLang attribute set to "en-US"PASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 14 visible text node(s) render at >= 12 CSS pixelsPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
ALighthouse Accessibility AuditsScore 94/100 — 2 failing, 20 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.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
A GOSPEL-CENTERED CHURCH IN WEST COUNTY, ST. LOUIS div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > h4 |
AFTER YOU CHECK OUT IMMANUEL ONLINE div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > h4 |
These are opportunities to improve keyboard navigation in your application.
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.fluid-image-animation-wrapper > div.fluid-image-container > div.js-content-mode-element-wrapper > a.sqs-block-image-link div.fluid-image-animation-wrapper > div.fluid-image-container > div.js-content-mode-element-wrapper > a.sqs-block-image-link |
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.