Accessibility statement

Version 1.0-draftDraft prepared 30 September 2026

On this page

Tractrix wants everyone, including people with disabilities, to be able to use the Tractrix website, its documentation and Tractrix Cloud. This statement describes the standard we work to, what we know does not yet meet it, and how to tell us about a barrier.

1. Scope

2. Standard and legal framework

  • We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.
  • This is also the benchmark of the harmonised European standard EN 301 549 (V3.2.1) for web content and software, used to presume conformity with the European Accessibility Act (Directive (EU) 2019/882), which has applied to new services since 28 June 2025.
  • In the United States, we take the ADA and Section 508 into account; in the UK, the Equality Act 2010.

3. Conformance status

The website and Tractrix Cloud are partially conformant with WCAG 2.2 AA: most content conforms, but the exceptions in section 4 do not yet fully conform.

Measures already taken include: semantic HTML with landmarks, headings and skip links; full keyboard operation of the navigation, menus, documentation and Cloud forms; visible focus indicators; colour contrast of at least 4.5:1 for text in both light and dark themes; respect for the reduced-motion preference; layouts that work down to 360 px wide; labelled form controls and an accessible combobox for aircraft search; tables with captions and header cells; and text alternatives for diagrams.

4. Known limitations

  • Plan-view canvas (Tractrix Cloud). The interactive plan view is a visual, geometric representation of swept paths, envelopes and clearances. It can be panned, zoomed and animated with the keyboard, and drawing a path supports keyboard input, but the geometry itself cannot be fully conveyed to screen-reader users. Equivalent information is available in text: the pass/fail summary, the issues list, and the CSV, GeoJSON and HTML report exports.
  • Drawing a path by pointer. Placing vertices precisely is easiest with a pointer. As an alternative, you can pick an existing line from an uploaded drawing, or upload a path as GeoJSON or DXF.
  • Colour in results. Results use colour to distinguish layers; each layer also has a legend entry and a toggle, and pass/fail states are labelled with text.
  • Diagrams and screenshots in the documentation have short text alternatives; some complex diagrams do not yet have a long description.
  • DXF exports are CAD data intended for CAD software and are not accessible documents in themselves.
  • Mathematical formulae on the methodology page use MathML, whose support varies between browsers and screen readers.

5. How we assessed accessibility

6. Desktop products

Tractrix for QGIS uses the standard QGIS Processing dialogs, and the AutoCAD and Revit add-ins use standard Windows (WPF) controls with keyboard access and accessible names. Their accessibility also depends on the host application. Reports produced by the add-ins are HTML and follow the same principles as the website.

7. Feedback and alternative formats

8. Enforcement procedure