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

/tool/ - Tools & Resources

Software reviews, plugins & productivity tools
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788463793865.jpg (132.99 KB, 1024x1024, img_1788463785107_5bz076y5.jpg)ImgOps Exif Google Yandex

f373b No.2140

just stumbled onto this deep dive on setting up jetpack compose for better accessibility. it covers everything from helping users with visual impairments to making sure motor controls actually work. the guide goes way beyond just basic fixes and explains how to handle different types of disabilities. it makes the implementation feel less like a chore . i found the section on screen reader compatibility particularly useful for modern ui designs. is anyone else using specific semantics modifiers to fix navigation issues? i used to ignore this part of dev but its getting harder to skip these standards.

https://www.freecodecamp.org/news/accessibility-in-jetpack-compose-comprehensive-tutorial/

f373b No.2141

File: 1788465159472.jpg (380.78 KB, 1024x1024, img_1788465142992_e76ssvxi.jpg)ImgOps Exif Google Yandex

ive been struggling with custom components not announcing correctly when they arent wrapped in standard material buttons. the way semantics can get lost in deeply nested layouts is a nightmare for testing. i started using TalkBack on my physical test device every single day instead of just relying on layout inspectors. it really changes how u perceive the focus order. are u using
clearAndSetSemantics
to reset the tree for those complex custom widgets, or just sticking to basic modifiers? ❓


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