Free & open source · by Slikk.Dev

Your website looks great. To you.

Ansy is a free desktop browser that lets you experience your own site the way people with low vision, colour blindness, motor, hearing or attention difficulties do. It brings the tools they rely on too, like screen readers, zoom and keyboard-only navigation. Spot what breaks, then hand your developer a clear report.

For macOS, Windows and Linux. In English and Hebrew. Free, for good.

Try the idea

Same shop. Seven ways of seeing it.

Below is a made-up online shop. Its designer used colour to say "on sale", "in stock" and "you typed that wrong". Switch how you see it and watch what survives.

A small online shop with two products. The mug's sale price is shown only in red, each product has a green or orange dot that is the only sign of whether it is in stock, and the email field signals an error only with a red border.
See it with

How the designer sees it. A red sale price, a green dot for "in stock" and an orange one for "almost gone", and a red border because the email address has a typo. Now pick another way of seeing it.

Protanopia, no red cones. The red sale price, the green and orange dots and the red error border all slide toward the same muddy yellow and brown. Colour was the only signal, so the signal is gone.

Deuteranopia, no green cones. Red–green colour blindness affects roughly 1 in 12 men. "In stock" and "almost gone" now look identical, and the sale price no longer stands out from the regular one.

Tritanopia, no blue cones. Rare, and it hits different colours: the sage vase and the green button shift toward teal and grey, while the reds survive. Every type of colour blindness breaks a different part of your design.

No colour at all. The extreme case, and a good stress test. "Sale", "in stock" and "error" become three grey shapes that mean nothing. A word, an icon or an underline would have carried the message.

Blurred vision. Uncorrected eyesight, cataracts, or simply forgotten glasses. Small grey text goes first: the old price and the stock labels are unreadable. Big, bold, high-contrast text survives.

Low contrast sensitivity. Common with age and in glare on a phone outdoors. Pale text and thin outlines fade into the background, and the error border is nearly invisible.

This preview is a rough CSS sketch. Ansy uses the browser engine's own vision emulation, and runs it on your real website.

Version 2.0

Nineteen experiences. One switch each.

Each experience changes how your site looks, sounds or responds, so you can feel the barrier yourself. Where people use a tool to cope, Ansy gives you that tool too. The few that can only give a rough impression say so, and name the tool that person really uses.

Sight and blindness

  • Colour blindness

    Four types, from red–green to total colour blindness. Find every place where colour is the only signal.

  • Blurred and low-contrast vision

    See which text, icons and buttons stop being readable long before your designer would notice.

  • A rough impression

    Tunnel and central vision loss

    Everything goes dark but a small circle around the mouse and the keyboard focus, or a grey patch covers the spot you look at. Can you still find the cart?

    Tool: screen magnifier
  • A rough impression

    Cataracts and glare

    A cloudy, yellowed veil, or a screen flooded with sunlight. Pale grey text is the first thing to go.

    Tool: high contrast and zoom
  • Screen reader

    Hear your page read aloud the way blind customers hear it, and move by headings, links and buttons.

    Tool: screen reader

Low vision and light sensitivity

  • Zoom to 200% and 400%

    Blow the page up the way people with low vision do. Does the layout reflow, or does the checkout button fall off the screen?

    Tool: magnifier
  • Larger text and spacing

    Bigger letters and wider line spacing, as many people set them. Watch for text that gets cut off or overlaps.

    Tool: text settings
  • High contrast

    Force the system's high-contrast colours, like Windows contrast themes do. Find the icons and buttons that disappear.

    Tool: contrast themes
  • Dark mode

    Tell your site the visitor prefers dark, as people with light sensitivity do. Does it have a dark theme, and does anything vanish when it is darkened anyway?

    Tool: system setting

Moving and clicking

  • Keyboard only

    Put the mouse away, like people with tremors or limited hand movement often do. See where focus goes, and where it gets lost.

    Tool: keyboard
  • A rough impression

    Tremor and unsteady hands

    The pointer shakes, and a click lands wherever the shake carries it. Ansy also flags buttons smaller than 24 pixels.

    Tool: keyboard and bigger targets
  • Switch access

    A highlight steps through your controls by itself and one key picks, as a single-switch user does. Count the steps your checkout takes.

    Tool: switch device
  • Voice control

    Type or dictate "click Buy now". When a button shows one name and is called another, the command misses, and Ansy shows you why.

    Tool: voice control

Hearing

  • No sound

    Mute everything and check your videos. Is there a caption for every word that matters?

    Tool: captions

Focus and reading

  • Reduced motion

    Turn on the setting people use when animation makes them dizzy or distracted, and see whether your site respects it.

    Tool: system setting
  • Dyslexia and reading aids

    A readable font, wider spacing, a line ruler and read-aloud: the tools people use. Watch for text the new font cuts off.

    Tool: reading tools
  • Plain language

    A reading score for every page, with the hardest paragraphs ringed. A standard formula in English, a rough measure in Hebrew.

  • A rough impression

    Seizure risk from flashing

    Ansy watches your page and counts flashes. More than three in a second can trigger a seizure, so it tells you where.

For every visitor

  • Automated check

    A scan that flags common problems and names the WCAG rule behind each, so your developer knows exactly what you mean.

    Engine: axe-core
How it works

From "huh" to "fixed" in four steps.

  1. Open your site

    Type your address into Ansy, like any browser. Your live site, your staging site, or a page your developer just sent you.

  2. Switch on an experience

    Pick one, or follow a short guided task like "buy something using only the keyboard".

  3. Note what breaks

    Save a finding in one click: a screenshot, your own words, and the rule it breaks.

  4. Hand it over, then re-test

    Export a PDF or plain-text report for whoever builds your site. When they say it's fixed, check again: for a keyboard or screen reader problem, Ansy presses the same keys again and tells you whether it's gone.

Straight talk

A way to see the problem. Not a magic fix.

The accessibility industry is full of widgets that promise compliance with one line of code. They don't deliver it. Ansy promises less, and means it.

Ansy is

  • A testing and empathy tool. It runs on your computer and changes only what you see.
  • A shared language with your developer. Findings come with screenshots and the exact rule, not a vague "it feels off".
  • A first step. Fixes belong in your site's actual code, made by the people who build it.

Ansy is not

  • An overlay or widget. Nothing gets installed on your website, and your visitors never see Ansy.
  • A compliance certificate. Automated checks catch only part of the problems. A clean scan is not a legal guarantee.
  • Lived experience. A simulation is a glimpse. Disabled people who use your site every day are the real experts, so listen to them.
Open source

Free for everyone. For good.

An accessible internet shouldn't depend on who can afford the tools. Ansy's code is public, MIT-licensed, and built in the open as part of Slikk.Dev's push for an internet that works for everyone.

₪0 / $0
No price, no trial, no "pro" tier.
MIT
Read it, fork it, ship it inside your own tools.
EN + עב
English and Hebrew from day one, with full right-to-left support.
macOS, Windows, Linux
A desktop app built on Electron, so every experience runs on a real browser engine.

Roadmap

  1. Done

    Research and plan

    Which experiences matter most, what tools people actually use, and what a non-technical owner needs to act on a finding.

  2. Done

    1.0

    The browser, ten experiences, guided tasks, findings and reports, and the built-in screen reader. Every step landed as a public pull request.

  3. Done

    2.0

    Nineteen experiences, every one the research called for, from switch access and voice control to reading aids and flash detection, and re-tests that press your keys again.

  4. Done

    Downloads

    Ansy 2.0 for macOS, Windows and Linux, on GitHub.

  5. Next

    Signed builds

    Signed and notarized builds for macOS, and Windows through the Microsoft Store.

  6. Later

    More languages, and an extension

    More interface languages, such as Arabic, and a companion browser extension.

Version 2.0.0 · 29 October 2026

Download Ansy.

Choose your system. Free, with no account to create. These first macOS and Windows downloads are unsigned; read the installation notes below.

  • macOS

    Choose Apple silicon for an M-series Mac, or Intel for an Intel Mac.

    The app is not signed or notarized by Apple, so macOS may block it from opening. Automatic updates are unavailable in this build; download future versions here.

  • Windows

    The direct installer for Windows on Intel and AMD PCs (x64).

    This installer is unsigned. If SmartScreen shows "Windows protected your PC", choose "More info", then "Run anyway" to install it. A Microsoft Store version is not available yet.

  • Linux

    For Intel and AMD PCs (x64). Choose AppImage, or the .deb package for Debian and Ubuntu.

    Make the AppImage executable before opening it. For .deb installations, download and install each new version by hand.

Release notes and all files on GitHub · Code signing policy

FAQ

Fair questions.

Who is Ansy for?

Business owners, marketers and product people who aren't accessibility experts, and don't want to become one just to know whether their site works for everyone. Developers and designers are welcome too.

Do I need any technical skills?

No. If you can use a web browser, you can use Ansy. Every experience explains, in plain language, what you're looking at and what to look for.

Does it change my website?

Never. Ansy only changes what you see and hear on your own computer. Your site, and what your visitors see, stay exactly as they are.

Why a desktop app and not a browser extension?

Owning the whole browser lets Ansy use the engine's built-in colour-vision emulation, real high-contrast rendering and the page's accessibility tree, things an extension can't fully reach. A companion extension may follow later.

Can a screen reader simulation replace testing with blind users?

No, and we'd be suspicious of anyone who says otherwise. Ansy gives you a feel for the problem and a vocabulary for it. For anything that matters, test with the people who use assistive technology every day.

What happens to my findings?

They stay on your computer until you export them. Reports can include an optional "Ask Slikk.Dev to fix this" link, which you can switch off. Send the report to any developer you like.

Who makes Ansy?

Slikk.Dev, a web development studio that builds accessibility into the code instead of bolting it on. Ansy's code is MIT-licensed. The Slikk.Dev name and logo are trademarks and stay reserved.

How do I install it?

Choose your system in the download section and read the installation notes. The current macOS and Windows builds are unsigned. On Windows, if SmartScreen shows "Windows protected your PC", choose "More info", then "Run anyway". macOS may block the unsigned app from opening.

Automatic updates are unavailable for this Mac build and for .deb installations; download new versions by hand. Signed builds and a Microsoft Store version are still to come.

Be first to see what your customers see.

Ansy 2.0 is out, free for macOS, Windows and Linux. Download it, or jump in with ideas and code.