Accessibility Statement

Last updated: March 22, 2026  •  Field Assembly LLC

Our commitment Field Assembly LLC is committed to making Rafter accessible to all users, including people with disabilities. We target WCAG 2.1 Level AA conformance across all public-facing pages.

1. Conformance Status

Rafter aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities. Conformance at Level AA means content meets all Level A and Level AA success criteria.

We assess Rafter against these standards through periodic internal review and will engage independent accessibility auditors as the product matures.

2. Measures We Have Taken

The following accessibility improvements have been implemented across Rafter's public pages and application as of March 2026:

Color contrast

All text and interactive elements have been reviewed against WCAG 1.4.3 (Contrast Minimum). Primary buttons and call-to-action elements use an amber shade (#E8953A) against dark backgrounds, and body text uses deep charcoal (#1C1917) on a warm cream background for ratios well above 7:1. Navigation links use white on a deep forest green (#1B3A2D) at sufficient contrast for the text size and weight used.

Keyboard navigation

All interactive elements — links, buttons, and form fields — are reachable and operable via keyboard. Focus indicators are visible on all focusable elements, using a 2px amber (#E8953A) outline with a 3px offset. We use :focus-visible to show focus indicators only during keyboard navigation, avoiding distraction for mouse users.

Skip navigation

Every page includes a "Skip to main content" link as the first focusable element. This satisfies WCAG 2.4.1 (Bypass Blocks), allowing keyboard and screen reader users to skip repeated navigation and reach the primary content directly.

Semantic landmarks and structure

Pages use semantic HTML5 elements — <nav>, <main>, <footer>, and heading hierarchy (h1 through h3) — to provide meaningful structure for assistive technologies. The <main> element carries an id="main-content" attribute to support skip-link targeting.

Form labels and inputs

All form inputs in the Rafter application include associated <label> elements with correct for attributes, satisfying WCAG 1.3.1 (Info and Relationships). Placeholder text is not used as a substitute for labels.

Images and alternative text

Informational images include descriptive alt attributes. The Rafter logo in the navigation includes alt="Rafter". Decorative images that convey no information use empty alt="" attributes to be ignored by screen readers.

Language attribute

All pages include a lang="en" attribute on the <html> element, enabling screen readers to select the appropriate language and pronunciation rules.

3. Known Limitations

We are aware of the following areas where full accessibility has not yet been achieved:

  • Voice input: The voice-to-document feature in the Rafter app relies on the browser's Web Speech API, which is not supported in all browsers. Users on unsupported browsers can use the text input fields as a full alternative.
  • AI-generated document output: Documents generated by Rafter are produced dynamically. While the output area uses semantic HTML, we have not yet verified that all generated document formats meet WCAG contrast and structure requirements in every case. We are actively working to improve this.
  • Mobile navigation: On small screens, the navigation collapses to show only the primary call-to-action button. We are evaluating improvements to the mobile navigation pattern to ensure all pages remain reachable via touch navigation.

4. Technical Specifications

Rafter relies on the following technologies for conformance:

  • HTML5
  • CSS3 (including custom properties)
  • JavaScript (ES2020+, for the app interface)
  • Web Speech API (optional, for voice input only)

The public marketing pages (landing, how-it-works, and all legal pages) are static HTML with no JavaScript dependencies, which supports broad compatibility with assistive technologies.

5. Supported Browsers and Assistive Technologies

We test against current versions of Chrome, Safari, Firefox, and Edge on desktop and mobile. For screen readers, we test against VoiceOver (macOS and iOS) and aim for compatibility with NVDA on Windows. We encourage users to contact us if they encounter issues with a specific browser or assistive technology combination.

6. Feedback and Contact

We welcome feedback on the accessibility of Rafter. If you encounter a barrier, notice a WCAG failure, or need content in an alternative format, please contact us:

Field Assembly LLC
63 Beach Street, Marblehead, MA 01945
[email protected]
(781) 576-0505

We aim to respond to accessibility feedback within 5 business days.

7. Formal Complaints

If you are not satisfied with our response to an accessibility concern, you may contact the relevant national authority. In the United States, accessibility complaints related to digital products may be directed to the U.S. Department of Justice Civil Rights Division or the U.S. Access Board.

8. Assessment and Review

This statement reflects a self-assessment completed in March 2026. We review and update our accessibility practices as the product evolves. The next scheduled review is planned for September 2026.

See also: Terms of Service  •  Privacy Policy