Accessibility Statement | Field Assembly LLC

Our Commitment

Field Assembly LLC is committed to ensuring that our website and products are accessible to everyone, including people with disabilities. We believe that accessibility is not an afterthought. It's part of building software that treats all users with respect.

We work to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standard, and we actively review our site and products to identify and address accessibility gaps. This statement describes the current state of accessibility on fieldassembly.net and in our products.

Conformance Status

Substantially conforms to WCAG 2.1 Level AA

fieldassembly.net • Reviewed March 23, 2026

"Substantially conforms" means that most success criteria at WCAG 2.1 AA have been met. Known areas where we fall short are listed under Known Limitations below, along with our remediation plans.

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. They define three levels of conformance: Level A (minimum), Level AA (standard), and Level AAA (enhanced). Field Assembly targets Level AA.

Measures We Take

Field Assembly takes the following steps to support accessibility on our website and in our products:

Perceivable

All text meets a minimum contrast ratio of 4.5:1 against its background (WCAG 1.4.3). Decorative elements use a minimum ratio of 3:1 (WCAG 1.4.11).
Color is never used as the sole means of conveying information (WCAG 1.4.1).
Meaningful images include descriptive alt text. Decorative images use alt="" so they are ignored by screen readers.
Text can be resized up to 200% without loss of content or functionality (WCAG 1.4.4).
Content does not rely on visual cues alone (e.g., shape, color, or position) to convey meaning.

Operable

All interactive elements are fully keyboard-accessible. Tab order follows a logical reading sequence.
A "Skip to main content" link appears at the top of every page for keyboard users (WCAG 2.4.1).
Focus indicators are visible on all interactive elements, using a 3px gold outline that meets the enhanced contrast requirement (WCAG 2.4.11).
All interactive elements meet a minimum touch target size of 44×44 CSS pixels (WCAG 2.5.5).
No content flashes more than three times per second (WCAG 2.3.1).

Understandable

The page language is declared in the lang attribute on the <html> element.
Pages use meaningful, descriptive <title> elements.
Navigation is consistent across pages.
Form inputs include visible labels and descriptive error messages.

Robust

Semantic HTML is used throughout: headings, landmarks (nav, main, footer), lists, and ARIA attributes where needed.
ARIA labels are provided for navigation landmarks and icons to distinguish their purpose for screen reader users.
Decorative SVG icons use aria-hidden="true" and focusable="false" to prevent them from appearing in the accessibility tree.

Technical Specifications

Accessibility on fieldassembly.net relies on the following technologies:

HTML5
CSS3
JavaScript (minimal; used for interactive components only)
WAI-ARIA 1.2

Our site and products are designed to work with the following assistive technologies:

Assistive Technology	Browser	Status
NVDA (latest)	Firefox, Chrome	Tested: passes
JAWS (latest)	Chrome, Edge	Tested: passes
VoiceOver (macOS)	Safari	Tested: passes
VoiceOver (iOS)	Safari	Tested: passes
TalkBack (Android)	Chrome	Partial: in review
Keyboard-only navigation	All modern browsers	Tested: passes

Known Limitations

Despite our best efforts, some areas of our website and products may not fully meet WCAG 2.1 AA. We document these openly and are actively working to address them.

fieldassembly.net (marketing site)

Mobile navigation: The navigation links are hidden on small screens (below 600px) without a disclosed mobile menu mechanism. Users relying on assistive technology on mobile may not be able to access navigation links. We are developing an accessible mobile menu and expect to ship it in Q2 2026.

Rafter (rafter-docs.com)

Rafter has its own accessibility statement at rafter-docs.com. Known issues specific to that product are documented there.

Vellum (vellum.build)

Vellum has its own accessibility statement at vellum.build/accessibility. Known issues specific to that product are documented there.

TakeHome (take-home.app)

TakeHome has its own accessibility statement at take-home.app/accessibility. Known issues specific to that product are documented there.

If you encounter an issue not listed here, please let us know using the contact details below. We treat accessibility reports as high priority.

Assessment Approach

Field Assembly assesses the accessibility of our website and products through a combination of the following approaches:

Self-evaluation: Our team reviews code against WCAG 2.1 AA criteria during development and before releases. We use automated linting tools as a first pass.
Manual testing: We test keyboard navigation, screen reader behavior (NVDA, VoiceOver), and touch interaction on real devices.
Automated audits: We use tools such as axe and Lighthouse to scan for common accessibility issues.
User feedback: We actively solicit and act on accessibility feedback from users.

We review this Accessibility Statement at least annually, and whenever a significant change is made to our website or products.

Feedback and Contact

We welcome feedback on the accessibility of our website and products. If you encounter a barrier, have a question, or need content in an alternative format, please contact us. We aim to respond to all accessibility-related inquiries within 5 business days.

Field Assembly LLC, Accessibility Contact

Email: hello@fieldassembly.net

Please include "Accessibility" in the subject line so we can route your message quickly.

When contacting us about an accessibility issue, it helps to include: the URL of the page, the assistive technology and browser you were using, and a description of the barrier you encountered.

Formal Complaints

We are committed to responding to and resolving accessibility complaints promptly and in good faith. If you have raised an accessibility concern with us and are not satisfied with our response, you may contact the relevant enforcement authority in your jurisdiction.

In the United States, the U.S. Department of Justice Civil Rights Division handles complaints related to website accessibility under the Americans with Disabilities Act (ADA). You may find more information at ada.gov.

This statement was prepared on March 23, 2026 and is reviewed on an ongoing basis. It is based on a self-assessment conducted against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standard.