Accessibility

WCAG 2.2 AA is the standard we build against. We are not claiming conformance with it, because no independent audit has been carried out. Saying otherwise would be easy and untrue.

• •Every interactive control is reachable and operable by keyboard
• •Focus is always visible, and the ring is never removed
• •Every form input has a real label; hints and errors are associated with their field
• •Errors are announced through live regions rather than only appearing visually
• •Colours meet WCAG AA contrast, checked with an automated scan of every page
• •Bio page blocks can be reordered with buttons, not only by dragging, and each move is announced
• •Bio page colours come from checked palettes, so a published page can't end up with unreadable contrast
• •Reduced-motion preferences are respected throughout
• •Every page has a skip link and a single main landmark

No screen reader testing has been carried out with people who use one daily, which is the only test that really counts. No audit by an accessibility specialist. No testing with voice control or switch access.

Email support@linkmint.org or use the contact form. Say what you were trying to do, what got in the way, and what you were using. That's usually enough to reproduce it.

Accessibility problems are treated as bugs rather than as requests, which means they go into the same queue as anything else that stops the product working.