Language and Accessibility

The platform supports English and Spanish today. Visit Settings → Language and pick the one you prefer. Your choice is saved as a cookie on your browser and applies to every page from then on.

Some pages may still display English until their translations land — when that happens, the page shows a small notice at the top so you know you’re seeing the English fallback. Translations are added as they’re reviewed.

The HTML language attribute updates with your choice, so screen readers, browser translation tools, and other assistive technology know what language they’re reading.

The platform targets WCAG 2.1 Level AA. Every interactive control has a visible focus indicator, color contrast meets the minimum ratios for text, and information is never conveyed by color alone — status badges pair color with text, and error states include written explanations beside any colored borders.

Form fields are labeled with proper <label> elements and wired to their inputs via htmlFor, so screen readers announce what each field is for. Error messages reference the field they describe via aria-describedby.

Modals (when present) use the native HTML <dialog> element so the browser handles focus trapping and the Escape key — no custom keyboard scripting that might miss an edge case.

If something on the platform isn’t accessible to you — a button you can’t reach with the keyboard, a contrast issue, a screen-reader misread — please report it through your NA admin or directly through the project’s GitHub issues. Accessibility regressions are treated as bugs, not feature requests.