Last month I paid $120 for a premium screen reader to test my designs. Thought it was the pro tool everyone used. Spent a whole weekend learning its quirks. Then a friend showed me the free open source one. It had better navigation, clearer voice, even a visual focus overlay I needed. Felt like an idiot. The money isn't the worst part, it's the three days I lost. Anyone else burned cash on paid access tools when free options were right there?
I was waiting to cross the street downtown last Tuesday and noticed the countdown numbers are way bigger than they used to be. They also have a bright flash when the walk signal starts, which I never paid attention to before. My dad has low vision and he mentioned last month that he can finally see when to go without squinting. That got me thinking about how we add states to buttons on websites. Do you usually make the active state obvious enough for someone with poor eyesight, or do you rely on color alone?
Back in September I made the call to drop the stark black on white theme for a dark mode option on the site we use for parent updates. The contrast ratio was technically better on the old one, but a few parents with migraines kept telling me the glare was killing them. So I went with a soft gray background and off white text, which helps in low light but now some older folks complain they can't see the buttons. I tested it with a 62 year old grandparent and a kid with dyslexia, both said it was easier, but the school board wanted data. Has anyone else juggled contrast needs between age groups like this?
I was testing a new checkout flow with a friend who has color blindness. They pointed out that my 'Continue' and 'Cancel' buttons were almost the same shade of green. I had just picked colors that looked good to me on my screen. Took me about 20 minutes to redo them with different shapes and a blue for Continue, red for Cancel. Has anyone else had trouble telling action buttons apart after a redesign?
Honestly, I spent three days picking this perfect script font for their save the dates, and when I printed a test page the lowercase 'g' looked completely broken and unreadable. Turns out the free version I downloaded had a missing glyph set nobody mentions in the previews. Has anyone else gotten burned by fonts that just fall apart when you actually use them?
I was at a local Starbucks in Denver last week trying to read a menu board from 15 feet away. The letters were this light gray on a white background and I physically could not make out the prices. A guy next to me pointed out he had the same problem and he wasn't even old. That moment made me realize all my web designs probably looked like that to someone with any vision issues. Now I test everything on my phone outside in sunlight before I call it done. Has anyone else had that gut check moment where a real world thing made you change your whole approach?
I've been using a screen reader for about 2 years now and always got annoyed when it would read everything on the page at once. Last week I accidentally hit a key combo and discovered focus mode only reads the stuff I'm actually interacting with on the page. It's made browsing so much faster for me. Has anyone else found weird shortcuts like this that make a big difference?
I was testing a pastel green on white for a client's site last week and every free tool I tried said it passed WCAG AA. My friend who has low vision looked at it and said it blended together for her. Turned out the tools were using different color perception models - I switched to one that simulates several types of color blindness and it flagged the combo immediately. Has anyone else caught false passes from the common checkers?
I installed the Stark plugin in Chrome back in January and trusted its green checkmarks for everything. Last week I showed my wireframes to a friend who uses screen readers and she pointed out three places where text was technically passing AA but still unreadable on actual screens. The checker was measuring color contrast ratios in a vacuum without considering that the background image shifted brightness in different spots. Now I'm screenshotting every section and checking multiple points with the eyedropper tool in manual mode. Has anyone else found a quick way to test contrast across variable backgrounds without pulling your hair out?
I was at Dollar Tree 2 weeks ago buying poster board to make sale signs for my flea market booth. I always used size 10 font on my computer prints because I thought it looked clean and professional. A cashier maybe 19 years old looked at my stack and said "sir nobody can read that from a car" and pointed at her phone. She showed me her grandma's sign making group on Facebook where they use nothing smaller than size 48. It hit me right there that I was designing for my own eyes not for people driving by or old folks with bad vision. So I blew up my next sign to size 72 bold black on yellow and my sales jumped $80 that Saturday. How do you test if your font sizes actually work for old people or people who don't have perfect 20/20 vision?
She told me I made the buttons too small and the contrast on the login screen was basically invisible for her, and that hit different because I spent weeks on that dashboard layout without once asking someone who can't see well to test it.
For a local library website redesign, I had to pick between a trendy thin font and a chunky high contrast one. I went with the ugly high contrast option because the library serves a lot of older patrons. Two board members complained it looked like a government document from 1995. Six months later, the usage stats showed a 40% drop in support requests from seniors. Still getting side eyes at meetings though. Has anyone else dealt with clients who prioritize looks over readability?
I bought this app called AccessiBuddy off the App Store because it claimed to simulate how blind users navigate your site. Cost me $80 after the trial ran out and I forgot to cancel. Turns out it only works on static HTML pages and crashes every time you hit a dynamic element like a dropdown or modal. I lost a whole afternoon trying to test my checkout flow with it and got zero useful feedback. The voiceover read half the buttons as 'unlabeled' even though they had aria labels. Save your money and just use the free built-in screen reader on your phone or computer instead. Has anyone else fallen for those paid accessibility testing tools?
He showed me how he bumps up the text size and uses greyscale mode to read better, and I realized I have never once tested my designs on those default settings - has anyone else found stuff breaking when they check their work with accessibility toggles on?
Visited Brew Haus on 3rd Street last Saturday and couldn't read half the drink options because they used light gray text on a white background, and when I asked the barista about it she said 'oh yeah, we get that a lot' - why do places keep doing this?
I used warm tones for a client dashboard in Austin last year. Looked great to me. Client called me after 3 weeks saying their boss couldn't tell red from green status indicators. Changed it to add symbols and patterns. Took me 2 hours to redo. The boss sent a thank you email the next day. Anyone else had to redo work for colorblind users?
I was showing my wireframes to a buddy who's got bigger fingers than me and he literally couldn't tap the send button on my app. Measured it and realized I was using 38px tall buttons when the guideline says 48 minimum. Has anyone else had a coworker or friend point out something obvious you missed?
I spent $40 on a demo version of NVDA last month just to see how my designs actually sounded to blind users. Turned out my carefully written alt text was reading out loud like garbage because I was cramming in too many keywords. Now I write short, clear descriptions and test them with the tool first... has anyone else actually listened to their own designs?
I was working on a client's signup form last week and kept failing the WCAG AA contrast check on the error messages. The text looked fine to me, but the tool kept saying it was too light against the background. Turned out I was checking the wrong background layer - there was a subtle gradient overlay I completely missed. After digging through the Figma layers for what felt like forever, I finally found the overlay was set to 15% opacity. Has anyone else wasted a ton of time on contrast issues that were hiding in plain sight like that?
I added a simple high-contrast filter option and suddenly everyone on the beta was saying the "Submit" button disappeared on their screens. Turned out the icon contrast was fine but the text contrast hit zero on standard displays. Has anyone else run into accessibility features that backfired on you?
Turns out the thin sans serif I loved looked great on my retina display but was a blurry mess on her cheap monitor. Who else has had to completely rethink their font stack after one specific user callout?
Last week on a job site in Portland, a general contractor told me he wouldn't install the high contrast stair markers I spec'd because they 'ruin the vibe' of the lobby. I had to explain that those markers keep someone with low vision from falling down three flights, and 'vibe' doesn't override safety. How do you all handle pushback from folks who prioritize looks over basic accessibility?
I was at the Austin Public Library on 6th yesterday and had to crouch down to even see the call button on the new elevator panel, which felt completely backwards for a building that just opened - has anyone else run into this kind of placement fail in new construction?
Been working on a new app design for my client in Seattle and was getting headaches staring at the screen after 9pm. Switched to the high contrast accessibility setting on my Android last Tuesday instead of just dimming the brightness. The difference was night and day - my eyes felt fresh even after 3 hours of tweaking color schemes. Anyone else find that high contrast modes work better than just turning down the light?
I was going through my grandma Ethel's recipe cards in her kitchen in Des Moines and noticed she always wrote ingredients in blue pen on yellow paper. The yellow text on white cards was nearly impossible to read, but those blue on yellow combos popped perfectly. It hit me that she figured out accessible color pairing 50 years ago without any tools. Has anyone else found good inspiration from old, unexpected places?