Accessibility Statement

In short

We want everyone to be able to use this website and SilverArrow — including people who use a screen reader, people who navigate by keyboard only, people who need larger text or more color contrast, and people with dyslexia or other reading differences. A lot of SilverArrow's own users are kids, so this matters to us in a very direct way.

We have not finished this work yet. Some parts of the site work well right now. Some parts do not work as well as they should. This page tells you the truth about both, and how to tell us if something is broken for you.

1. Our commitment

Project Research LLC is working to make silverarrowapp.com meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We treat that as a starting point, not a finish line. We check new pages and features against these guidelines before they go live, and we fix problems as we find them.

2. Conformance status

Our target is WCAG 2.1 Level AA, and we are also working toward two newer WCAG 2.2 AA rules: visible focus that isn’t hidden behind other content, and a minimum size for clickable buttons and links.

As of the date above, this website partially conforms to WCAG 2.1 Level AA. That means some parts meet the standard and some parts do not yet. We have not completed a full, independent accessibility audit. What you’re reading is the result of an internal review of our own code — not a certification, and not a claim that every page has been checked.

We will not describe this site as “fully accessible,” “fully compliant,” or “certified” anywhere until an independent, documented audit says we’ve earned that.

3. Compatibility

We have not yet completed formal testing with real screen readers or other assistive technology on specific browser combinations (for example, NVDA with Chrome, or VoiceOver with Safari). Until that testing is complete and documented here, treat this site as not yet verified against any specific screen reader or browser pairing, even where the underlying code follows standard, well-supported patterns.

The site is built with standard HTML, so it should work reasonably with any modern browser and any assistive technology that supports current web standards. “Should work” is not the same promise as “tested and confirmed,” and we want to be clear about that difference.

4. Technical specifications

This site is built with HTML, CSS, and a small amount of JavaScript. The JavaScript only adds small extras (like pausing background video for people who’ve asked their device for less motion) — the words, links, and pictures on every page work with JavaScript turned off. We use WAI-ARIA attributes sparingly, and only where plain HTML doesn’t already carry the meaning we need (for example, marking a purely decorative icon as hidden from screen readers, since it sits right next to text that already says the same thing).

5. Known limitations

We know about the following problems. Here is what each one is, why it’s not fixed yet, and when we expect to fix it:

• Some button text is hard to read against its background color. The lightest part of our blue gradient buttons doesn’t have enough contrast with the white text on it. This is a brand color question, not just a code fix, so it needs a decision from our design team before we change it. Target: next design review.
• The small “Coming Soon” badge text is hard to read. Same reason as above — it’s a color choice that needs a decision, not just a markup fix. Target: next design review.
• Our stylesheet has a leftover duplicate section that redefines some footer icon colors a second time, which makes those colors harder to audit with confidence. Target: next stylesheet cleanup.
• We haven’t confirmed that every link and button in the navigation and footer meets the new minimum click-target size from WCAG 2.2. Some short text links may be smaller than the recommended size. Target: pending accessibility reviewer sign-off.
• We haven’t tested this site at 200% or 400% browser zoom in a real browser. The page is built to reflow to one column and avoid sideways scrolling, but we haven’t confirmed that by hand yet. Target: pending manual testing.
• We haven’t tested this site with real screen readers or other assistive technology. See Section 3 above. Target: pending manual testing.
• Not every page on this site has been reviewed yet. Our home page, Privacy Policy, Terms of Use, README, and shared stylesheet have been reviewed. Our About, Features, Download, Contact, Guide, White Paper, and Store & AI Disclosures pages have not yet been through this same review. Target: next review phase.

6. Feedback

If something on this site is hard to use, please tell us. Email admin@projectresearchllc.com and describe what happened and what page you were on. We aim to reply within 5 business days.

See our Accessibility Help page for keyboard shortcuts, zoom instructions, and how to ask for content in a different format.

7. Assessment approach

This statement is based on a self-evaluation — a review of our own code by our own team — not a third-party audit. We have not hired an outside accessibility firm to test this site as of the date below.

8. Statement date

This statement was written and last reviewed on August 20, 2026.