jupiter_rowland

Maybe someone can answer me this accessibility question, especially blind or visually-impaired users as well as Mastodon's alt-text police, just be safe:

When I mention in an image description that a 3-D avatar is wearing a herringbone-patterned tweed jacket and full brogue shoes, do I have to describe in detail what the herringbone fabric pattern and full brogue shoes look like, in general and/or specifically in this case?

I mean, I will mention the colours of these jackets and shoes, I will mention the size of the herringbone pattern, and I will mention that at least the herringbone pattern does not come with any actual surface structure.

But do I have to explain and describe what a herringbone pattern is? And do I have to give a detailed description of the shape and the structure of the toe cap that defines a full brogue shoe in general and these particular full brogue shoes in particular? And if I do so, do I have to also explain the relevant parts of a shoe (main body, toe cap, lace panels, heel cap)?

Or don't I have to describe all this because nobody will need to know it anyway? Because it's commonly known? Because it doesn't matter? Or because absolutely nobody actually cares? Can I actually get away with name-dropping "herringbone pattern" and "full brogue shoes"?

(For the record: Such detail descriptions will probably not go into the alt-text. They will rather go into a long image description in the post itself where I don't have any character limits to worry about.)

@accessibility group @a11y group

#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Blind #VisuallyImpaired #Inclusion #A11y #Accessibility

I'm wondering how my renderings from 3-D virtual worlds could be made accessible to deaf-blind Fediverse users, if there are any.

I've read somewhere that they have no use for visual descriptions. They want to know what someone or something feels like when touched.

But how shall I describe what something feels like that isn't even tangible?

@accessibility group @a11y group

#ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #A11y #Accessibility

@Fediverse News

The cat is out of the bag. Mike Macgirvin's family of Fediverse server applications has a new member: Forte which he has forked off his own streams repository some three weeks ago.

The first announcement came in a comment on a post about Friendica with which everything had begun, just three days ago. The same day, the up-until-then still unannounced Forte repository was discovered. Unlike what's in the streams repository, Forte seems to have a name again, and Mike refers to it as a "project".

(streams), as its predecessor is colloquially being referred to, is already one of the most advanced and innovative server applications in the Fediverse. It has the most elaborate set of permission controls as of yet, even surpassing Hubzilla, the younger one of its surviving ancestors. Also, Mike uses it to develop the implementation of nomadic identity, his own invention from as early as 2011, purely via ActivityPub, including FEP-ef61. So (streams) itself is already a pioneering work, and its development is far from done.

And now we have Forte which promises to be even more advanced. There are no specs yet, much less any public instances. And even if it's the latest fork in 14 years of Fediverse development, I guess it's far from being ready for prime time. But seriously, it's a (streams) fork.

#Fediverse #NomadicIdentity #FEP_ef61 #Friendica #Hubzilla #Streams #(streams) #Forte

@Test

Okay, von Hubzilla nach Lemmy geht kein Wall-to-wall ohne Mention, und Deliverable Mentions mit ! gehen auch nicht, nur normale.

Jetzt will ich mal sehen, was passiert, wenn ich zumindest das Titelfeld nutze und den Titel nicht an den Anfang des Posts stelle.

Mal langsam herantasten bei den Features.