Report #1 — Accessibility PreCheck

1.1.1 medium partial

Non-text Content

The page contains one inline SVG inside the logo div with no accessible name — no <title>, aria-label, aria-hidden, or role attribute. While the adjacent text 'AccessibilityPreCheck' provides brand context, the SVG itself is non-text content that is exposed to assistive technology without an explicit text alternative or an explicit decorative marker. There are no <img> elements, so no missing alt attributes elsewhere.

Remediation

Mark the decorative logo SVG with aria-hidden="true" and focusable="false" (since the adjacent brand text conveys the name), or add role="img" with an aria-label such as "AccessibilityPreCheck logo" if it is intended to be meaningful.

WCAG 1.1.1 — Non-text Content

1.2.1 not_applicable

Audio-only and Video-only (Prerecorded)

The page contains no prerecorded audio-only or video-only media. The HTML source includes only text content, CSS styling, and a single inline SVG icon (a checkmark in the logo). No <audio>, <video>, <embed>, or <object> elements referencing media files are present.

WCAG 1.2.1 — Audio-only and Video-only (Prerecorded)

1.2.2 not_applicable

Captions (Prerecorded)

The page contains no prerecorded audio or video content. The HTML source includes only text, CSS styling, inline SVG icons, and hyperlinks — no <audio>, <video>, <iframe>, or embedded media elements that would require captions.

WCAG 1.2.2 — Captions (Prerecorded)

1.2.3 not_applicable

Audio Description or Media Alternative (Prerecorded)

The page contains no prerecorded synchronized media (no <video>, <audio>, <iframe>, or embedded media players). The content is entirely text, CSS, and a single decorative SVG icon, so there is no video content requiring audio description or a media alternative.

WCAG 1.2.3 — Audio Description or Media Alternative (Prerecorded)

1.3.1 low partial

Info and Relationships

The page uses semantic landmarks (<header>, <nav>, <section>, <footer>) and heading structure (h1, h2, h3) that programmatically convey document outline. However, the pricing features list uses CSS pseudo-element content ('::before { content: "✓ "; }') to inject checkmark indicators that visually convey 'included' status — this presentational meaning is not programmatically determinable nor available in text within the <li> elements. Additionally, the brand text splits 'Accessibility' and 'PreCheck' across nested <span> elements purely for color styling, which is cosmetic and acceptable, but the SVG logo lacks role/aria-hidden, leaving its semantic intent ambiguous.

Remediation

Move the checkmark indicator into the DOM as real text (e.g., '<li><span aria-hidden="true">✓</span> PDF document or web page URL</li>') or use a list semantic that conveys 'included' status, so assistive tech users perceive the same affirmative meaning sighted users get. Add aria-hidden="true" to the decorative SVG in the logo.

WCAG 1.3.1 — Info and Relationships

1.3.2 pass

Meaningful Sequence

The DOM order follows a logical sequence: header/nav, hero with heading and supporting text, 'How It Works' steps numbered 1-3 in source order, 'What Gets Checked' features, pricing, and footer. No CSS positioning techniques (absolute positioning, float, flexbox order, or grid-area reordering) are used that would cause the visual presentation to diverge from the source order. Grid layouts in .steps and .features use default auto-placement, preserving DOM sequence.

WCAG 1.3.2 — Meaningful Sequence

1.3.3 pass

Sensory Characteristics

The page contains no instructions that rely on sensory characteristics. Navigation and CTAs are identified by visible text labels (e.g., 'Run a Check', 'Browse Standards', 'Sign In', 'Step 1/2/3' with headings like 'Upload or Enter URL'). There are no references such as 'click the green button' or 'see the box on the right' that would depend solely on shape, color, size, or location.

WCAG 1.3.3 — Sensory Characteristics

1.4.1 pass

Use of Color

The page does not rely on color alone to convey information. Navigation links and buttons are distinguished by text labels, layout, and borders (e.g., .btn-primary has a solid background and text 'Run a Check', .btn-outline has a visible border). The trust-strip pills use both color and text content. The price-features list uses a '✓' checkmark character in addition to green color to indicate included features. No form validation states, charts, or color-coded indicators are present that would depend on color alone.

WCAG 1.4.1 — Use of Color

1.4.2 not_applicable

Audio Control

The HTML source contains no <audio>, <video>, <embed>, <object>, or <iframe> elements, and no autoplay attributes or media references. There is no audio content on this page that could play automatically.

WCAG 1.4.2 — Audio Control

2.1.1 pass

Keyboard

All interactive elements on the page are native anchor (<a>) elements — navigation links, CTAs (Run a Check, Browse Standards), and footer links. Native anchors are inherently keyboard-operable via Tab and Enter. No custom widgets, divs-as-buttons, onclick handlers without keyboard equivalents, or elements requiring specific keystroke timings are present.

WCAG 2.1.1 — Keyboard

2.1.2 pass

No Keyboard Trap

The page contains only standard interactive elements: anchor links in the header navigation, hero CTAs, and pricing card. There are no custom widgets, modal dialogs, embedded media players, iframes, or scripted focus handlers that could create a keyboard trap. All focusable elements are native <a> tags which inherently allow focus to move in and out via Tab/Shift+Tab.

WCAG 2.1.2 — No Keyboard Trap

2.1.4 not_applicable

Character Key Shortcuts

The HTML source contains no JavaScript event handlers for keyboard shortcuts (no keydown, keyup, or keypress listeners) and no evidence of single-character key shortcuts being implemented. The page is a static marketing page with standard link navigation only.

WCAG 2.1.4 — Character Key Shortcuts

2.2.1 not_applicable

Timing Adjustable

The page is a static marketing/landing page with no time limits, session timeouts, auto-refresh, auto-advancing content, or other timing mechanisms. There is no JavaScript timer, meta refresh, or session-bound functionality in the HTML that would impose a time constraint on the user.

WCAG 2.2.1 — Timing Adjustable

2.2.2 not_applicable

Pause, Stop, Hide

The HTML contains no moving, blinking, scrolling, or auto-updating content. The only animations are CSS hover transitions on buttons (0.15s background/color changes), which are user-initiated and do not constitute moving content under this criterion. No carousels, marquees, auto-refreshing widgets, or animated elements are present.

WCAG 2.2.2 — Pause, Stop, Hide

2.3.1 pass

Three Flashes or Below Threshold

The HTML contains only static content: text, SVG icons, CSS gradients, and hover transitions (0.15s background/color changes). No animations, video, GIFs, auto-playing media, or flashing elements are present. The only motion is subtle hover state transitions on buttons and links, which do not flash and occur only on user interaction.

WCAG 2.3.1 — Three Flashes or Below Threshold

2.4.1 medium fail

Bypass Blocks

The page contains a repeated header/navigation block (header with logo, brand, and nav links) but provides no skip link mechanism to bypass it. There is no 'Skip to main content' anchor link as the first focusable element, no <main> landmark element, and the <section> elements lack ARIA landmark roles or IDs that could serve as skip targets. Keyboard users must tab through all header navigation links on every page load.

Remediation

Add a visually-hidden 'Skip to main content' link as the first focusable element inside <body> that targets a <main id="main"> element wrapping the hero/primary content. Also wrap primary content in a <main> landmark to enable landmark-based navigation as an additional bypass mechanism.

WCAG 2.4.1 — Bypass Blocks

2.4.2 pass

Page Titled

The page has a descriptive <title> element: 'Accessibility PreCheck — Accessibility Gap Analysis, Before the Audit'. This title clearly describes both the site/product identity and the topic/purpose of the page (gap analysis before an accessibility audit).

WCAG 2.4.2 — Page Titled

2.4.3 pass

Focus Order

The DOM order follows a logical sequence: header logo/brand, then nav links (Standards, Sign In, Run a Check), then hero content with primary/secondary CTAs, then sequential sections (How It Works steps 1-2-3, What Gets Checked features, Pricing), and finally the footer links. This matches the visual reading order, and no positive tabindex values or absolute positioning disrupt the natural focus flow. Focusable elements (anchors) will receive focus in an order that preserves meaning and operability.

WCAG 2.4.3 — Focus Order

2.4.4 pass

Link Purpose (In Context)

All links on the page have descriptive text that conveys their purpose: navigation links use clear labels ('Standards', 'Sign In', 'Run a Check'), CTA buttons specify purpose ('Run a Check — $100', 'Browse Standards'), the footer contains named links ('Terms', 'Privacy', 'Trust', 'Contact', 'AI Launch Pods'), and there are no generic 'click here' or 'read more' style links. No icon-only or empty links were found in the HTML source.

WCAG 2.4.4 — Link Purpose (In Context)

2.5.1 not_applicable

Pointer Gestures

The page consists entirely of static content, text, links, and buttons (anchor tags with href attributes for navigation). There are no multipoint or path-based gestures (e.g., pinch-to-zoom controls, swipe carousels, drag-and-drop, or path-based drawing) implemented in the HTML or referenced via JavaScript event handlers.

WCAG 2.5.1 — Pointer Gestures

2.5.2 pass

Pointer Cancellation

All interactive elements on the page are standard anchor tags (<a href>) used for navigation — '/run-check/', '/library/', '/accounts/login/', '/terms/', '/privacy/', '/trust/', and mailto link. There are no custom pointer event handlers (no onmousedown, onpointerdown, or JavaScript event listeners), so activation follows default browser behavior which triggers on the up-event (click), satisfying the criterion.

WCAG 2.5.2 — Pointer Cancellation

2.5.3 pass

Label in Name

All interactive UI components on this page are plain text links (e.g., 'Run a Check — $100', 'Browse Standards', 'Standards', 'Sign In', 'Run a Check', 'Terms', 'Privacy', 'Trust', 'Contact'). None of these links have aria-label or aria-labelledby attributes that would override the visible text, so the accessible name matches the visible label by default. The logo SVG has no visible text label associated with it, so 2.5.3 does not impose a name-mismatch concern there.

WCAG 2.5.3 — Label in Name

2.5.4 not_applicable

Motion Actuation

The page is a static marketing landing page containing only standard HTML elements (header, navigation links, hero text, CTA buttons, step cards, pricing card, footer). There is no JavaScript that listens to device motion events (e.g., DeviceMotionEvent, DeviceOrientationEvent) or user motion, and no functionality is triggered by shaking, tilting, or gesturing.

WCAG 2.5.4 — Motion Actuation

3.1.1 pass

Language of Page

The <html> element explicitly declares lang="en", making the default human language of the page programmatically determinable by assistive technologies.

WCAG 3.1.1 — Language of Page

3.2.1 pass

On Focus

The page contains only static interactive elements: anchor links in the header navigation, hero CTAs, and pricing section. None of these links carry onfocus handlers, JavaScript event attributes, or any mechanism that would trigger a context change (navigation, form submission, new window) upon receiving focus. Hover-only styling on links and buttons does not affect focus behavior.

WCAG 3.2.1 — On Focus

3.2.2 pass

On Input

The page contains no form inputs, select elements, or interactive UI components that accept user input. The only interactive elements are static navigation links and CTA anchors (e.g., /run-check/, /library/, /accounts/login/), none of which are user-settable controls that could trigger an unexpected context change on input.

WCAG 3.2.2 — On Input

3.3.1 not_applicable

Error Identification

The page contains no form inputs or user input fields that could trigger error detection. It is a marketing landing page with navigation links and CTA buttons only — no text inputs, selects, textareas, or form submission elements are present in the HTML source.

WCAG 3.3.1 — Error Identification

3.3.2 not_applicable

Labels or Instructions

The page contains no user input controls — no form fields, text inputs, search boxes, checkboxes, or other elements requiring user input. The only interactive elements are navigation links and call-to-action anchors (e.g., '/run-check/', '/library/', '/accounts/login/'), which do not require labels or instructions under 3.3.2.

WCAG 3.3.2 — Labels or Instructions

4.1.1 pass

Parsing (Deprecated in 2.2)

Review of the raw HTML shows well-formed markup: DOCTYPE declared, all elements have matching start/end tags (header, nav, section, div, footer, ul, li), proper nesting (e.g., nav inside header, ul/li in pricing-card), no duplicate attributes observed, and no duplicate IDs — in fact, no id attributes are used in the document at all, eliminating uniqueness conflicts. Self-closing tags (meta, link, svg path/circle) are used correctly per HTML5 rules.

WCAG 4.1.1 — Parsing (Deprecated in 2.2)

4.1.2 pass

Name, Role, Value

All interactive UI components on the page are native HTML elements with implicit roles and accessible names. The navigation uses semantic <nav> with anchor links containing visible text labels ('Standards', 'Sign In', 'Run a Check'), the header uses <header>, footer uses <footer>, and section headings use proper <h1>-<h3> hierarchy. No custom widgets, ARIA components, or stateful controls exist that would require explicit role/state/value management. The decorative SVG logo is inside a non-interactive div and does not require an accessible name.

WCAG 4.1.2 — Name, Role, Value

1.2.4 not_applicable

Captions (Live)

The page contains no live audio or synchronized media content. The HTML consists entirely of static text, CSS styling, and an inline SVG icon — no <audio>, <video>, streaming embeds, or live broadcast elements are present.

WCAG 1.2.4 — Captions (Live)

1.2.5 not_applicable

Audio Description (Prerecorded)

The page contains no prerecorded video or synchronized media content. The HTML source includes no <video>, <audio>, <iframe> (e.g., embedded YouTube/Vimeo), or <object> elements — only text, inline SVG icons, and styling. With no video content present, audio description requirements do not apply.

WCAG 1.2.5 — Audio Description (Prerecorded)

1.3.4 pass

Orientation

The page uses a responsive viewport meta tag (width=device-width, initial-scale=1.0) and includes a media query at max-width 768px that adapts the layout for narrower viewports. No CSS orientation locks (e.g., orientation media queries restricting display, or transform-based rotation locks) are present in the HTML or stylesheet, so the content will render in both portrait and landscape orientations.

WCAG 1.3.4 — Orientation

1.3.5 not_applicable

Identify Input Purpose

The page contains no input fields that collect information about the user. Navigation consists only of anchor links (Standards, Sign In, Run a Check) and there are no form elements (no <input>, <textarea>, or <select> tags) on this landing page.

WCAG 1.3.5 — Identify Input Purpose

1.4.3 high fail

Contrast (Minimum)

Multiple text/background combinations fall below the 4.5:1 minimum contrast ratio on the dark background (#0F172A). Specifically: muted body/nav text #94A3B8 on #0F172A yields ~5.8:1 (passes), but #64748B (disclaimer line, footer brand, footer links) on #0F172A yields only ~3.5:1 — failing for normal text. Additionally, the accent green #5DCAA5 on the trust-strip pill background rgba(29,158,117,0.12) over #0F172A produces marginal contrast, and the white-on-#0F6E56 primary button text yields ~4.9:1 which passes but the hover state #1D9E75 with white text drops to ~3.4:1, failing AA for normal text.

Remediation

Darken or brighten low-contrast text: replace #64748B with at least #94A3B8 (or lighter) on the #0F172A background for the disclaimer, footer brand, and footer links. Adjust the primary button hover background (#1D9E75) to a darker shade (e.g., #0F6E56 or darker) so white text maintains ≥4.5:1. Verify all green accent text against its actual rendered background with a contrast checker.

WCAG 1.4.3 — Contrast (Minimum)

1.4.4 pass

Resize Text

The page uses relative units appropriately: viewport meta tag allows user scaling (no maximum-scale or user-scalable=no restriction), and the layout uses flexible CSS with max-width containers and flexbox/grid that should accommodate browser zoom up to 200%. Font sizes are declared in px but modern browsers scale px-based text with the zoom function without loss of content. A responsive breakpoint at 768px further supports reflow at higher zoom levels.

WCAG 1.4.4 — Resize Text

1.4.5 pass

Images of Text

All textual content on the page — including the brand name 'AccessibilityPreCheck', headings, body copy, button labels, pill badges, pricing, and footer links — is rendered as live HTML text styled with CSS (Inter font family) rather than as images. The only image-like elements are a decorative inline SVG checkmark logo icon, which conveys no textual information.

WCAG 1.4.5 — Images of Text

1.4.10 pass

Reflow

The page declares a responsive viewport (`<meta name="viewport" content="width=device-width, initial-scale=1.0">`) and includes a mobile breakpoint at 768px that collapses multi-column grids (`.steps` and `.features`) to single columns, stacks the CTA buttons, and reduces section padding. Layouts use flexible units (max-width with auto margins, percentage-based grid columns, flex-wrap on the trust-strip), so content should reflow to a 320 CSS pixel viewport without requiring horizontal scrolling. No fixed-width containers, horizontal scroll containers, or wide tables/images were found that would force two-dimensional scrolling.

WCAG 1.4.10 — Reflow

1.4.11 medium partial

Non-text Contrast

Several UI components have contrast issues against the #0F172A background. The .btn-outline border (#334155) against #0F172A yields ~1.6:1, well below 3:1. The step-card and feature-card borders (#334155) also fail at ~1.6:1 against the body background, meaning these card boundaries — which are the visual UI component indicators — do not meet 3:1. The primary button #0F6E56 vs #0F172A background gives ~2.2:1, failing component contrast (though text within may still pass 1.4.3). Focus indicators are not defined in CSS, so default browser focus rings may also fail on this dark background.

Remediation

Increase border colors on .btn-outline, .step-card, .feature-card, and .pricing-card from #334155 to at least #6B7A94 or lighter to achieve 3:1 against #0F172A. Lighten the .btn-primary background or add a visible border, and define explicit :focus-visible outlines with ≥3:1 contrast.

WCAG 1.4.11 — Non-text Contrast

1.4.12 medium partial

Text Spacing

The CSS uses fixed font-size values and explicit line-height declarations (e.g., body line-height: 1.6, .hero h1 line-height: 1.15, letter-spacing: -0.02em on headings) without max-width or overflow constraints that would clearly prevent clipping when text spacing is overridden. However, containers generally use flexible widths (max-width with auto margins) and the hero h1 has a max-width of 720px with no fixed height, suggesting most text would reflow. The negative letter-spacing on headings (-0.02em, -0.01em) would be overridden by user spacing rules without loss, but tight line-height (1.15) on the h1 combined with no height constraint should accommodate 1.5x override. No explicit fixed heights on text containers were found that would cause content clipping.

Remediation

Manually test the page with a text-spacing bookmarklet (line-height 1.5, paragraph spacing 2x, letter-spacing 0.12em, word-spacing 0.16em) to confirm no clipping or overlap occurs, particularly in the .pill trust-strip elements (fixed padding with small font) and .step-card/.feature-card grid layouts. Avoid fixed heights on any text-containing element.

WCAG 1.4.12 — Text Spacing

1.4.13 not_applicable

Content on Hover or Focus

The page contains no hover- or focus-triggered additional content such as custom tooltips, popovers, or disclosure widgets. The only hover interactions are CSS color changes on nav links and buttons (e.g., `.nav a:hover`, `.btn-primary:hover`), which modify styling of existing elements rather than revealing new content. No `title` attributes, `aria-describedby` tooltips, or JS-driven hover/focus reveals are present.

WCAG 1.4.13 — Content on Hover or Focus

2.4.5 low fail

Multiple Ways

The page provides only a single navigation mechanism — a top header nav with links to Standards, Sign In, and Run a Check. There is no site map, search function, table of contents, or alternative navigation method to locate pages within the site. With only three navigation links and a small site, this is a technical failure of 2.4.5, though practical impact is minimal.

Remediation

Add a second way to locate pages, such as a site map page, a search function, or an expanded footer navigation listing all key pages (Standards, Run a Check, Sign In, Terms, Privacy, Trust, Contact already partially appear in the footer but key content pages like Standards/Run a Check are not duplicated there).

WCAG 2.4.5 — Multiple Ways

2.4.6 pass

Headings and Labels

The page uses descriptive headings that accurately reflect section content: h1 'Accessibility Gap Analysis, Before the Audit', h2 headings 'How It Works', 'What Gets Checked', 'Pricing', and h3 headings like 'Upload or Enter URL', 'Select Standards', 'Get Your Report', 'PDF Documents', 'Web Pages', 'Section 508 Compliance', 'Actionable Remediation'. Navigation link labels ('Standards', 'Sign In', 'Run a Check') and CTA labels ('Run a Check — $100', 'Browse Standards') clearly describe their purpose. No form fields exist on this page that would require additional label evaluation.

WCAG 2.4.6 — Headings and Labels

2.4.7 high fail

Focus Visible

The stylesheet defines no :focus or :focus-visible styles for any interactive element (nav links, buttons, CTA anchors, footer links). Browsers' default focus outlines may be suppressed or rendered invisibly against the dark #0F172A background, and the custom .btn-primary, .btn-outline, .nav a, and .footer-links a selectors only define :hover states, leaving keyboard users without a reliable focus indicator.

Remediation

Add explicit :focus-visible styles for all interactive elements (e.g., a, button, .btn-primary, .btn-outline, .nav a) with a high-contrast outline such as `outline: 2px solid #5DCAA5; outline-offset: 2px;` to ensure keyboard focus is clearly visible against the dark background.

WCAG 2.4.7 — Focus Visible

3.1.2 pass

Language of Parts

The page declares its primary language via <html lang="en">. All visible text content is in English; there are no foreign-language passages or phrases requiring a separate lang attribute. Terms like 'axe-core', 'ARIA', 'WCAG', and the brand name 'AI Launch Pods' are technical terms and proper names, which are explicitly exempt from this criterion.

WCAG 3.1.2 — Language of Parts

3.2.3 pass

Consistent Navigation

This is a single-page evaluation containing one consistent navigation block in the <header> with links in a fixed order (Standards, Sign In, Run a Check) and a footer with links in a fixed order (Terms, Privacy, Trust, Contact). Since only one page is provided, consistency across multiple pages cannot be fully verified, but the navigation structure is statically defined in HTML/CSS (not dynamically reordered) and would render in the same relative order on any page using this template.

WCAG 3.2.3 — Consistent Navigation

3.2.4 pass

Consistent Identification

On this single-page document, repeated functional components are identified consistently. The 'Run a Check' CTA appears in the header nav, hero, and pricing section using identical label text and the same /run-check/ destination. The logo/brand mark is rendered once, and footer links use consistent labels. No conflicting identifications (e.g., the same icon used for different functions, or different labels for the same action) were observed.

WCAG 3.2.4 — Consistent Identification

3.3.3 not_applicable

Error Suggestion

The page contains no form inputs requiring validation — only navigation links and call-to-action anchors (e.g., /run-check/, /accounts/login/). With no input fields present, there is no opportunity for input errors to be detected or for correction suggestions to be required.

WCAG 3.3.3 — Error Suggestion

3.3.4 not_applicable

Error Prevention (Legal, Financial, Data)

This page is a marketing landing page with no forms that cause legal commitments, financial transactions, or modifications/deletions of user-controlled data. The CTAs are navigation links to /run-check/ and /accounts/login/; no submission occurs on this page itself.

WCAG 3.3.4 — Error Prevention (Legal, Financial, Data)

4.1.3 not_applicable

Status Messages

This is a static marketing landing page with no dynamic status messages, no form submissions with feedback, no live regions, no loading indicators, and no asynchronous content updates. There is no functionality that would trigger status messages requiring programmatic announcement to assistive technologies.

WCAG 4.1.3 — Status Messages

Accessibility Report #1

Section 508 (Revised)