Our target for this site is WCAG 2.1, Level AA.

Done.

• Headings that never skip a level. One h1 per page, and the levels below it descend in order, so the heading list a screen reader offers is a usable table of contents rather than a scramble.
• A skip-to-content link. First stop in the tab order on every page, visible the moment it takes focus, so a keyboard user is not tabbing through the navigation on each visit.
• Visible focus indicators. Every link, button, and form control shows where focus is. We do not remove an outline without putting a clearer one in its place.
• Text contrast checked to AA. Every text and background pair in the palette is measured against 4.5:1 for body text and 3:1 for large text. The lightest greys in the palette are reserved for hairlines and decoration and are never used for body copy.
• No meaning carried by color alone. Where a status is shown, a word says what the color says. Links are underlined, not merely tinted.
• Resizable text. Type is set in relative units and survives browser zoom and text-only zoom; the layout reflows to narrow widths without a horizontal scrollbar and without cutting content off.
• Keyboard operability. Everything on the site can be reached and operated from the keyboard, including the mobile menu, which reports its own state and closes on navigation. There are no keyboard traps.
• No autoplaying media. No video, no audio, no carousel, no auto-advancing anything, nothing that starts on its own.
• No motion-triggered content. Nothing appears, moves, or changes because you scrolled or hovered. The only movement on the site is a short color or position change on hover, and it never carries information.
• Real text and a declared language. Content is live text, not pictures of text, and the page declares its language so a screen reader pronounces it correctly. Decorative icons are hidden from assistive technology; icons that carry meaning have a text label.

Not done, and stated rather than omitted.

• No third-party audit, no VPAT, no conformance claim. We have not commissioned an external evaluation and we do not publish an accessibility conformance report. If that changes, this page will say so and will say who did it.
• No third-party embedded content today. There is no video player, no map, no chat widget, no social embed, and no advertising on this site — so there is no component here whose accessibility we do not control. If one is ever added, it will be listed here with what we know about it.
• No PDFs published on this site today. Everything is HTML. If we publish a PDF, it will be tagged, and this page will note anything about it that falls short.
• Combinations we have not tried. Assistive technology, browser, and operating system combine in more ways than anyone tests. Something that works in our checks can still fail in yours. That is what the report route below is for, and a report is a favor to us rather than a complaint we tolerate.

The structure of your source comes across.

• Headings stay headings, lists stay lists, and table header cells stay table header cells. The reading order of the translated file follows the reading order of the source.
• Text is returned as live text — selectable, searchable, reflowable — not flattened into an image. Send a tagged PDF and you get a tagged PDF back.
• Alt text you supply is translated along with the rest of the document rather than left in English.
• Right-to-left scripts and CJK line breaking are set so the translated file reads and prints the way the source did, rather than arriving with reversed punctuation or broken lines.

The language is tagged, which matters more here than in English.

For web deliverables we return content with correct language attributes, so a screen reader switches voice and pronunciation instead of reading Spanish or Vietnamese with an English engine. Where a passage stays in the source language inside a translated document — a form name, a legal citation, an address — that passage is marked too. For document deliverables we set the document language. If you tell us your CMS strips attributes on paste, say so and we will give you the text in a form that survives it.

We flag what your source will carry into the translation.

Some accessibility problems are inherited. A scanned form is an image of text in every language. An untagged PDF is untagged after translation. Tables used for visual layout, images with no alt text, instructions that depend on color, and form fields without labels all reach the translated file intact. Where we see these, we tell you what we saw and what will not survive translation — before delivery, not after.

What we do not do is quietly fix them. Remediating a source document is a different job from translating it, we do not perform it as part of a translation, and we do not audit your source. We report; the decision and the work stay with you.