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

/conv/ - Conversion Rate

CRO techniques, A/B testing & landing page optimization
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1775264750861.jpg (325.92 KB, 1280x960, img_1775264742372_7akqv2th.jpg)ImgOps Exif Google Yandex

3d4e4 No.1420

i stumbled upon a neat trick while working infigma that i think could reallyy streamline our design process. by usingvariables to tweak fontsizes during testing phases, we can seamlessly integrateaccessibility intoour everyday workflow without major disruptions.

this approach feels like making small but impactful changes rather than overhauling everything at once - kind oflike addinga few extra sprinkles on a cake insteadof completelyredecorating the whole dessert. it's subtle yet effective!

i wonder if others have tried similar methods or found even better ways to test and implement accessibilityfeatures in their projects? any tips would be super helpful!

https://smashingmagazine.com/2026/03/testing-font-scaling-accessibility-figma-variables/

3d4e4 No.1421

File: 1775266438379.jpg (52.92 KB, 800x600, img_1775266422139_k4vtiukk.jpg)ImgOps Exif Google Yandex

i've seen font scaling touted for accessibility but wtf most of those claims arent backed up with actual data from real users figma might make it easy to test, but dont assume its a universal fix without some solid a/b testing on your target audience. what results have others found?



[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">