accessibility

last updated 16 september 2026

this describes lynxr as it is on the date above, not a permanent claim. it has not been audited by anyone outside the team, and it does not claim conformance with any standard — an independent audit has not been done. what it does instead is name the specific things that work and the specific things that do not, so you can tell before you sign up whether lynxr is usable for you.

what we aim at

lynxr aims at WCAG 2.2 level AA. that is the target, not a claim that we have reached it — the known gaps are listed further down, and they are listed rather than summarised because a general phrase like “we take accessibility seriously” tells you nothing you can act on.

what works today

each of these was measured on the built pages rather than assumed from the code:

• keyboard. every button, link, tab, disclosure and text field can be reached and operated with a keyboard alone, and every one of them draws a visible focus ring when you arrive by tab — a 2px outline that measures 7.9:1 against the page and follows the control's own shape, so it traces a capsule around a capsule and a rounded rectangle around a text box. sixteen text fields had no ring at all until 19 august 2026; that is fixed.
• controls that are only an icon still have names. the wait‑list submit is announced as “join wait list”, the arrow on a video card as “open the original video on TikTok” (or whichever platform it is), and a status chip that shows a short word on a small card keeps its full wording as its accessible name — a chip drawn as “ready” is still announced as “script ready”.
• state is never carried by colour alone. the library's mode switcher sets aria-selected as well as painting the selected tab, and a video's status is a word as well as a colour.
• the waiting status clears the contrast floor now. the “writing your script” label measured 3.4:1 against the chip it sits on, under the 4.5:1 AA floor for text, in every place it is drawn but one: a closed video card had been raised to 7.2:1 and the rest had not. on 19 august 2026 the rest were raised the same way — the open row, the library entry, a script nested inside one, the count in a brand's header, and the agency app's own waiting chip — and every one of them measures 7.2:1. the word holds that ratio through the whole of its pulse. the dot beside it does not: at the bottom of the pulse it is 1.8:1, which is why the dot is never the only thing saying a script is being written.
• things that change without a click announce themselves. the wait‑list result, the search result count and the app's status messages are live regions, so a screen reader is told when the page changes underneath it.
• motion respects your system setting. if your device is set to reduce motion, every animation and transition on the site is turned off, including the sliding tab indicator and the card and panel transitions. nothing is left mid‑animation and nothing becomes invisible as a result — the loading mark in particular is drawn in its assembled state rather than disappearing.
• type scales with the page. text is set in relative units against the viewport, and the public pages can be pinch‑zoomed and browser‑zoomed without content being cut off or overlapping.
• structure. real headings in order, real form labels, real lists, and one main landmark per page.

what does not work yet

this list is the point of the page. it is complete as far as we know on the date above, and anything found later gets added here rather than quietly fixed and forgotten.

• pinch‑zoom is switched off inside the creator app. the creator app caps page scale, which fails WCAG 1.4.4 (resize text). it is a deliberate trade made on 19 august 2026: it is what allows the search field to be the same size as the text around it instead of looming over it. it affects the creator app only. the agency app, this page, the home page, the wait list, the privacy policy and the terms are all unaffected and stay fully zoomable. browser zoom is not affected anywhere. if this stops you using lynxr, tell us and we will change it — it is one line.
• nothing here has been tested with a real screen reader or on a real assistive device. the checks above are measurements of the rendered pages — focus rings, contrast ratios, accessible names, keyboard order. that is not the same as somebody using VoiceOver or NVDA to get through a task, and we are not going to imply that it is.
• the video player inside the app is the platform's own embed. when you watch a source video in lynxr, that frame is TikTok's or Instagram's, and its accessibility is theirs. we do not control it and cannot fix it.
• captions and transcripts of the videos you paste come from automatic transcription and are not checked by a person, so they carry the errors that any automatic transcript carries.

telling us about a problem

email hello@lynxr.io. it goes to the two people who build lynxr. we are not going to promise a response time we cannot keep — there are two of us — but a specific report (what you were doing, what happened, what you use) is the thing most likely to get fixed, and the gaps above are listed because somebody measured them and wrote them down.

contact

lynxr LLC
15 Farrington Ave, Allston MA 02134, USA
hello@lynxr.io