Blind Dev article
Hyperliquid accessibility: how interface improvements change real work
A case on accessibility affecting a real workflow, not an abstract checklist.
Based on Blind Dev personal experience and source posts; verify current details before applying.
Not investment advice. This article describes methodology and risks.
English translation of the original Russian post dated 2025-09-26. This is my experience at publication, not an assessment of Hyperliquid today. “100% accessible” describes my own workflows, not WCAG certification.
The story of how I helped improve Hyperliquid’s accessibility for blind users.
I had been using the project since around February 2024. For the most part, the interface was convenient, understandable and accessible.
The one difficult part was transferring funds between spot and perps.
Imagine two elements — for me, two consecutive lines:
spot
perps
Somewhere between them was an icon you had to click to switch the direction. If that is unclear, I could try illustrating it with AI.
The icon was not announced at all, so I could not click it. I had to ask sighted people for help, but that was not always possible. It was inconvenient.
After a while, I opened a ticket on Discord. I asked them to improve accessibility by making it possible to switch between spot and perp balances by activating the element from the keyboard.
In other words, it would initially say:
spot
perp
I would activate the element containing those two words, and it would become:
perp
spot
A month or a month and a half passed. I asked again when it would be done. They replied that they had other priorities for now, but would definitely do it.
By then, I did not have much faith in that promise. That made it all the more exciting to see the change another one or two months later!
It felt wonderful to activate the control and switch direction when transferring tokens between balances, and when staking or unstaking, where the same problem had existed.
At the time of writing, I was using an interface that was 100% accessible to me, and I was very pleased.
P.S. It surprises me when perp DEXs make even stop-loss and take-profit settings poorly accessible.
Which other projects’ accessibility would you like to read about? Aster, other perp DEXs, or something else?