LetterForgeUSA is meant to be usable by everyone, including people who use a keyboard, a screen reader, magnification, voice control or a small phone. This statement describes the standard we work to, what has been implemented, what we know still falls short, and how to tell us when something does not work for you.
Standard
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across the public site and the letter editor. Conformance is checked by the site’s own team with automated checks during development (every built page is checked for one main heading, a title, a description, working links and landmark regions). Manual keyboard and screen-reader testing has not yet been completed, we have not commissioned an independent audit, and this statement is not a certification.
What has been implemented
- Keyboard operation. Every link, button, form field, menu, dialog, tab and step in the letter editor can be reached and operated with a keyboard alone, in a logical order. Dialogs (including the privacy preferences dialog) trap focus while open, close with Escape and return focus to the element that opened them.
- Visible focus. A clear focus indicator is shown on every interactive element and is not removed by styling.
- Labels and instructions. Every form field has a visible, programmatically associated label. Required and optional fields are marked. Help text and examples are linked to their fields so assistive technology announces them. Validation errors are listed in an error summary that receives focus and are repeated next to the field.
- Contrast. Text and essential interface elements meet the WCAG AA contrast ratios in both the default and dark color schemes. Color is never the only way information is conveyed.
- Text size and spacing. Body and input text is 16px or larger. The layout is built to tolerate 200 percent zoom and increased text spacing without loss of content or function; this has not yet been verified across browsers.
- Touch targets. Buttons, links in menus and form controls have a target size of at least 44 by 44 CSS pixels where practical.
- Small screens. The site works at a viewport width of 320 CSS pixels with no horizontal page scrolling. The editor switches to a single column with Edit and Preview tabs on narrow screens.
- Structure. Each page has one main heading, a logical heading outline, landmark regions and descriptive link text. Every page except the homepage and the error page has breadcrumbs. Tables used for payment or deposit figures have header cells.
- No reliance on JavaScript for reading. All public content (tool explanations, guides, category pages, policies and sources) is readable with JavaScript disabled. The interactive editor requires JavaScript, and the page says so when it is not available.
- Motion and timing. The site uses no auto-playing media, no carousels and no time limits. Nothing flashes.
- Consent banner. The privacy banner does not cover controls, does not block scrolling, and is fully operable by keyboard and screen reader.
Known limitations
- PDF export tags. Downloaded PDF files contain selectable, searchable text but are not yet tagged PDFs; headings, lists and reading order are not marked up for assistive technology inside the PDF. The Word (DOCX) export preserves heading and list structure and is the better choice for screen-reader users. We intend to add PDF tagging and will update this statement when it ships.
- Third-party advertising. On pages where advertising is shown, the content inside the labeled advertising region is supplied by third parties and is not under our control. We reserve a minimum space for it to reduce layout movement; live placement still needs testing, and we keep it away from controls, but we cannot assure the accessibility of the advertisement itself.
- Official sources. The site links to court, library and agency pages whose accessibility we do not control.
- Testing coverage. So far the site has been checked with automated build-time checks. Manual testing with screen readers, physical mobile devices and a range of browsers has not yet been completed. Combinations we have not tested may behave differently; please tell us if you find one.
Report an accessibility problem
If any part of the site is difficult or impossible for you to use, please let us know through the contact page. It helps to include the page address, what you were trying to do, the browser and assistive technology you were using, and what happened. We will reply, and where the fix is in our hands we will treat it as a correction under the editorial policy and schedule it promptly. If you need the content of a page or a sample letter in another format in the meantime, ask and we will do what we reasonably can.
This statement was last reviewed on the date shown at the top of the page and is updated when the implementation changes.