bbc.github.io/accessibility-ne…
Web: How to document the screen reader user experience - Accessibility, Your Team and You
User experience designers guide - How to document the screen reader user experience for web content. Using your visual as a starting point, we’ll take you step by step through how to document the screen reader UX introducing concepts along the way.bbc.github.io
modulux reshared this.


brennen
in reply to Emmanuele Bassi • • •Emmanuele Bassi
in reply to brennen • • •Emmanuele Bassi
in reply to Emmanuele Bassi • • •brennen
in reply to Emmanuele Bassi • • •sure, sure. polls don't work.
on the other hand, opt-out metrics are a cracked door for future bad actors. it's not that i don't trust the good faith individuals trying very hard to design relatively benign versions of this. it's that i simply don't trust any version of it to stay benign, because software, programmers, and corporations are in the main bad.
Emmanuele Bassi
in reply to brennen • • •brennen
in reply to Emmanuele Bassi • • •Dmitry Tantsur
in reply to Emmanuele Bassi • • •Drew 🐘
in reply to Emmanuele Bassi • • •@brennen That is perhaps true of polls run directly by an open source project. Those projects could pay for the expertise required to run polls effectively and analyze the resulting data holistically.
Telemetry is also statistically biased. There is zero assurance that you're assessing the entire population of users. You're effectively oversampling users for whom the software already works well. You cannot appropriately develop weights to counter that because of the population problem.
Emmanuele Bassi
Unknown parent • • •Cleo Menezes Jr.
in reply to Emmanuele Bassi • • •> you should ask them
Telemetry that is being proposed: automate what to ask and just answer what you want.
These people just want to complain and, okay. Let's just ignore them, they always find something else to complain about. Let's move on.
Emmanuele Bassi
Unknown parent • • •Scott Trakker
in reply to Emmanuele Bassi • • •Emmanuele Bassi
in reply to Scott Trakker • • •@Scott_Trakker You mean like: blogs.gnome.org/aday/2023/01/1… ?
It doesn't work, because it self-selects the pool of people responding; unless you're Valve, and have 100 million users, you're not getting representative data. It's also incredibly hard to make it granular without going into full 1hr survey territory, which will limit the number of people responding even further.
There's a whole ass science behind polling, and there's no "simple" solution whatsoever.
gnome-info-collect: What we learned – Form and Function
blogs.gnome.orgScott Trakker
in reply to Emmanuele Bassi • • •Yes, exactly like the research they did in the begining of this year, but with the difference that users can use GTK4 app. As you can read in the article, Allan Day was quite positive about the outcome.
The advantages of this approach is that you can drive user engagement a lot. Imagine the GNOME UX-designer asking us the monitor a certain part of the desktop-environment and we all help them to collect the data!
Emmanuele Bassi
in reply to Scott Trakker • • •Emmanuele Bassi
in reply to Emmanuele Bassi • • •Scott Trakker
in reply to Emmanuele Bassi • • •Let me put it different: I think it's important that when you start doing telemetry, you have to expose it to the user interface so that people now what's going on in the background. This can be in the system setting or in a separate application. It's important that the user has the feeling that he/she is control. It would be great if the user can decide what to monitor and for how long.
Emmanuele Bassi
in reply to Scott Trakker • • •Scott Trakker
in reply to Emmanuele Bassi • • •@fedora
>he noted the issues this approach has—self-selection of the audience
Did he? I didn't read that.
>The idea that asking people to participate in a collection campaign will drive engagement is also quite far fetched
I don't think this is far fetched at all.
>What kind of data you can collect if you require an external tool to be installed and executed?
I don't see a problem.
Emmanuele Bassi
in reply to Scott Trakker • • •