Skip to main content
401kROBSCheck eligibility
Accessibility statement

Accessibility statement for 401kROBS.com

Direct answer: 401kROBS.com aims to make its public educational pages, trust pages, provider references, and tools usable by people who navigate with keyboards, screen readers, browser zoom, and responsive devices. WCAG 2.2 is the reference standard used for current accessibility practices, but this page does not claim full WCAG conformance, legal compliance, certification, or third-party audit completion. The site also currently has no public accessibility-report channel or response service level.[1][2][3][4]

Published and reviewed by Dennis Shirshikov. Effective and last updated 2026-08-17.

Keyboard access: repeated navigation includes a skip link, and route content uses semantic links, buttons, sections, headings, and lists.

Responsive access: layouts use flexible containers and stacks for mobile, tablet, and desktop reading.

Bounded claim: this statement is not a conformance certificate, legal opinion, audit report, or promised remediation process.

Commitment and scope

401kROBS.com is committed to making its public ROBS education accessible to people with disabilities. The scope of this statement is the public 401kROBS.com website: educational pages, trust pages, tools, provider references, source libraries, route metadata, and route-local Open Graph image routes. It does not cover external provider pages, government sources, professional directories outside this site, browser extensions, operating systems, or assistive-technology products controlled by others.

W3C WAI states that accessibility statements should be useful to users and include a commitment, the applied standard, and contact information when users encounter problems. It also recommends known limitations and measures taken.[1] This page follows that structure while preserving the site's current no-intake boundary.

Reference standard: WCAG 2.2 without a conformance guarantee

The reference standard for current practices is Web Content Accessibility Guidelines (WCAG) 2.2. W3C WAI describes WCAG as a shared standard for web content accessibility. WCAG 2.2 has 13 guidelines organized under four principles: perceivable, operable, understandable, and robust. Its success criteria determine conformance at Levels A, AA, and AAA.[2]

This site uses WCAG 2.2 as a working reference, not as a blanket conformance claim. WCAG 2.2 itself says following the guidelines will make content more accessible to a wider range of people with disabilities, but will not address every user need.[3] 401kROBS.com has not published evidence sufficient to claim full WCAG 2.2 Level AA conformance, ADA compliance, Section 508 compliance, EN 301 549 compliance, or any accessibility certification.

Current accessibility practices

The current route pattern is built around plain HTML semantics and reusable site components rather than custom inaccessible controls. These practices are observable design choices for the public site today; they are not a substitute for user testing, assistive-technology testing, or a formal conformance audit.

Semantic structure

Pages use headings, sections, lists, buttons, links, breadcrumbs, and source cards so assistive technology has meaningful structure to navigate.

Keyboard path

The site header includes a skip link to the main content area. Interactive controls are implemented as real links, buttons, or form controls rather than non-semantic click targets.

Responsive reading

Content containers, cards, and navigation are designed to reflow across viewport widths rather than requiring one fixed desktop canvas.

Source-visible writing

Citations, source cards, authorship, review dates, and policy links are visible in page content, not hidden only in metadata.

These are current implementation practices observed in the site pattern, not a promise that every future route, dependency, or third-party destination will behave the same way.

Supported user actions

Readers should be able to use standard browser and assistive-technology controls to reach and understand the public content. The practical actions below describe intended ways to use the site; they do not create a support request or prove that every combination of browser, device, and assistive technology works without barriers.

  • Use the skip link at the top of the page to move past repeated header navigation.
  • Navigate page headings, lists, cards, source links, and policy links with a keyboard or assistive technology.
  • Zoom the browser or use built-in browser text scaling; content should reflow rather than requiring horizontal reading on ordinary responsive widths.
  • Open source links and internal policy links directly; a link click is navigation only and does not submit an accessibility report.
  • Use browser or assistive-technology controls for contrast, reading modes, speech output, and focus review where available.

If a page is difficult to use, try the most direct supported path first: browser zoom or text scaling, keyboard navigation, heading navigation, simplified reading features, or opening the same internal route in another current browser. These are practical use steps, not a substitute for the site fixing confirmed barriers.

Known limitations and non-claims

The limitations below are included so readers do not mistake this accessibility statement for a legal filing, audit deliverable, certification, or promised remediation program. They are part of the statement because current evidence does not support stronger claims.

  • 401kROBS.com has not published a third-party accessibility audit, VPAT, accessibility conformance report, certification, legal-compliance opinion, or continuous-monitoring service level.
  • The site currently has no public accessibility-report channel, support inbox, secure portal, ticket queue, telephone line, or promised response deadline.
  • External provider, government, professional, and source pages linked from this site are controlled by their own publishers and may have different accessibility behavior.
  • Route-local Open Graph images are for social sharing and metadata previews. They summarize pages visually but should not be treated as the only source of page meaning.

No page, component, metadata record, sitemap entry, Open Graph image, citation link, or test file should be described as proof of complete accessibility, legal compliance, or uninterrupted compatibility with every assistive technology.

Feedback and request channel status

W3C WAI recommends contact information in accessibility statements so users can report problems.[1] Current 401kROBS.com contact and privacy routes state the opposite operational fact for this site: there is no public accessibility-report channel, named support inbox, secure portal, ticket queue, telephone line, or response service level.[4][5]

Because there is no public intake, do not send private facts through ordinary site interactions, URL query strings, provider-match answers, calculator fields, external source links, or affiliate destinations. If a future real accessibility channel is published, useful non-sensitive details would include the affected page URL, visible barrier, browser, device, assistive technology if relevant, steps tried, and the result needed. Until then, opening this accessibility page, the Contact page, a policy page, or an external source does not submit a request.

Sources and verification destinations

External W3C sources support accessibility-statement structure and WCAG terminology only. Internal sources establish the current no-public-intake status. None of these sources certify this website or guarantee legal compliance.

[1]W3C WAI: Developing an Accessibility Statement

Primary W3C WAI guidance that accessibility statements should include a commitment, the accessibility standard applied, and contact information when users encounter problems; it also recommends known limitations, measures taken, technical prerequisites, tested environments, and easy-to-find placement.

[2]W3C WAI: WCAG 2 Overview

Primary W3C WAI overview explaining that WCAG is a shared web-content accessibility standard, that WCAG 2.2 has 13 guidelines organized under perceivable, operable, understandable, and robust principles, and that success criteria determine conformance.

[3]W3C Recommendation: WCAG 2.2

Normative WCAG 2.2 recommendation stating that the guidelines cover a wide range of recommendations for making web content more accessible but do not address every user need.

[4]Contact 401kROBS.com

Current contact route stating that 401kROBS.com has no public general, editorial, correction, provider, commercial, privacy, or accessibility submission channel and that policy links are reference destinations only.

[5]Privacy Policy

Current privacy policy confirming no public accessibility-report channel, named support inbox, ticket queue, secure portal, or response service level.

Use accessibility information with its limits visible

The site aims for accessible public education, uses WCAG 2.2 as a reference, and does not claim certification or a public report intake.

Read current contact status