I find myself increasingly asking what value do I get out of existing commercial accessibility testing tools? What do they catch? What do they not catch? I ask because I want to improve on the results, and I also want to know what exactly I need to manual
I find myself increasingly asking what value do I get out of existing commercial accessibility testing tools? What do they catch? What do they not catch? I ask because I want to improve on the results, and I also want to know what exactly I need to m…Robert Dodd (www.linkedin.com)



The Matrix.org Foundation
in reply to Krille - Christian K. • • •Krille - Christian K.
in reply to The Matrix.org Foundation • • •chebra
in reply to Krille - Christian K. • • •Krille - Christian K.
in reply to chebra • • •chebra
in reply to Krille - Christian K. • • •The Matrix.org Foundation
in reply to chebra • • •chebra
in reply to The Matrix.org Foundation • • •Shine
in reply to chebra • • •WhatsApp and other closed source apps have a full dictatorship over the whole protocol and all clients. They can experiment with new features on all users at once, and they can turn them off if they don't meet the expectations for all at once.
How exactly do you want to do this in open world? Some clients will inevitably lag behind, some clients will not implement all features. Even if you didn't allow other clients to experiment with API proposals, they would lag behind the upstream.
The only thing you can do is to give developers tools to create reasonable fallback.
chebra
in reply to Shine • • •The Matrix.org Foundation
in reply to chebra • • •Shine
in reply to chebra • • •The Matrix.org Foundation
in reply to Shine • • •