Email or username:

Password:

Forgot your password?
All posts Devin's posts Back to profile
4 posts total
Devin Prater

Please boost for reach: To any F-droid developers, is there a way for tags or categories to be added by developers or users, like "accessible", so that users could then filter apps by that tag? This could be useful for people to find accessible #foss apps for Android. Perhaps another tag could be added, "not accessible", so that users or developers could mark apps that are not, or cannot, be made accessible as well.

#a11y #android #fdroid

30 Oct 2022 at 1:59 | Open on devin.masto.host
Devin Prater

There's now a new light markup language, similar to Common Mark, but with lots of new features and fixes. github.com/jgm/djot

14 Jul 2022 at 23:07 | Open on devin.masto.host
Devin Prater

Please boost for reach. So, anyone that is working on FOSS projects like web apps, sites, Linux apps, desktop environments, or other user interfaces, please let me know if you want them tested for accessibility. I can do both CLI, web, and GUI testing, and app testing on Android. I'm running Debian (on a ChromeBook but that's not too important), so just give me the name of the package, or the URL of the site or app. I can also do Flatpak!

#a11y #foss #linux #flatpak #accessibility

26 Jun 2022 at 14:25 | Open on devin.masto.host
Show previous comments
Sylvia van Os

@devinprater Hi, I maintain github.com/CatimaLoyalty/Andro. I already used it myself with Talkback and let some accessibility tools check it so I am hoping the accessibility is in a pretty good state but a more human touch may catch issues I've missed would be awesome :)

26 Jun 2022 at 17:31 | Open on social.tchncs.de
ilja
@devinprater Not really accessibility test, but I do have a question and maybe you'll be able to provide a better answer than what I find online.

There's a thing called EXIF data with which you can add meta data to e.g. images. This also includes things like "description", "caption", etc.

On fedi we have image descriptions, but that's completely different from the EXIF data in the image.

For Pleroma I currently have an MR open to read the EXIF data and prefill the image description with that. The idea is to later go the other way around as well. That way image descriptions can be more portable (i.e. You post an image, give it a proper description, someone downloads it, now other software can still access the image description through the correct EXIF data fields. If someone wants to upload the image again, the image description field will already pre filled and they can choose to keep the description or not.).

The problem I have is that I'm unsure what EXIF data fields I should use. I now use -ImageDescription, if that's empty, it will check -iptc:Caption-Abstract.

So my question is if you happen to know a bit about these things, and if so, what's best to use here.

If this isn't something you know either, do you happen to have some good examples of images that have descriptions like that? Then maybe I can check what fields are used. (Or you can run `exiftool path/to/image` and see what fields are used.)
@devinprater Not really accessibility test, but I do have a question and maybe you'll be able to provide a better answer than what I find online.

There's a thing called EXIF data with which you can add meta data to e.g. images. This also includes things like "description", "caption", etc.
26 Jun 2022 at 17:43 | Open on ilja.space
applejack 🇮🇸:hitlergrin2:

@devinprater What disabilities you cover specifically?

26 Jun 2022 at 17:54 | Open on gameliberty.club
Devin Prater

If you release a program for use by other people, accessibility is your responsibility.
If you create a website for other people to use, accessibility is your responsibility.
If you make a platform for people to come together and meet on, accessibility is your responsibility.
If you make a framework for other developers to build things on top of, accessibility is your responsibility.

20 May 2022 at 8:17 | Open on devin.masto.host
Devin Prater

This means that if you make a script that does something that only you personally will get anything out of, that's fine, make it as inaccessible as you like, only you will deal with any consequences that arise from that. But if you make something you're going to release to the public, and you don't know a thing about accessibility, don't you dare expect users to do to the work of learning your codebase, and making your thing accessible.

20 May 2022 at 8:19 | Open on devin.masto.host
Go Up