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?
I put together a landing page last Tuesday that looked great on my monitor. Sent it to the client for review and they came back saying the text was unreadable. Ran it through a contrast checker and the light gray on white background failed at a 2.8 ratio. Had to go back and darken the text color which messed up the whole visual balance. Now I run every color combo through the WCAG tool before I even start styling. Anyone else have a color fail that slipped through because you trusted your eyes?
I compared two approaches for labeling buttons in a checkout flow: using "Purchase" vs "Complete Order." The screen reader users I tested with skipped "Purchase" 3 out of 5 times because it sounded too generic. Has anyone else found certain action words work way better with their accessibility tools?
Honestly, I was at a coffee shop in Austin last month and watched a guy squint at my app's login button for like 10 seconds before giving up. It hit me that I'd been using a 2.5:1 contrast ratio the whole time thinking it was fine. Has anyone else had a stranger's face tell them they messed up?
I always swore by that WCAG AA contrast checker app on my phone. Used it for like 3 years on every project. Then last Wednesday I was designing a sign for a local library event in Austin, and I kept getting that stupid red X on a light yellow background with dark blue text. I spent 45 minutes tweaking colors just to get the checkmark. My student teacher saw me and asked why I was fighting it so hard. I showed her the app and she just pulled out a printed piece of paper with the same colors on it and asked if I could read it fine. I could, no problem. She said the app uses some outdated formula that doesn't account for modern screen brightness or real world lighting. I felt like an idiot. Now I just print a test page and ask a couple coworkers with different eyesight to check it. That Wednesday changed my whole process. Has anyone else had a design tool lie to them like that?
A dev in a forum said autoplay video was bad for users with motion sensitivity and screen readers, but I thought engagement would drop without it. After 3 months with autoplay, my bounce rate went up 12% and I got two complaints about dizziness. Anyone else ditch autoplay and see better results?
I spent 3 hours picking the perfect muted sage green for a website header, only to realize it failed WCAG contrast at every size. Had to scrap the whole palette and start over with a brighter green that looked like slime at first. Anyone else have a color scheme that passed tests but felt like a visual insult?
I'm only 35 with decent vision and the buttons were literally the size of a grain of rice, has anyone else run into this at a major chain or is it just my store?
Turns out my app design looked fine on my OLED phone but when the guy next to me with an older LCD screen tried to read it in the sun at 8 AM, he asked if I was trying to hide something, so now I test on at least three different screens with glare before shipping anything, anyone else checking contrast in real world lighting?
On one hand, strict contrast rules feel limiting for creative designers, but on the other, ignoring them locks out millions of users with low vision - where do you draw the line between art and access?
I had been designing a transit app using a big map view for 3 months and never once thought about how someone using a screen reader would navigate it, so now I'm redoing the whole layout like, what else am I missing here?
I was stuck at my desk in Minneapolis last Tuesday trying to check if my new button text was readable against a light blue background. Every online checker I tried gave me a different pass/fail result and it was driving me nuts. Then I realized I had the wrong hex code for the background shade because I pulled it from a screenshot instead of the actual file. Fixed that, ran it through the Stark plugin in Figma, and boom it passed WCAG AA just barely at 4.6 to 1. Felt like a huge win for such a small thing. Has anyone else had a color mismatch from screenshots mess up their accessibility checks?
I was walking to a showing in the Pearl District last spring and watched a mom with a stroller struggle to get over a 4 inch curb. Then I noticed a newer curb cut 20 feet away that someone had poured with a gentle slope and textured surface. She rolled right up it without even slowing down. That little moment made me rethink how I approach entryways in the homes I stage. We talk about contrast and font sizes but what about the physical path someone takes to get through a door? Has anyone else had a random street observation change their whole approach?
She couldn't tell the difference between my #888 and #666 text on a white background, which was a huge wakeup call that passing WCAG AA isn't always enough in real lighting conditions. Has anyone else run into situations where the numbers check out but real users still struggle?
He said 87% of mobile users never even trigger a hover state so why build a whole feature around something that leaves people out, and now I can't unsee how dumb my own designs look in testing - anyone else had to rip out hover interactions because a real user called them out?
I used to think high contrast was always the answer for accessible design. Last year I worked on a sign-up page for a library system in Austin. I put black text on white backgrounds with bright red error messages. A user who is dyslexic told me the red text vibrated on the page. That made me look into color blindness and reading comfort. Now I use softer tones like dark gray on off-white and avoid pure red or green for feedback. I tested it with 5 users who have different vision needs and they all said it felt easier on their eyes. Has anyone else found that too much contrast actually makes things harder to read?
I was building a login page for a client in Portland last month and got stuck trying to pick a green button color that passed WCAG AA against a white background. After testing 47 different hex codes with a contrast checker, I realized I could have just used a dark outline instead of fighting with the background color. Does anyone else spend way too long on tiny accessibility details that could be solved with a different design choice from the start?
I was at the Kroger on 3rd street last Tuesday trying to use the self-checkout screen. The touch targets were so tiny my fingers kept hitting the wrong button, and I had to call the attendant over 3 times to void items. Has anyone else dealt with kiosks that seem designed for people with tiny hands?