Accessibility of this documentation

This page is about this help site — the pages you are reading now, in your own browser. It makes no claim about the FriendTrack app: whether a particular screen inside the app works with a screen reader is a separate question, and this page does not answer it.

What this site claims about its own pages

Six things are true of every page here, and only these six.

Every image carries a text equivalent, and no image is load-bearing. A page is complete, correct and followable with every image removed. A picture may only confirm something a sentence has already said.
No instruction identifies a control by colour or shape alone. Where a page tells you to press something, it names that thing by the words printed on it.
Heading structure is navigable. One top-level heading per page and no level skipped, so a page can be read by moving from heading to heading.
Every link says where it goes. No “click here” and no “read more”: a link read on its own, lifted out of the sentence around it, still names its destination.
Every table has a header row. No page here uses a table for layout.
Every diagram has a text equivalent. Where a page draws something, the same information is also written out in prose on that page.

That is the whole claim.

Why it is a list and not a standard

This is not a conformance statement. This site does not claim conformance to WCAG or to any other accessibility standard, and it does not claim to be free of barriers.

Each of the six above is a property of the text a page is written in rather than a judgement about it, so any of them can be re-checked against the page itself at any time and found false. A conformance claim that nobody can re-check is worth less than a short list that holds, which is why a clause that could only be judged is not on the list.

And all six are checked automatically. Every one of them is asserted against the source of every page here, by a test that runs before a change to this site can be published. A page that breaks a clause fails by name and does not go out. That is the reason the list is six things and not sixty: each had to be something a machine could be pointed at.

What that does not mean is that this site is free of barriers. Six clauses that hold are six clauses that hold.

What the claim does not cover

The six are properties of the page text. They say nothing about the following, and nothing above should be read as covering them.

Colour contrast as your browser renders it, under your own theme and settings.
Keyboard focus order, visible focus, and keyboard traps.
The page frame — the navigation, the sidebar and the search results list. That markup is generated by the site builder and its search index rather than written page by page here.
Reduced-motion behaviour, and behaviour at high zoom or at a narrow window width.

A one-off audit of the rendered site covering exactly these points was carried out on 4 September 2026, against the published pages in a desktop browser, in both themes, at window widths from 320 pixels up. It was a single pass, made by hand and by tooling on that day; it is not repeated when the site is republished, and nothing below is a standing guarantee. What it found and did not fix is listed under known exceptions. What it observed and left as it was:

Contrast. Every text pairing measured on the day met 4.5:1 in both themes, including the search results and the two diagrams. Non-text lines that fell short — the diagram connectors on the dark theme, the border of the search field — were corrected.
Keyboard. There is one tab order: the skip link, the header, the navigation, the page outline, then the text. Every stop showed the browser’s own focus ring. Nothing trapped the keyboard; the search dialog holds focus while open and releases it on Escape.
Headings. Every page had one top-level heading and no skipped level as rendered. The frame adds one heading of its own, On this page, which a screen reader moving by headings meets before the page title on a wide window.
Reduced motion, zoom and width. With reduced motion requested, nothing on the site animates. At 320 pixels wide no page scrolls sideways and every table fits. At 200% zoom the pages fall into a single column.

Known exceptions

Written as observations rather than verdicts, so that each one can be re-checked later instead of being taken on trust.

The search field is named Search through a tooltip attribute and its placeholder text, and by the dialog that contains it. There is no label element attached to it. A screen reader announces it as a search box called Search, which is accurate; what is missing is a label a sighted reader can see once the placeholder has been typed over. The field is the search library’s own markup, which this site does not write, and the library’s maintainers closed the request for a label by adding the tooltip attribute. Recorded as it was found on 4 September 2026.

Search results are not announced

Typing in the search box draws the results and a line such as 58 results for sharing above them. Neither the line nor the list is marked as a live region, so a screen reader is told nothing when the results change, and nothing when a search finds no results. The reader has to move out of the field to discover what happened. This too is the search library’s markup. Recorded as it was found on 4 September 2026.

Each search result begins with the same link twice

A result is a page title, linking to the page, followed by the headings within that page where the search term appears, each linking to its section. The first of those is always the page’s own title again, linking to the top of the same page, so a reader moving link by link hears every result’s title twice in a row. The search library’s markup, recorded as it was found on 4 September 2026.

The product’s design specification over-claims its own contrast

The FriendTrack design specification states that all of its colour combinations meet WCAG AA contrast. Measured, three of them do not: #5B4FCF is 3.16:1 against the dark page background, which is enough for a non-text element and not for text, while #2EC4B6 is 2.17:1 and #FFB347 is 1.78:1 against white. This site uses none of the three for text — link text on the dark theme is #5DD9CE at 11.19:1 — so the pages here are unaffected. What is wrong is the wording of the specification, and it is recorded here because a reader comparing the two documents would otherwise find a contradiction with no explanation attached to it.

Clause 1 is now exercised, by three images

Until recently there was not a single picture on this site and clause 1 was true of nothing. There are now three, all on the calibration pages, and all three screenshots of the venue-map editor: the Calibration tab’s side panel, the accuracy overlay switched on over a venue image, and the GPS preview with two projected test points on it.

Each one carries alt text naming what it shows, and each of those pages was written to stand without it — remove any of the three and the page it sits on still says everything it said before, because what a picture carries here is also written in the prose beside it.

There are no pictures of the phone app anywhere on this site, and that is a decision rather than a gap: no page here asks a reader to recognise a screen from an image of it.

The claim covers the pages, and the pages are now written

When this page was first published there were four pages on this site, one of which was a placeholder. There are now around ninety, covering the phone app and the venue-map editor. The six clauses were asserted over the small set and are asserted over the large one, and nothing about them was relaxed to fit; what changed is that they are now being exercised by real headings, real tables, real links and real diagrams rather than by four files.

This site is republished continuously and is not a dated certificate

There is one always-current set of pages, republished as the product changes. The claim above describes the pages as they are published now. It is not archived, it is not dated, and an older state of this site cannot be appealed to.

Report a barrier

If something on this site is unreachable, unreadable or unusable for you, please write to support@friendtrack.net.

It helps to say which page it was, what you were reading it with — a screen reader, the keyboard alone, zoom, your own stylesheet — and what happened instead of what you expected. This site records nothing about who reads it or what fails on it, so a barrier nobody describes leaves no trace at all, and one clear description is the whole of the evidence.