An R&D Binder you can read, navigate, and use.

R&D Binder targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We treat WCAG 2.1 AA as the design and implementation bar for every page on rdbinder.com, including the marketing pages, the order form, the post-payment intake form, the sample binder previews, and the legal pages.

Accessibility is part of our definition of done for any new page or material change. We do not ship a page that we believe falls short of AA on a known and reproducible barrier.

Concretely, these are the practices baked into the site today.

• Semantic HTML. Pages are built with standard landmark elements (header, nav, main, section, footer), and headings follow a logical outline. Buttons are button elements and links are a elements; we do not style generic divs into interactive controls.
• Single H1 per page. Every page has exactly one top-level heading that names the page, followed by subsections that step down through H2 and H3 without skipping levels.
• Sufficient color contrast. Body text, headings, and interactive controls meet or exceed the 4.5:1 contrast ratio required by WCAG 2.1 AA for normal text, and 3:1 for large text and non-text UI components.
• Keyboard navigation. Every interactive control on the site (links, buttons, form fields, the GitHub App install link on intake) is reachable and operable using only the keyboard. Focus order follows the visual reading order, and focus indicators are visible against the page background.
• Descriptive link text. Links describe their destination in their own text ("Read the Data Processing Agreement", "Estimate your credit"), not generic "click here" or "read more." Link text on its own is meaningful out of context, which matters for screen-reader rotor navigation.
• Skip link. A "Skip to content" link is the first focusable element on every page so keyboard and screen-reader users can bypass the primary navigation and land directly in the main content region.
• Labeled form controls. Every form field on the contact form and intake form has a programmatically associated label. Required fields are marked with the standard required attribute, not by color alone.
• Live regions for form status. Form submission status (sending, sent, retry) is announced through aria-live regions so screen-reader users hear the result without having to hunt for it.
• Responsive layout. Pages reflow to fit small screens and large screens without horizontal scrolling at standard zoom levels, and text remains readable at 200% zoom.
• No autoplaying media, no carousels, no modals on load. The site is text and static images. There are no pop-ups, no chat widgets, and no automatically-playing video.

No known significant issues. If you encounter a barrier, please tell us via the contact form. We treat every accessibility report as a defect, not a feature request, and we fix barriers in priority order behind active customer engagements.

A small number of third-party documents linked from the site (for example, sub-processor privacy policies linked from the subprocessors page) are outside our control. We choose vendors who themselves take accessibility seriously, but their compliance is theirs to maintain.

If you encounter an accessibility barrier on rdbinder.com, please report it through the contact form with subject "accessibility". Helpful detail, if you have it: the URL of the page, the browser and assistive technology you were using, and a short description of what did not work. A screenshot is welcome but not required.

We commit to:

• Acknowledging your report within one business day. You will hear back from a human that we received it.
• Responding substantively within five business days. Either with a fix, a planned fix date, or a clear explanation if we believe the behavior is correct and the misunderstanding is on our end.

We do not use a contact email address for accessibility reports because the contact form routes directly to a human inbox and the form fields ensure we have the context we need to respond quickly.

We review this site against WCAG 2.1 AA on a rolling basis whenever we ship a new page or a material change to an existing page, and at minimum once per year. The review combines automated tooling (axe-core, Lighthouse) with manual keyboard-only and screen-reader passes on the primary user flows: estimate, sample, pricing, order, intake, and contact.

This statement reflects our practices as of the date below. We update it whenever the practices materially change.

Last reviewed: May 10, 2026. Cadence: at least annually, and on every material change.