why do accessibility folks get so heated about custom-styled dropdowns????

a11yaccessibilityopinion13 replies · 294 views · started
  1. ok weird one im building a startup lnading page and the topic of custom-styled dropdowns came up in a planning meeting. were a small team with a limited budget, so priorities really matter. some ppl think its a quick win for accessibility, others think its a problem in itself. id like to hear from people who work with accessibility daily, and ideally from people who use assistive technology. whats ur real-world experience?? id especially love to hear from anyone who relies on assistive technology every day. pls help 🙏

    1
  2. hmmmm quick q are there legal or contract requirements for accessibility? ??

    0 2 helpful
  3. Automated tools catch only part of the issues. A perfect score can still mean a site that's unusable with a keyboard. Pair automated checks with manual testing: tab through every page, use a screen reader for key flows, zoom to 200% and 400%.

    0 2 helpful
  4. ok so told my boss it would take 10 minutes. its been my entire lunch break

    1 5 helpful
  5. been there man honestly just reset the thermal paste and save yourself the pain. came here to say exactly this hope that helps :)

    0 1 helpful
  6. lol same thing happened to me infinite scroll makes footers unreachable and loses position when navigating back... offer a load more button or pagiantion, and move focus senisbly when new content appears. lmk how it goes

    2 2 helpful
  7. ok so try turning off teh upadte first, fixed it for me

    1 1 helpful
  8. yesss ok update: did what @rmendes_45 said and its fine now. following, having the same problem

    5 6 helpful
  9. overlay widgets can't fix inaccessible markup reliably. many screen reader users already have their own settings and tools, and overlays sometimes interfere with them. the money is usually better spent fixing the underlying HTML: headings, labels, focus order, alt text.

    11 0 helpful
  10. hmmm custom dropdowns are a common source of trouble. native <select> elements come with keyboard support and screen reader semantics for free lol If you need a custom one, follow the ARIA patterns cloesly and test with real assistive tcehnology. lmk how it goes

    2 1 helpful
  11. yeahhh this. so much this fingers crossed 🤞

    5 0 helpful
  12. hmmm auto-playing carousels move content before people can read it and are hard to control. if u must have one, dont autoplay, or provide a visible pause control, and make every slide reachable by keyboard.

    2 0 helpful

Reply to this topic

Sign in or create an account to reply.