Low vision is not blindness, and that matters
When people hear "visual disability" they picture total blindness and a screen reader speaking the page aloud. That is real, and it is important, but it is a minority of us. Far more people sit where I do: we have some usable sight, often quite a lot of it, but not the sharp, effortless vision a typical website is designed around. We read with our eyes, not our ears. We just need the page to meet us partway.
This is the largest and most overlooked group in accessibility, and it includes a rapidly growing population you might not label as disabled at all: anyone middle-aged and older whose eyes have simply changed. The person squinting at a menu in dim light, the customer who bumps their phone text size up two notches, the grandparent zooming a page to two hundred percent — they are all navigating the web the way I do. Design that works for me works for a huge slice of your customers who would never call themselves disabled but who feel every one of these decisions.
The first thing I do is make it bigger
On almost every page, my first move is to enlarge it — browser zoom, and on some sites a dedicated screen magnifier on top of that. This is the most common thing low vision users do, and it is the single fastest test of whether a site was built with us in mind. When I zoom a well-built page to two hundred percent, the text simply gets bigger and reflows to fit, the way water fills a narrower glass. Everything stays readable, nothing gets cut off, and I can still reach every link and button.
When I zoom a badly built page, it falls apart. Text overflows its box and hides behind other text. A horizontal scrollbar appears and I have to drag the page left and right to read a single line, which is exhausting. Menus vanish or overlap. Buttons slide off the edge of the screen where I cannot reach them. This is why the accessibility guidelines insist a page must stay usable when enlarged and must reflow without a horizontal scrollbar. It is not a technicality — it is the difference between a page I can read and a page that physically shoves my content out of reach every time I make it big enough to see. When you build a site that survives zoom, you have quietly done the most important thing for the largest group of us.
Contrast is not decoration to me
Designers love low contrast. Light grey text on a white background looks calm, modern, expensive. To me it looks like nothing at all. Pale grey on white, thin light type, placeholder text inside a form field — these are the visual equivalent of someone mumbling. I can sometimes force my way through with high contrast mode or by leaning in, but every low-contrast element is a small tax on my attention, and enough of them and I give up and leave.
This is exactly what the contrast ratio guidelines are protecting. When the rules say body text needs a certain contrast against its background, they are encoding what I experience directly: below a certain point, text stops being reliably readable for people with reduced vision, and it gets worse in bright rooms, on cheap screens, and outdoors. The frustrating part is that good contrast costs a designer nothing — it is the same layout, the same font, just a darker text colour. There is a whole separate piece on this site about hitting contrast targets, but the human version is simple: if your text is a soft grey because it looks tasteful, you are choosing style over whether I can read you, and I will notice.
Where am I on the page?
When a page is magnified, I am only ever seeing a slice of it — imagine reading a newspaper through a paper-towel tube. That changes everything about how I navigate. I lean heavily on clear structure: real headings I can jump between, a logical order to the content, and above all a visible sign of where I currently am. When I use the keyboard to move through a page, I need to see which link or button I have landed on. That highlighted outline around the focused element is my cursor, my "you are here" pin. Without it, I am lost inside my own zoom.
Designers remove that outline constantly because they think it is ugly, replacing it with nothing. Every time that happens, a keyboard or low vision user loses the ability to tell where they are on the page. This is why keyboard accessibility and visible focus are such a big deal in the guidelines — not for some abstract user, but for the very concrete experience of me, zoomed in, trying to find the button I just tabbed to. Give me a clear focus style and predictable structure and I can fly through your site. Take them away and I am guessing.
Why text beats pictures of text
Real text is flexible. I can enlarge it, my browser can recolour it, my high contrast mode can invert it, and a screen reader could read it if I needed that. A picture of text — a nicely designed graphic with words baked into it, an infographic, a promotion saved as an image — is a locked box. When I zoom it, it just turns blurry and pixelated instead of getting genuinely bigger and sharper. My contrast tools cannot touch it. If the important information on your page lives inside an image, it is often information I cannot get to.
This is why the guidelines push so hard for real text over images of text, and for every meaningful image to carry a text description. When you put your hours, your prices, or your phone number in a graphic because it looks nicer, you are handing them to me in a format I cannot adjust. Put them in actual text and they bend to whatever I need — bigger, darker, inverted, read aloud. Text is the most accessible thing on the web, and it is free.
The small things that quietly lock me out
A handful of small design habits cause a lot of my daily friction. Tiny click targets that I struggle to land on when zoomed. Pop-ups with a close button so small or so faint I cannot find it, trapping me. Motion and auto-playing carousels that move content before I have finished reading it. Colour used as the only signal — a form that marks an error only by turning a field red, when red and its neighbours look nearly identical to some people. Forms where the label disappears the moment I click in, so once I am typing I can no longer see what the field was for.
None of these are exotic. They are ordinary choices made without thinking about someone like me, and each one is covered by an accessibility guideline that exists precisely because it trips real people. When I test a site and hit three or four of these in a row, it is not that the site is malicious. It is that nobody who built it ever tried to use it the way I have to. That is the gap accessibility work closes: not adding some special disabled mode, just building the normal site so it does not fall apart under the conditions a large part of your audience actually lives in.
Why this is good business, not charity
I want to be clear that none of this is a plea for pity or a lecture about doing the right thing, though the right thing is a fine reason. It is a business argument. People with disabilities and the far larger group of aging eyes represent an enormous amount of spending power, and we are intensely loyal to the businesses whose websites treat us as welcome rather than as an afterthought. When I find a site I can actually use — where I can zoom without it breaking, read without straining, and find where I am without hunting — I remember it, I come back, and I tell people. When a site fights me, I leave, and there is almost always a competitor one search away who did the work.
That is the real reason I write this material from lived experience rather than from a checklist. The guidelines are good, but they land differently once you understand they are describing a person on the other side of the screen, doing their best to give you their business through a page that either helps them or does not. Build for the version of your customer whose eyes are not perfect — which is most of them, eventually — and you build a better website for everyone. If you want a hand checking whether your own site holds up under real assistive use, that is exactly the kind of accessibility review I do at Design Menu, from the same chair, with the same tools I have described here.