Accessibility

Ask Bobby J aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. This is the standard we build and test against, not a certification of full conformance: a formal third-party accessibility audit has not yet been completed, and some parts of the product may not yet meet the target. We prioritize equivalent task completion, sign-in, chat, evidence review, Decision Files, and checkout, over visual sameness.

• Keyboard navigation with visible focus indicators, skip links, and predictable focus return.
• Reduced-motion support: the interface honors the operating system’s “reduce motion” preference and tones down or removes animation when it is set.
• Semantic headings, landmarks, labels, and status announcements for assistive technology.
• Text resizing, zoom, and responsive reflow on small screens, with non-color status cues alongside color.
• Descriptive alternatives for meaningful imagery and empty alternatives for decorative imagery.

Automated accessibility checks run against our public pages in our continuous integration pipeline, on every change proposed to our main branch. They use axe-core, an open source rules engine, limited to its WCAG 2.1 Level A and Level AA rule sets, and they cover the home page, pricing, how it works, about, the sample Decision File, resources, help, contact, the guide page, and every legal notice on this site. A change that introduces a serious or critical failure on one of those pages fails those checks.

What that does not prove: automated rules can only detect part of WCAG. They cannot judge whether alternative text is meaningful, whether the reading order makes sense, or whether a person using a screen reader can actually finish a task. Those still require human testing, and a formal third-party accessibility audit has not been completed.

The automated checks do not yet cover signed-in areas such as chat, Decision Files, account settings, and checkout, and they cannot measure services that run on a third party’s own systems, such as hosted payment pages and security challenges.

Hosted checkout, sign-in, security challenges, maps, data-source pages, and linked documents may be operated by third parties whose accessibility we do not control. We aim to select accessible vendors, test critical tasks, and help you complete a task another way when a third-party barrier prevents completion.

If you encounter an accessibility barrier, or need to receive the service in another way, contact us at support@askbobbyj.com. Telling us the page, the task you were attempting, and the assistive technology and browser you were using helps us reproduce and fix the problem. We aim to acknowledge accessibility reports promptly and to offer an alternate path to complete your task while a fix is in progress.

Accessibility is reviewed at design review, component review, before release, and after material changes. The automated checks described above run in our continuous integration pipeline on every change proposed to our main branch. Keyboard and screen reader review is done by hand and is not automated yet, so it is not run on every change. This statement will be updated as testing coverage and conformance improve.