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?
Turns out the real accessibility issue was me not asking the actual users what they needed first, so has anyone else built something that solved a problem nobody had?
I was testing a checkout form last week and realized the error messages weren't being read aloud at all. Adding aria-describedby to link each field to its error message fixed it in about 10 minutes. Has anyone else found a quick fix that made a big difference for accessibility?
I bought AccessiBuddy Pro about 4 months ago for $199 thinking it would help me check my designs for blind users. Half the time it couldn't even parse simple buttons or forms on my own sites, and their support never replied to my emails after the first week. I ended up just learning to use NVDA for free and it works way better than that overpriced junk. Has anyone else gotten burned by a fancy accessibility tool that didn't deliver?
I was digging through some old accessibility reports from a government website audit last week (just curiosity, I'm weird like that) and found out that over 60% of images on major news sites still don't have proper alt text. That shocked me, because I always figured the big players had their stuff together by now. I remember back in 2015 working a help desk gig where a coworker showed me how screen readers just say 'image' with no description, and it felt like a huge oversight even then. Fast forward almost a decade and apparently not much has changed, at least not for the top 50 traffic sites. It made me wonder if designers and content folks just forget or if there's a training gap somewhere. Has anyone else noticed this issue creeping up in places you'd expect to be better?
I tested both against screen readers and the bold color version got way fewer errors because people could see enough to navigate without full reliance on audio feedback. Has anyone else found that pure high contrast can actually make things harder for some users?
I swapped my app's color scheme to high contrast black and white last week thinking it would help visually impaired users. Turned out the harsh white on black triggered headaches in about 15% of testers within minutes. How do you balance accessibility needs for different groups when they conflict like this?
I spent about 3 hours last week trying to pick a green for a button on a dashboard design. Ran it through three different free contrast checkers online and got three different ratios. One said it passed WCAG AA, another said it barely failed. Had to dig up the official WCAG formula myself and do the math by hand. Took forever. Anyone else run into this where the tools disagree? Which checker do you lean on?
So last week I redesigned my little Etsy shop page. Made the 'Add to Cart' buttons huge with high contrast colors. Like 60px tall and bright orange. Thought I was being super inclusive. Showed my 78 year old grandma the site and she spent 30 seconds trying to click the product description text next to the button instead of the actual button. I was like 'Grandma, the big orange thing!' and she said 'Oh I thought that was just decoration.' lmao. Learned that if something looks too flashy some people just ignore it as noise. Has anyone else had a family member completely miss an obvious design choice? What'd you do to fix it? I'm thinking of adding a subtle arrow pointing to the button now lol.
I watched a developer at my coworking space last Tuesday slap black text on pure white backgrounds for every button because someone told him accessibility means max contrast, but all it did was make the app harsh to look at and gave me a headache after 10 minutes of testing it.
Had a big pitch meeting last Tuesday with a Chicago nonprofit. I had labeled all my mockups with proper alt text for the presentation screen reader demo. My boss rushed before we went in and deleted it all, said it "looked cleaner." Screen reader user on their team couldn't navigate a single slide. We lost the contract on the spot. Anyone else deal with a higher-up who doesn't get why accessibility matters?
I used to think making sites accessible was just about adding alt text and checking contrast ratios. Then I sat near someone at the Seattle Public Library who talked about testing their app with people who have dyslexia. He mentioned that real users caught issues like confusing button labels that no checklist would find. Has anyone else tried running a small usability test with just 3 or 4 people from the disability community?
I was showing a dev a new sign-up flow last week and he kept clicking the same button twice because he couldn't tell when it was hovered. Turns out I only changed the color from blue to a slightly darker blue, but to his red-green color blindness it looked exactly the same. I added a subtle underline and a slight scale bump and he said it was way clearer. Has anyone else had to rethink hover states after testing with real users?
So I was at the Verizon store last week picking up a new charger and I noticed they had both a Samsung OLED and an older LCD phone on display. I pulled up my app on both and holy cow the difference was huge. Dark mode on the OLED looked clean and the text was sharp but on the LCD the same dark backgrounds looked washed out and grayish. The buttons I designed with a subtle drop shadow totally disappeared on the LCD screen. I never would have caught this if I just kept testing on my own phone. Has anyone else run into this where your design looks great on one device but falls apart on another type of screen?
I was building a new site and had this developer tell me dark mode was always better for accessibility. Then I ran into a user in a forum who gets bad astigmatism flare from white text on black backgrounds. Has anyone else run into cases where the usual "accessible" choice backfires?
I was testing a new app design with a buddy who has low vision. He kept switching between high contrast mode and the app's dark theme and got frustrated because neither really worked. High contrast made things too harsh and dark theme made some text disappear. So I went back and adjusted contrast ratios manually on each element instead of relying on the default settings. Has anyone else found that custom contrast tweaks beat automated themes every time?
I was at the natural history museum in Denver and my dad couldn't zoom in on the exhibit text because the buttons were too tiny and close together. He's got fine motor issues from his hands shaking and just gave up on using it. Has anyone found a good minimum button size that works for older users without making the layout look clunky?
I was redesigning the instructions for our store's online ordering page and had a choice between a nice dark gray on white or straight up black on white. The dark gray looked cleaner and more modern, but I went with black on white for the body text after testing it with my phone at arm's length. My dad who's in his 60s came over and tried to place an order on his tablet, and he actually read through the whole thing without squinting or asking me to zoom in. That was a small win for me since I usually overthink the aesthetic stuff. Now I'm wondering if I should go back and check my other text choices too. Has anyone else had to choose between looking good and being easier to read?
I was sitting at a community college workshop last Tuesday and heard a UI designer tell the class that WCAG contrast ratios should be the rule for every design decision. I get that accessibility matters, but I think that approach misses something important. For some folks with certain types of migraines or light sensitivity, that maximum contrast can actually cause pain. Has anyone else had to balance accessibility guidelines against real user comfort?
I tried adding alt text to every single decorative image on my site last week and it actually slowed down screen reader users who kept hearing 'decorative' over and over (which felt useless). On the other hand, skipping alt text completely feels like ignoring a rule for no good reason. What do you all think, is there a middle ground or should decorative images always get null alt?
I spent a solid 4 hours last Tuesday trying to figure out why my button text was invisible on a blue background. Turns out the transparency setting on the layer was set to 80% by accident. I must have clicked through a dozen accessibility checker tools before I just zoomed in and saw the opacity slider was off. Felt pretty dumb but hey, it happens. Anybody else waste a chunk of time on something this basic?
I read it in a web accessibility survey from WebAIM last week and it surprised me how many people skip a mouse entirely. Has anyone here changed their design workflow after finding stats like this?
Last month in an accessibility audit at work, a blind tester pointed out that my 'Learn More' button text was basically invisible to her screen reader. She said to think of it like walking up to 50 doors with no signs. I switched to descriptive labels like 'Read our pricing guide' and 'See wheelchair ramp specs' instead. Has anyone else gotten feedback that made you rethink something you thought was fine?