Accessibility.

The standard we target.

We aim to meet WCAG 2.1 Level AA. That is the level referenced by the European Accessibility Act and by Section 508 in the United States, and it is the level we hold ourselves to.

We describe ourselves as partially conformant: most of the service meets the standard, and the exceptions are listed below rather than left for you to discover.

What we have tested.

On August 3, 2026 we ran automated accessibility audits (axe-core, via Lighthouse) against the public pages of the site, and fixed what they surfaced. Pages audited:

• •Home page — no outstanding automated violations
• •Pricing — one known issue, listed below
• •Legal pages (privacy, terms, refund, cookies, acceptable use, security) — no outstanding automated violations

Issues found and corrected in that pass:

• •Muted body text and footer links sat at 3.4–3.5:1 contrast, below the 4.5:1 minimum. The colour was darkened site-wide so that all body text now clears AA against both background surfaces.
• •Inline link colour sat at 4.36:1 against the page background. It was darkened to 5.5:1.
• •Email links in the legal pages were distinguished by colour alone; they are now underlined, so the cue does not depend on colour vision.
• •The feature section on the home page skipped a heading level, which disrupts screen-reader navigation. The heading structure was corrected.
• •The pricing page had no main landmark, so screen-reader users could not jump straight to the content. One was added.

Known limitations.

We would rather tell you these than have you find them:

• •The pricing page still has a heading-order issue: one subheading skips a level, which can make the page harder to navigate by headings in a screen reader. The content is fully readable and all functionality is reachable.
• •The signed-in dashboard has not yet been through the same audit as the public pages. If you rely on assistive technology and hit a barrier there, please tell us — we will prioritise it.
• •Some interface copy uses colour to convey status. We are working through those cases to add a text or icon cue alongside the colour.

What we have not done yet.

Automated tools catch roughly a third of accessibility problems. They cannot tell you whether a flow actually makes sense to someone using a screen reader, or whether a control is reachable in a sensible order.

We have not yet tested Directd with disabled users, and we have not had an independent accessibility audit. We are not going to imply otherwise. When we do either, this page will say so and will name who carried it out.

Report a barrier.

If something on Directd is difficult or impossible for you to use, email contact@directd.app. It helps if you can tell us the page, what you were trying to do, and what assistive technology you use — but report it either way.

We aim to respond within five working days. If an accessibility problem stops you from using something you have paid for, contact us and we will sort out a refund — see our refund policy.