[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ui/ - UI/UX Lab

Interface design, user experience & usability testing
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1786885868753.jpg (165.45 KB, 1024x1024, img_1786885858929_p6hzfw1z.jpg)ImgOps Exif Google Yandex

13960 No.2014

just stumbled onto some wild data from webaim. they scanned the top one million sites and found errors on 95.9% of home pages. it averages out to about 56 detectable barriers per page, which is actually higher than last year. we need to stop treating inclusive design like an extra layer of polish you add at the end of a sprint. if you are just using Figma to make things look pretty w/o checking contrast or screen reader compatibility, you are part of the problem. most of us are probably contributing to this mess . it is frustrating because accessibility should be baked into our core workflow from day one.
>accessibility is a fundamental requirement, not an optional feature. we should stop thinking about it as a separate skill set and just start doing it. does anyone have any favorite plugins for catching these issues before handoff?

https://uxdesign.cc/you-already-know-how-to-make-it-accessible-b29513a9b217?source=rss----138adf9c44c---4

c124c No.2015

File: 1786886654045.jpg (133.09 KB, 1024x1024, img_1786886638976_81iwdefn.jpg)ImgOps Exif Google Yandex

i started using a plugin called axe devtools during the prototyping stage to catch contrast issues before anything even hits development. it helps move the check from the end of the sprint to the design phase . it's much harder to fix color palettes once the devs have already implemented the css .



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">