#Tag
Les carrousels hantent le web, mais qu’en est-il de leur accessibilité ?
Notre collègue @cookingmaia présente les points critiques qui peuvent créer des situations de handicap et propose des solutions concrètes pour rendre vos carrousels accessibles.
À découvrir sur 24 Jours de Web, aux bons soins de @ParisWeb :
This is so obvious, yet at the same time it seems to me that people rarely really understand what is at stake.
"Most of the breakdowns in a product don’t come from bad intentions or bad work. They come from the way teams divide responsibilities. Engineering focuses on the system behavior. Design focuses on screens and interaction. Product focuses on requirements and scope. Each group works inside its own boundary, and no one is responsible for checking whether all those boundaries line up.
That’s how you end up with a feature that technically “works,” but only if the user magically knows the right order of steps, or already understands a concept that was never explained, or follows a path that only makes sense inside one team’s mental model.
The writer is the first person who has to confront that reality. Not because we’re smarter—because documentation forces us to walk the entire experience in the same order the user will. No shortcuts. No inherited assumptions. No internal knowledge. Just: If I follow this from beginning to end, does it hold together?
That’s when the real gaps surface:
- Prerequisite steps that were never shown in the UI, but the system silently requires.
- Terminology drift where three teams named the same thing differently and nobody noticed.
- Logic branches that exist in engineering’s head, but not in the design or the workflow.
- Error states with no recovery, dropping users into dead ends no one tested.
- Hidden dependencies, like expecting users to configure something before they even have access to it.
- Contradictory steps created by teams working from different assumptions about how something is “supposed” to work.
None of these are “documentation problems.” They’re structural problems that documentation exposes because documentation is the first time anyone tries to describe the system as one connected experience."
https://brandihopkins.com/involve-writers-early/
#TechnicalWriting #SoftwareDevelopment #SoftwareDocumentation #DocsAsProduct #UX
I would highly recommend any techbro (and any developer) to spend some time on slow, laggy or even cutting out internet. So just they can see how their always-online web apps plainly crash when unable to cope with a short offline time. Absolute tragic #UX, loss of data common!
#webdev #usability #accessibility #a11y #web
We have a new full-time developer! Dan Williams joins the #LibreOffice team, working on design, UI and #UX improvements – with an initial focus on macOS. Of course, everything we do is open source, so you can help him: https://blog.documentfoundation.org/blog/2025/12/04/welcome-dan-williams-new-libreoffice-developer-focusing-on-ui-ux/ #foss #openSource #freesoftware
Small #UX design exploration. I built this because a famous message app uses one of these styles and it felt distracting.
Which do you prefer and why?
This *is* a small detail, but it unlocks a much deeper principle about when and why to use animation.
✋ Small digital frictions can slow the spread of misinformation
https://techxplore.com/news/2025-11-small-digital-frictions-misinformation.html
Les carrousels hantent le web, mais qu’en est-il de leur accessibilité ?
Notre collègue @cookingmaia présente les points critiques qui peuvent créer des situations de handicap et propose des solutions concrètes pour rendre vos carrousels accessibles.
À découvrir sur 24 Jours de Web, aux bons soins de @ParisWeb :
Terrible UI behavior in the Apple macOS app store app (v3.0):
When writing an app review, the return key does not create a line break. Return does nothing on first press and submits on the second press, even though the focus does not visibly change and the submit button is not highlighted. You must use shift+return to insert a line break. 🤦
@Mastodon
You know what Mastodon needs, given the nature of its distributed worlwide tooting?
A way to know the time of the day a toot was posted. As in posted: 21:55 GMT or 18:55 Australian-whatever time or 09:55 CERT
THAT would add a lot of context to some toots that don't make sense without knowing the local time of the poster.
What amount of touchscreen-only controls should cars have?
You forgot the option of "None".
Touchscreens should never be used in safety-critical systems.
Every control that takes the driuver's attention away from driving is a safety-critical problem.
I would highly recommend any techbro (and any developer) to spend some time on slow, laggy or even cutting out internet. So just they can see how their always-online web apps plainly crash when unable to cope with a short offline time. Absolute tragic #UX, loss of data common!
#webdev #usability #accessibility #a11y #web
This is so obvious, yet at the same time it seems to me that people rarely really understand what is at stake.
"Most of the breakdowns in a product don’t come from bad intentions or bad work. They come from the way teams divide responsibilities. Engineering focuses on the system behavior. Design focuses on screens and interaction. Product focuses on requirements and scope. Each group works inside its own boundary, and no one is responsible for checking whether all those boundaries line up.
That’s how you end up with a feature that technically “works,” but only if the user magically knows the right order of steps, or already understands a concept that was never explained, or follows a path that only makes sense inside one team’s mental model.
The writer is the first person who has to confront that reality. Not because we’re smarter—because documentation forces us to walk the entire experience in the same order the user will. No shortcuts. No inherited assumptions. No internal knowledge. Just: If I follow this from beginning to end, does it hold together?
That’s when the real gaps surface:
- Prerequisite steps that were never shown in the UI, but the system silently requires.
- Terminology drift where three teams named the same thing differently and nobody noticed.
- Logic branches that exist in engineering’s head, but not in the design or the workflow.
- Error states with no recovery, dropping users into dead ends no one tested.
- Hidden dependencies, like expecting users to configure something before they even have access to it.
- Contradictory steps created by teams working from different assumptions about how something is “supposed” to work.
None of these are “documentation problems.” They’re structural problems that documentation exposes because documentation is the first time anyone tries to describe the system as one connected experience."
https://brandihopkins.com/involve-writers-early/
#TechnicalWriting #SoftwareDevelopment #SoftwareDocumentation #DocsAsProduct #UX
hi! 👋🏻
ich bin walter, ein 32 jahre alter kommunikationsdesigner mit schwerpunkt ui/ux. mit acht jahren berufserfahrung suche ich nun nach einem neuen team und spannenden projekten, bei denen ich meine talente und die liebe zur gestaltung wirkungsvoll einsetzen kann.
mein vollstaendiges, interaktives portfolio schicke ich gerne auf anfrage zu.
wenn du suchst, oder wen kennst, der sucht, freue ich mich ueber kontaktaufnahme fuer jobs in #augsburg.
boosts appreciated. 🫶🏻
Citez moi des gens qui font de l'UX / UI design de façon bénévole dans les logiciels libres.
Je peux vous en citer peut être quatre cinq personnes grand max.
Citez moi des gens qui codent des trucs, toujours bénévolement dans le même domaine. Y'en a archi beaucoup plus.
Bon, comment ca se fait, et comment on fait pour qu'il y ait plus de gens qui fassent des choses dans l'ux / ui ?
Small #UX design exploration. I built this because a famous message app uses one of these styles and it felt distracting.
Which do you prefer and why?
This *is* a small detail, but it unlocks a much deeper principle about when and why to use animation.
✋ Small digital frictions can slow the spread of misinformation
https://techxplore.com/news/2025-11-small-digital-frictions-misinformation.html
We have a new full-time developer! Dan Williams joins the #LibreOffice team, working on design, UI and #UX improvements – with an initial focus on macOS. Of course, everything we do is open source, so you can help him: https://blog.documentfoundation.org/blog/2025/12/04/welcome-dan-williams-new-libreoffice-developer-focusing-on-ui-ux/ #foss #openSource #freesoftware
A space for Bonfire maintainers and contributors to communicate
