Accessibility
What is built, and what is still missing.
Atarla aims to meet WCAG 2.2 level AA on this site. That target is stated as an aim rather than a certification, because no independent audit has been done. The gaps below are listed with the same weight as the work, since a page that names only its strengths is not an accessibility statement.
Built and in place.
- Reading preferences
- The control in the header sets larger text, higher contrast and reduced motion. The choice is stored only in your browser and is never sent to Atarla.
- Motion
- Animation respects the operating system's reduced-motion setting, and the preference above overrides it either way, so you are not dependent on the OS to stop movement.
- Keyboard
- A skip link opens every page, and every interactive control shows a focus ring drawn to stay visible against the page, the dark sections and the orange button alike.
- Targets
- Interactive controls are at least 44 by 44 pixels, including the compact links in the utility bar and the footer.
- Structure
- Pages use a single main landmark and labelled sections, so headings can be used to navigate rather than scrolled past.
- Contrast
- Body and accent text meet WCAG 2.2 AA against the backgrounds they sit on. The accent used for text is a darker value than the accent used for fills, because the brand orange does not pass as text.
- Images and diagrams
- Meaningful images carry text alternatives, and the architecture diagram is marked up as an image with a title and a description rather than left as bare shapes.
- Language
- Every page declares its language, and the English and Spanish editions link to each other so assistive technology announces the right one.
Known gaps.
- No independent accessibility audit has been carried out, and no VPAT or conformance statement is published. The claims above are Atarla's own testing.
- Two comparison tables are built from div elements with table roles rather than native table markup, which weakens table navigation in some screen readers. This is being changed to native tables.
- Three statistic cards on the homepage present a label and a figure without their own heading, so they read as fragments out of context.
- The contact form validates in Atarla's own code and does not yet announce errors through a live region.
- Automated contrast and heading-order checks do not yet run in the build, so a regression would currently be caught by review rather than by the pipeline.
Report a barrier.
If something on this site blocked you, please say so, and describe what you were trying to do and what happened. Barriers reported this way are treated as defects, not as feedback. Tell us the browser and any assistive technology you were using if you can, but a plain description is enough.