Skip to content
LingravelixMultilingual websites, planned properly

Policy

Accessibility statement

Lingravelix works towards conformance with WCAG 2.2, the W3C accessibility guidelines, at Level AA. This statement lists the tests carried out before publication, the tests not yet done, and how to tell us about a barrier. It describes only checks that were actually made.

The target

WCAG 2.2 Level AA is the target for every page and tool on this site. Because the site is about multilingual websites, two criteria get particular attention: every page declares its language, which is success criterion 3.1.1 1, and passages in other languages, such as the sample phrases and language names, carry their own language attribute, which is criterion 3.1.2 2.

Tests carried out

These checks were run on the published build in November 2026 with an automated browser, Chromium, driven by test scripts:

  • Keyboard. Every page was walked with the Tab key from top to bottom, confirming that every link, button and form field is reachable in a logical order and that focus is always visible, with a focus outline measured at no less than 3:1 contrast against its background.
  • Contrast of text. Computed contrast of visible text against its background was measured on every page at several screen widths, against the 4.5:1 threshold for normal text and 3:1 for large text.
  • Narrow and wide windows. Every page was loaded at widths from 360 to 1,440 pixels and checked for content that forced horizontal scrolling.
  • Target size. Buttons, form fields and links outside running text were measured at no less than 24 by 24 pixels, with buttons 44 pixels high or more. Links inside sentences rely on the WCAG exception for inline text.
  • With scripts switched off. Every page was loaded with JavaScript switched off to confirm that content and navigation remain available.
  • Tools. Each of the four tools was operated with the keyboard alone, including entering data, running the calculation and reaching the results.
  • Markup. Every page was checked for a single main heading, a language attribute, labelled form fields and captions on data tables.

Tests not yet done

Screen reader testing and testing with disabled people are still outstanding, and this statement records that gap until both are done.

Known limitations

  • The hero area of the home page and the language demo contain short Arabic text samples. They are marked with the correct language and direction, but their wording has not been checked by a fluent reader, which is why they are labelled as samples.
  • Some decorative illustrations are drawn in code and hidden from assistive technology; everything they suggest is also said in words.

Design choices that support accessibility

  • Body text is set at about 17 pixels and resizes with browser settings.
  • Links in body text are underlined.
  • Animations are minimal, and transitions are switched off when your system asks for reduced motion.
  • Form errors from the contact form are announced in text, not by colour alone.
  • The language switcher examples in the guides use language names, not flags.

Reporting a barrier

Write to hello@lingravelix.site, or use the contact page, whenever part of this site gets in your way. Please include the page address and a short description of what happened, and, if you are willing, the browser and any assistive technology you use.

Related

The editorial policy explains how corrections are handled, and the privacy notice explains what happens to the details you send.

Sources

  1. WCAG 2.2 explainer for 3.1.1 (page language) W3C WAI, primary source
  2. WCAG 2.2 explainer for 3.1.2 (language of passages) W3C WAI, primary source