This site is designed to be usable by the widest possible audience, including readers who rely on assistive technology. The notes below describe the standard we target, the decisions we have made in the build, the limits we are honest about, and how to tell us when we have fallen short.
1. The Standard We Target
We design and maintain the public website with reference to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. WCAG 2.1 AA is the standard most widely referenced in U.S. and international digital accessibility law and the level of compliance we believe a reader has a right to expect.
2. Decisions in the Build
Specific implementation choices that follow from that standard include:
- Semantic structure. Headings appear in order. Pages use real landmarks (header, main, footer, nav). Lists are lists, not styled divs. Form fields use real labels.
- Keyboard. Every interactive element on the public site can be reached and operated with a keyboard. Focus indicators are visible.
- Image text alternatives. Informative images carry alternative text. Atmospheric and decorative images are marked as such so they are not announced to screen readers as content.
- Contrast. Body text on both surfaces is set to meet the 4.5:1 ratio required for WCAG 2.1 AA. Large display text meets 3:1.
- Color independence. No information is conveyed by color alone. Hover, focus, and active states combine color with motion or underline.
- Reduced motion. The site honors the
prefers-reduced-motionuser preference. When that preference is set, animated reveals are removed, smooth scroll is disabled, and the homepage background video is replaced by its still-image fallback. - Decorative video. The homepage uses a muted, decorative video. It has no audio, no narration, and conveys no information that is not also conveyed in type. It is marked so screen readers ignore it.
- Typography. Body text is sized for comfortable reading at default browser zoom, weighted at regular (400) or heavier, and set at generous line heights.
- No accessibility overlay widget. We do not use a third-party overlay or accessibility "fix" widget. The disability community has raised consistent and serious concerns that overlays interfere with the assistive technology real users depend on. We rely on the page itself to be accessible.
3. How We Test
We run automated audits on the public pages using widely available tools, including Google Lighthouse, and review the results before publishing material changes. Automated tools catch many issues but not all of them; where appropriate we supplement with keyboard-only navigation and spot checks using assistive technology available to us. We treat accessibility findings the same way we treat any other build defect.
4. Known Limits
- The investor portal behind authentication has not been audited to the same standard as the public marketing site, and remains in active development.
- This is a small firm. We do not employ a full-time accessibility specialist. Where we identify a barrier we cannot solve internally, we will say so plainly and seek the right help.
5. Tell Us When We Fall Short
If you have encountered a barrier on this site, write to [email protected]. To help us respond efficiently, please include the page where the issue occurred, a description of what went wrong, and (if relevant) the assistive technology and browser you were using.
6. External Authorities
If we cannot resolve a barrier to your satisfaction, you retain the right to raise the matter with the U.S. Department of Justice or, depending on your location, the equivalent authority in your jurisdiction.
7. Updates
This page is reviewed at least annually and whenever the site changes substantively.