Accessibility Statement

3.1Keyboard operation

In plain EnglishEvery control is built to be reached and worked with a keyboard, including both menus and the search palette. Where that falls short is listed under known limitations.

No control on the site is built so that it needs a mouse, a hover, a drag or a gesture, and every page was driven with the keyboard alone before this statement was written. The header menu opens on hover for a pointer, but it also opens from the keyboard, and everything it contains is reachable without it. What that testing does not cover is set out in clause 4, and the keyboard problems Troy already knows about are in clause 6.1.

The site draws a small cursor that follows the system pointer on large screens. It never replaces the system pointer and never hides it, so pointer settings such as a large or high-contrast cursor keep working. It is not drawn at all under reduced motion, on a touch screen, or below 1280 pixels wide.

3.2Visible focus

In plain EnglishYou can always see where you are.

One rule in the site's stylesheet gives every focused control a three-pixel outline in the accent colour, set two pixels clear of the control so it is not lost against a border. It is applied on focus-visible, so it appears for keyboard and other non-pointer input without flashing on every mouse click.

No rule anywhere in the site removes an outline. The focus ring is one of only four jobs the accent colour is allowed to do on this site, which is why it is never mistaken for decoration.

3.3Forms, labels and errors

In plain EnglishEvery field has a real label, and an error says which field and what to do about it.

There is one form on the site: the brief at /start. It is built from native controls — text fields, radio groups, checkboxes and one form element — so arrow keys, Space and Enter work the way the browser and any assistive technology already expect.

• Every text field has a label tied to it. Every group of radios or checkboxes sits in a fieldset with a legend, so the group's question is read with each option.
• Help text and error text are tied to the field they belong to, so they are read out with it rather than stranded.
• A field that has failed is marked as invalid, and the group carries that state too.
• The browser's own validation is turned off so the messages are Troy's own words. An error names the field and says what to do, not that something is wrong.
• When a step fails, focus moves to the first field that needs fixing. When a step is completed, focus moves to the heading of the new step, so a screen reader is told where it now is.
• Going back never loses an answer. The whole form is held in one place in memory, so a correction does not cost you the rest of the brief.
• The last step shows exactly what will be sent, in full, before anything is sent.
• The form's spam trap is hidden from sight, hidden from assistive technology and taken out of the tab order, so it cannot catch a person who is tabbing through.
• Nothing typed into the form is written to browser storage, and no personal detail is ever put into a page address.

If the brief cannot be delivered, the form says so rather than showing a success it has not earned, and offers the same brief already written out as an email you send from your own program. That fallback is also the answer in clause 11.

3.4Colour and contrast

In plain EnglishStatus is always in words as well as colour, and the colours are measured rather than assumed.

• Status is never carried by colour alone. Every availability marker on the site pairs a coloured pip with the words — "Available now", "Waitlist", "Invite-only from 2027", "Draft · not in force" — and the words are what carry the meaning.
• Charts, dials, bars, markers and selected states are drawn in the text and line colours, not in the accent, so nothing depends on telling one hue from another.
• Meaning is not carried by shape or position alone either: every step, pip and state has a text label.
• The design reference page at /design measures contrast at runtime from the live theme rather than from a specification. It reads the colours the browser has actually resolved, flattens translucent colours onto whatever is behind them, and grades each pair for the job it does — 4.5:1 for body text, 3:1 for a graphical object. Switch the theme or the accent and every badge re-grades itself.
• Two colours in the system were set by that measurement rather than by taste, after they were caught failing.

The last two rows of that table do not meet the target. They are not hidden here: they are set out as defects in clause 6.2.

3.5Headings, landmarks and tables

In plain EnglishThe page has a shape you can move through without seeing it.

• Every page has one first-level heading in its opening block, a second-level heading for each section, and third-level headings inside. Levels descend in order and are not chosen for their size.
• These legal documents work out each clause's heading level from how deeply the clause is nested, so a level can never be skipped by accident, however the document is edited.
• Every page puts its content inside a main landmark. The header is a navigation region named "Primary". Each column of the footer is its own named navigation region.
• Every section is tied to its own heading, so moving by region announces what the region is.
• Tables are real tables, with a caption, column headers and a row header on the first cell of each row.
• Decorative marks — the moving line, the rules, the numbers beside a heading, the image plates behind a menu — are hidden from assistive technology, because the text beside them already says what they mean.

3.6What gets announced

In plain EnglishA result is announced once, when it has settled.

• A settled result is announced through one polite live region: that the brief is being sent, that it has been copied, that it has been received.
• A failure is announced through an assertive region, which is present on the page from the start so that the message is announced when it arrives rather than being missed.
• The moving line that runs across the site shows progress visually and is not announced. Announcing a progress animation frame by frame would bury everything else.
• The step indicator on the brief marks the current step as the current step, and each step's button is named with its number, its name and its state, so it is not read as a bare digit.

3.7Motion, and turning it off

In plain EnglishIf your system asks for less motion, the site removes the motion and the content is still complete.

Reduced motion is not bolted onto each component, where a component could forget it. The site's duration and distance values themselves collapse, so there is nothing left for a component to animate with.

• Every animation and transition duration becomes one millisecond, and every travel distance becomes zero.
• A rule applied to every element on the page catches anything that animates outside those values, and turns off smooth scrolling.
• The smooth scrolling that otherwise takes over the scroll wheel never starts, so the page scrolls the way the browser normally scrolls.
• The cursor that follows the pointer is never drawn.
• The one video on the site never plays. Its still frame stands in for it, which is what it was designed to do.
• Anything animated from code checks the setting and shows the finished state immediately.

Nothing on the site is conveyed only by movement. Every animated element has a still state that reads correctly, including the four states of the moving line: idle, carrying, resolving and live. Nothing on the site flashes.

One thing does move on its own without being asked to: the ribbon of words on the home page scrolls sideways continuously, and its speed and direction follow your scrolling. A reduced-motion setting stops it and turns it into an ordinary sideways scroller. Without that setting the only thing that stops it is resting a pointer on it, which is not a way anyone can reach from a keyboard or a touch screen. That is a defect, and it is set out in clause 6.6.

The design page at /design carries a Motion control that switches the same reduced mode on for testing, so the fallback can be checked from the page rather than from system settings. A fallback nobody can easily test is a fallback nobody has tested. That override is deliberately never saved: it lasts as long as the page, and the system setting always wins over it.

3.8Appearance controls

In plain EnglishYou can switch between the dark and light themes from any page, and change the density on the design page.

• There are two themes, dark and light. Both are complete: no colour on the site assumes one or the other.
• The theme can be switched from the command palette on any page, with the keyboard shortcut or the named button in the header.
• The design page at /design carries controls for theme, density, motion and accent colour, each a group of buttons with a proper label and a pressed state.
• Density changes the height of controls, the padding of rows and the spacing of sections. There are three. Comfortable, which is what the site opens with, gives 44-pixel controls. The one named Default gives 36. Compact gives 28.
• The choice is stored by the browser it was made in and applied before the page first paints, so switching does not cost you a flash of the wrong theme.
• The motion override is the one setting that is never stored, because a motion preference belongs to the system rather than to this site.

The site opens in its dark theme and does not read the operating system's light or dark preference. That is a limitation, not a decision anyone should have to like, and it is recorded in clause 6.5.

3.9Target size, text size and small screens

In plain EnglishControls are large enough to hit, text scales with your browser setting, and the page works on a phone.

• At the density the site opens with, buttons, form fields and the other standing controls are 44 pixels tall, which is more than the target asks for. A link inside a sentence is the height of the sentence, as links normally are.
• Every text size on the site is set relative to the browser's own text size, so raising the text size in the browser raises it everywhere, including labels and figures.
• Zoom is not disabled. The page can be pinched, zoomed and scaled like any other.
• Every page is built to work at 375 pixels wide with no sideways scrolling of the page itself. Long labels wrap rather than forcing the page wider.
• Layouts of more than one column collapse to a single column below roughly 860 pixels.
• Hovering is never required to reveal something that is not also available another way, and a panel opened by hovering can be dismissed with Escape and stays open while the pointer is over it.

6.1Menus, dialogs and skipping the header

In plain EnglishThere is no skip link, and the mobile menu says it holds focus when it does not.

• There is no skip-to-content link. Every page puts its content inside a main landmark, which a screen reader can jump to directly, but someone using a keyboard without a screen reader has to tab past the header's links on every page.
• The menu sheet on small screens is marked as a dialog, but focus is not actually held inside it and the page behind it is not disabled. Focus is moved to its Close button when it opens, and returned to the Menu button when it closes, so it is not a trap in either direction — but Tab can walk out of it into a page that is still there. The command palette and the other dialogs on the site do hold focus properly.
• The header's menu panel cannot sit next to its button in the page structure, for a reason to do with how the header draws itself over the page. It is tied to the button by name and Tab is steered by hand, but a screen reader reading the page in order meets the panel away from the button that opened it.
• The command palette's shortcut is Command and K, which some browsers and some assistive technology already use. The named button in the header is the way around that, and it is always there.

6.2Contrast that does not meet the target

In plain EnglishTwo colour pairs fail. Here they are.

• The label on a primary button measures 3.0:1 against the button's fill, at the default accent. The target asks for 4.5:1 at that text size. Every primary button on the site is affected, which includes the main action on most pages.
• The faintest text colour measures 3.3:1 in the dark theme and 2.7:1 in the light theme against the page background. It is used for captions, dates and supporting labels. It is below the target in both themes, and further below it in light.
• The header inverts itself over whatever is beneath it rather than switching colour. Over a mid-grey image the result can be low contrast, and nothing measures it, because there is no single pair of colours to measure.
• The smallest label on the site is set at about eleven pixels at the default browser text size. WCAG sets no minimum text size, and the label scales with the browser's text setting, but it is small.

Troy treats these as defects rather than as design choices. Nothing in this clause commits Troy to a date for fixing them, because clause 10.2 explains why Troy is not putting timings in this document yet.

6.3Product previews, decorative content and reveals

In plain EnglishThe mock product screens are hidden from screen readers on purpose, and the reason cuts both ways.

• Several pages show mock product screens: a score dial, an agent console, an approval queue, a change log, a tour of the platform. All of them show illustrative data and no real account, and each is labelled "Product preview".
• Where the words around a preview already carry its meaning, the preview itself is hidden from assistive technology and is not read out. That is deliberate. Reading a decorative mock dashboard aloud, cell by cell, is worse than skipping it.
• The cost of that decision is that someone using a screen reader gets the meaning and not the picture. If a preview is carrying something the surrounding words do not say, that is a defect in the page, and clause 10 is how to tell Troy about it.
• Images on the site are decorative grey plates. The one video has no speech and carries no information; it is muted, hidden from assistive technology, kept out of the tab order, and never plays under reduced motion. It has no captions because it has nothing to caption.
• Content below the first screen starts invisible and appears as it scrolls into view. Under reduced motion it appears at once instead of sliding, but it is still hidden until it is scrolled to. It is hidden by transparency rather than being removed, so a screen reader reaches the text before it becomes visible — which means a sighted person using magnification can be told about text that has not yet appeared.
• If the page's code does not run, or does not finish within four seconds, nothing is hidden at all and the whole page is visible. That fallback is deliberate.

6.4Small screens, wide tables and density

In plain EnglishSome tables are wider than a phone and scroll sideways inside their own box.

• Long comparison tables — the plan comparison, the permission matrix, the tables in these legal documents — are wider than a phone screen. They scroll sideways inside their own area rather than shrinking. The area is focusable and named so it can be scrolled with a keyboard, but a table read a screen at a time is harder to follow than one that fits.
• At the compact density, controls are 28 pixels tall, below the 44 the site aims at. Compact can only be chosen from the design page, so nobody meets it by accident, but anyone who chooses it gets smaller targets.
• Some sections pin themselves while you scroll past them. They have not been tested with a screen magnifier, where a pinned element can cover the part of the page someone is reading.
• The design page at /design is a reference for the people building the site. It is dense by intention and it is not written for a general reader.

6.5Theme, contrast preferences and what the site ignores

In plain EnglishThe site opens dark whatever your system asks for, and it ignores a request for higher contrast.

• The site opens in its dark theme and does not read the operating system's light or dark preference. Someone who has asked their system for a light interface gets a dark page until they change it.
• The theme can be changed from the command palette on any page. Density, motion and accent can only be changed on the design page, which is a reference page rather than part of the site's navigation.
• The site does not respond to a system request for increased contrast, and has no rules for forced-colours or high-contrast modes. In those modes the result is whatever the browser decides, and Troy has not looked at it.
• A stored preference lives in the browser it was set in. It does not follow you to another browser or another device, and it is cleared if you clear the site's data.

6.6Content that moves on its own

In plain EnglishOne ribbon of words on the home page scrolls by itself, and the only way to stop it is to hold a pointer over it.

• The home page carries a ribbon of words that scrolls sideways continuously from the moment the page loads. It does not stop by itself, and its speed and direction follow your scrolling.
• It stops while a pointer rests on it. That is the only way to stop it, so it is no use to someone working from a keyboard, from a touch screen, or from speech or switch input. There is no button to pause it and no setting on the site that turns it off.
• A system reduced-motion setting does stop it: the movement is removed and the ribbon becomes an ordinary sideways scroller. For anyone who has that setting on, this limitation does not arise.
• The ribbon carries six words naming the kinds of work Troy does, and nothing that is not said in ordinary text on the pages those words lead to. It is not the only route to any of it. That does not settle the problem: a line of text moving beside what you are reading can make the rest of a page harder to get through whether or not it carries anything new.
• Troy treats this as a defect rather than as a design choice. Nothing in this clause commits Troy to a date for fixing it, for the reason clause 10.2 gives.

10.1How to report a problem

In plain EnglishOne address, and nothing you have to prove.

Write to troy@louin.io and put the word Accessibility in the subject line, so it is not lost among everything else that address receives.

Any of the following helps, and none of it is required:

• The address of the page.
• What you were trying to do.
• What happened instead.
• The browser you used, and if you use assistive technology, which one and roughly which version.
• Whether it happens every time, or only sometimes.

You do not have to prove anything, cite a guideline, name a criterion or use any particular words. A message that says only "the menu does not work with my keyboard" is a useful message. Send it.

10.2What Troy does with a report

In plain EnglishA person reads it and a person replies. Troy will not tell you how fast.

• A person reads it. Troy does not put an automatic reply in the place of an answer.
• A person replies to you, in their own words. Not a ticket number and not a form letter.
• If Troy can reproduce the problem, it says so, and says what it is going to do about it.
• If Troy cannot reproduce it, it says that too, and asks you for what it needs rather than closing the matter.
• If it is a real problem that Troy is not going to fix soon, Troy says so plainly, and the problem is added to clause 6 of this statement at the next version. That is what that clause is for.
• Whatever the answer about the site, Troy sends you by email, at no cost, whatever is on the site that you were trying to reach. See clause 11 for what that covers and what it does not.
• Troy does not ask you to sign anything, to accept terms, or to use a different product in order to be helped.

If you are not satisfied with Troy's answer, you may be able to take the matter further. Which route is open to you depends on where you live and on which law applies, and clause 9 names the ones that may be relevant. In Ontario, a complaint about discrimination in services goes to the Human Rights Tribunal of Ontario under the Human Rights Code, while the Accessibility for Ontarians with Disabilities Act is enforced by the province rather than through individual complaints. Those routes have time limits, and the law sets them rather than this statement: an application to the Human Rights Tribunal of Ontario has its own deadline under the Code, and Ontario's Limitations Act, 2002 sets a basic two-year limit for most civil claims, running from when the claim was discovered. If you are thinking about either, check the limit that applies to you rather than relying on this paragraph. All of that is a description of the routes, not advice about yours, and nothing in this document is a condition of using any of them.