Programming

22563 readers

137 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Thunderbird Accessibility Study (tilvids.com)

submitted 3 days ago by cm0002@lemmy.world to c/programming@programming.dev

4 comments fedilink hide all child comments

Result presentation (first 25 mins) and discussion of an accessibility study that Thunderbird ran. They explain various accessibility technologies (like screen readers, eye tracking etc.) and problems they encountered in their design when users relied on these technologies.

Nothing really groundbreaking in here, but still good for challenging one's assumptions.

you are viewing a single comment's thread
view the rest of the comments

[–] Kissaki@programming.dev 2 points 2 days ago

At the end, pointing to their Bugzilla issue tracker

I've always found Bugzilla incredibly inaccessible. It's so overloaded, so complicated, so noisy with unrelated and irrelevant things. It always baffled me how projects use it and keep using it, and especially projects like Thunderbird and Mozilla, for such a long time.

I regularly use bug trackers, to report, comment, or work on. When I see Bugzilla, in most cases, I give up/leave right away.

Consequently, I find it ironic that they point to Bugzilla at the end.

That being said, I think this video is a good intro to accessibility, common issues, and study findings.

How do you guys view Bugzilla as an issue tracker, bug tracker, and work task tracker?