Accessibility statement
How accessible plugwith.me is, what we know is not yet good enough, and how to tell us when something blocks you.
Where we stand. We aim for WCAG 2.2 Level AA across the marketing site, the customer dashboard and the link pages our customers publish. We are partially conformant: most of it meets the target, and the known exceptions are listed in section 3 rather than hidden. This statement is self-assessed, not audited by a third party — we would rather say so than imply a certification we do not hold.
1. Scope
This statement covers everything served under plugwith.me: the landing page and blog, the legal documents, the signup, login and dashboard pages, and the public link pages at plugwith.me/<slug>.
It does not cover the destinations our customers link to. Those are third-party sites we neither operate nor control — see section 6 of the Imprint.
2. What we do
- Alternative text — the link editor and the model editor both ask for a description of the avatar, and it is what a screen reader announces. Left empty it falls back to the profile or model name, which for a portrait used as a profile picture is the accurate description rather than a placeholder.
- Semantic markup and landmarks — real headings in order,
<main>,<nav>and<footer>regions, and labelled forms, so a screen reader can navigate by structure rather than by guessing. - Keyboard operability — every control, including the age gate, the password gate and the privacy consent notice, is reachable and operable by keyboard, with a visible focus ring (
:focus-visible) that we do not remove. - Contrast — body text and interactive controls are chosen against the dark background to meet the 4.5:1 minimum; large headings meet 3:1.
- Text that scales — relative units throughout, no maximum-scale lock on the pages we control, and layouts that reflow at 320 px without horizontal scrolling. Wide content such as the tables in our legal documents scrolls inside its own container rather than forcing the page sideways.
- Reduced motion — animations are suppressed under
prefers-reduced-motion, including the background video a customer can put on their link page: it is paused on its first frame rather than looping. - No time limits — nothing on our own pages expires while you read it. The one timed behaviour is the redirect on a direct link, which is the function you asked for by opening the link.
- Works without JavaScript for the legal documents: the table of contents is an enhancement, and every document is complete and readable with scripting off.
- Print — the legal documents have a dedicated print stylesheet, because people file contracts on paper.
3. Known limitations
We would rather list these than let you discover them:
- Customer-configured link pages. Customers choose their own background image or video, avatar and button labels. We cannot guarantee the contrast of a page whose background someone else picked, and we cannot write alternative text for an image we have never seen. We supply accessible defaults and the customer can undo them.
- Background video contrast. Where a customer enables one it no longer plays for visitors who have asked for reduced motion — it is paused on the first frame and used as a still image. What we still cannot guarantee is the contrast of text over a video someone else chose.
- The in-app-browser hand-off can move a visitor between applications abruptly. That is the product's core function and cannot be removed, but the "Continue" step on Meta's iOS WebView is a real button and is keyboard- and screen-reader-operable.
- No third-party audit. Everything above is self-assessed against WCAG 2.2 AA by manual keyboard and screen-reader testing plus automated checks. We have not commissioned an external conformance evaluation.
4. Tell us about a barrier
If something on plugwith.me blocks you, write to info@ponyagcy.com with "Accessibility" in the subject. Tell us the page, what you were trying to do, and what assistive technology and browser you use if you know.
We answer within 5 business days. If we can fix it quickly we do; if not, we tell you what we will do and by when, and we offer an alternative way to get the same result in the meantime — including doing it for you by email where that is the honest answer.
5. Regulatory position
European Union. Directive (EU) 2019/882 (the European Accessibility Act) has applied to e-commerce services since 28 June 2025. Article 4(5) of that Directive exempts microenterprises providing services from its requirements. plugwith.me is operated by a microenterprise — fewer than 10 persons and an annual turnover and balance sheet total below EUR 2 million — and is therefore exempt from the Act's obligations. We publish this statement and work to WCAG 2.2 AA anyway, because the exemption is about paperwork and enforcement, not about whether people can use the product. If we outgrow the exemption we will say so here and commission a proper evaluation.
Germany. The Barrierefreiheitsstärkungsgesetz (BFSG) transposes the Directive and carries the same microenterprise exemption in § 3(3).
United States. We aim at WCAG 2.2 AA as the reference standard commonly applied under Title III of the Americans with Disabilities Act and Section 508. We make no representation of certified conformance.
Nothing in this section limits your right to contact us about a barrier, or our commitment in section 4 to deal with it.
6. Review
We review this statement whenever the interface changes materially, and at least once a year. It was last reviewed on 31 July 2026.