npub16rd8lagwh224jkyu3v5vehkjtnxmz7t7zfuc9ltsg04qpp87xc7sfh3v3k (npub16rd…3v3k) Thank you for your reply and apologies. I need to clarify a few points.
You say "Accessibility has always been a first-order priority for us." If accessibility has always been a first-order priority for you, why hasn't Nextcloud been built to be accessible by design from the beginning?
So I can hear that accessibility is important to you, but that hasn't always been the case. The page you link to is insufficient to prove that you take accessibility into account. For example, there's nothing about compatibility with the screen readers used by, mostly, blind people to navigate.
It's great to know that the survey was not intended to be a choice of what you would do in 2024.
You ask us to create tickets for problems encountered. But there are far too many problems for it to be effective to create a ticket here and there. For example, there are so many buttons without labels in the web interface that I wouldn't know where to start. I tried to guide a blind person via screen sharing, and ended up having to take over and do it for her because it was so inaccessible. It would be a colossal free job to create these tickets when, on the other hand, you're a company.
You ask us if you excel in the field of accessibility. The answer is clearly no, for the moment.
If I understand correctly, you're in the process of having your tools audited, and that's great news! I hope it's a serious WCAG (or even ATAG https://www.w3.org/WAI/standards-guidelines/atag/) audit, which will identify all the non-compliant points. It will have to be accompanied by an action plan to correct all this, as there will be a lot to do. It's this audit that will provide you with the tickets you're asking us to write.
The stakes of accessibility are huge. Today, we often have to turn to GAFAM tools, which are more accessible, but this is often not feasible in militant collectives, for example. If you make a serious commitment to NextCloud, it will be a huge step forward.
I can't wait to see what happens next. Thank you.
Julie Moynat /
npub106…c8xdu
2024-01-03 10:00:49
in reply to nevent1q…ss08
Author Public Key
npub106kevckeakz2s5upukdc39vmkqnwmcd8y5hdrjkhhedw3sny4vzsgc8xduSeen on
wss://relay.nostr.bandPublished at
2024-01-03 10:00:49Event JSON
{
"id": "99efb64ac80d779337a3cdb9ba8f611c37ad592b26212ee67b10f572344fdc5e",
"pubkey": "7ead9662d9ed84a85381e59b88959bb026ede1a7252ed1cad7be5ae8c264ab05",
"created_at": 1704276049,
"kind": 1,
"tags": [
[
"p",
"d0da7ff50eba9559589c8b28ccded25ccdb1797e127982fd7043ea0084fe363d",
"wss://relay.mostr.pub"
],
[
"p",
"6e8f8827ba165a021e13b7424eb1288258ff4050945f5752f1ce477f5a2cf134",
"wss://relay.mostr.pub"
],
[
"e",
"05f157c33853723f5605b4a5cb60642199ce36f10ecfc194a1ac7784de52fdb8",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://eldritch.cafe/users/juliemoynat/statuses/111691435148341149",
"activitypub"
]
],
"content": "nostr:npub16rd8lagwh224jkyu3v5vehkjtnxmz7t7zfuc9ltsg04qpp87xc7sfh3v3k Thank you for your reply and apologies. I need to clarify a few points.\n\nYou say \"Accessibility has always been a first-order priority for us.\" If accessibility has always been a first-order priority for you, why hasn't Nextcloud been built to be accessible by design from the beginning?\n\nSo I can hear that accessibility is important to you, but that hasn't always been the case. The page you link to is insufficient to prove that you take accessibility into account. For example, there's nothing about compatibility with the screen readers used by, mostly, blind people to navigate.\n\nIt's great to know that the survey was not intended to be a choice of what you would do in 2024.\n\nYou ask us to create tickets for problems encountered. But there are far too many problems for it to be effective to create a ticket here and there. For example, there are so many buttons without labels in the web interface that I wouldn't know where to start. I tried to guide a blind person via screen sharing, and ended up having to take over and do it for her because it was so inaccessible. It would be a colossal free job to create these tickets when, on the other hand, you're a company.\n\nYou ask us if you excel in the field of accessibility. The answer is clearly no, for the moment.\n\nIf I understand correctly, you're in the process of having your tools audited, and that's great news! I hope it's a serious WCAG (or even ATAG https://www.w3.org/WAI/standards-guidelines/atag/) audit, which will identify all the non-compliant points. It will have to be accompanied by an action plan to correct all this, as there will be a lot to do. It's this audit that will provide you with the tickets you're asking us to write.\n\nThe stakes of accessibility are huge. Today, we often have to turn to GAFAM tools, which are more accessible, but this is often not feasible in militant collectives, for example. If you make a serious commitment to NextCloud, it will be a huge step forward.\n\nI can't wait to see what happens next. Thank you.",
"sig": "f4844ae092122d0c2bbb0e6c4838179f3bb0857261c22da5f4dc95e8711a104af025771ade80cf78251ac97f9b17fce4f67ff77bd3bc37854fd3cac2447788f6"
}