Support
One address, answered by the person who wrote the thing you are asking about. No ticket number, no first-line script.
Last updated 4 September 2026.
Write to us
hello@skiplink.app, in English or Turkish. We answer within two working days, usually the same one.
Three things make an answer useful instead of a round trip: the address of the page, what you expected, and what happened instead. If the extension showed a message, the words in it are worth more than a description of them.
Things we are asked
Sign-in opens a window that goes nowhere
Signing in is only needed for sharing a report, scanning a whole site and scheduled re-checks. Auditing a page never needs it. If the window opens and stalls, tell us which build you are on — the one from the Chrome Web Store or the download on the install page — because they are separate builds and the answer differs.
The audit found nothing on a page I know is broken
Automated checks cover a portion of the criteria, and the portion they cover is the part a machine can measure: contrast ratios, target sizes, names and roles. Reading order, keyboard flow and whether alt text is true are not in it. The report says what it did not check, and that list is not a formality.
The page uses an accessibility overlay
Skiplink detects it, disables it and audits the page underneath. An overlay changes what a scanner sees without changing what a screen reader user gets, so measuring the page with one running would report somebody else's work as yours.
A whole-site scan stopped early
Scans are bounded per plan and per day, and the popup says which limit was
reached. Addresses disallowed in your robots.txt are skipped
and counted separately — see SkiplinkBot for the rules
the crawler follows.
I want my data gone
Uninstalling removes the local history with the extension. Anything on our side — shared reports, monitored sites, the account itself — is deleted on request to privacy@skiplink.app, and the privacy page lists what exists and for how long.
Reporting something broken in Skiplink itself
The one we most want to hear about: a finding that is wrong. A criterion reported against an element that passes, or a measurement that does not match what you measure yourself. Send the page and the finding. An accessibility tool that is confidently wrong is worse than no tool, so these go to the front of the queue.
We audit our own screens with our own engine on every build and publish what is not counted and why. If you find something on this site or in the extension that fails a criterion we report to customers, that is the same kind of bug and gets the same treatment.
Billing
Team and Agency are bought from inside the extension, on the screen that tells you about a limit. Payment is handled by Polar, who are the reseller and the name that appears on your statement. Cancellation and refunds work the way the refunds page describes, and the terms apply.