Accessibility
Fieldmark®‘s product site is built to meet the Web Content Accessibility Guidelines (WCAG) version 2.1 at Level AA. When someone tells us we have missed it, we fix it.
What is covered
Two things, each with its own section: the product site at fieldmark.au, and the Fieldmark applications and Dashboard. The documentation site is not covered.
The product site
What is built in
Colour and contrast. The Fieldmark green, #669911, sits at roughly 3.4:1 against white, which is below the 4.5:1 that Level AA asks of body text. The site therefore uses the darker green #324C08 wherever green carries small text, and keeps the lighter green for large text, logos, and decorative fills.
Motion. Where the site animates anything, it honours the reduced-motion setting in your operating system and browser.
Speed on a poor connection. The site is built to load on a phone with weak reception: static pages, a budget on image weight, and no heavy scripts.
Text, structure, and keyboard use. Pages use real headings in order, text that resizes with your browser settings, descriptive link text, and alternative text on images that carry meaning. Everything you can do with a mouse you can do from the keyboard.
What we have not done
We have not commissioned an external accessibility audit of the site, and we do not hold a formal conformance certificate. Level AA is our target, but no third party has signed it off.
The Fieldmark applications and Dashboard
The same standard applies: WCAG 2.1 at Level AA. The Fieldmark app and the Dashboard do not fully meet it yet, and we are working towards it.
What is built in
Established component libraries. The Fieldmark app and the Dashboard’s Notebook Editor are built on Material UI, and the rest of the Dashboard on Radix UI. Both libraries implement the WAI-ARIA authoring patterns, keyboard interaction, and focus management in their components. Where we have combined those components in our code, the automated check found faults that the libraries do not prevent.
A declared language. The Fieldmark app and the Dashboard declare English, so a screen reader pronounces content with the right rules. The sign-in page they share does not yet.
What we are fixing
Our tests found faults in four main areas, and we are working through them.
Form labels. Each field’s label shows on screen but is not yet linked to its input, so a screen reader can announce a field without its label.
Button names. A few buttons that show only an icon, such as the app’s sync-status button, have no name for a screen reader to announce.
Alternative text. Some logos and icons have none, though each sits beside visible text.
Colour contrast. In places, including the app’s main buttons, links, and tabs, the Fieldmark green and orange fall below the contrast WCAG asks for small text. This site already uses a darker green for small text.
Testing so far
Automated testing. In September 2026 we tested the Fieldmark app and the Dashboard with an automated accessibility checker, at desktop and phone sizes and in the colours our deployments use. Automated checks find many faults but not all, so we treat the results as a starting point.
Keyboard and screen readers. The Dashboard is designed to be used from the keyboard, but we have not yet tested every function that way, and we have not yet tested the app with the screen readers built into phones and tablets.
Independent assessment. No third party has assessed the applications yet, and we do not yet publish a conformance report.
What we are doing about it
We ran our first accessibility tests on the Fieldmark app and the Dashboard in September 2026, and we are working through the faults they found. We will keep testing the applications and repairing what we find, with WCAG 2.1 at Level AA as our target.
Telling us about a problem
If you find something you cannot use, on the site or in the applications, that is a defect. Tell us which page or screen and what happened, and we will write back. We fix problems on this site promptly; problems in the applications join the faults we are working through.
Email [email protected].
Last reviewed: 16 October 2026