Flipboard

0 posts0 participants0 posts today

Jupiter Rowland@<a href="https://connectified.com/@masukomi" rel="nofollow noopener noreferrer" target="_blank">masukomi</a> @<a href="https://mastodon.social/@iFixit" rel="nofollow noopener noreferrer" target="_blank">iFixit</a> And this is only mostly a transcript of the spoken words. What if someone actually took upon themselves the effort to describe a video with a timestamped/timecoded combination of visual description, spoken word transcript and non-spoken word audio description? Especially if the visual description is on the same high level of detail that's expected in the Fediverse? CC: @<a href="https://mastodon.scot/@gunchleoc" rel="nofollow noopener noreferrer" target="_blank">GunChleoc</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener noreferrer" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescriptions" rel="nofollow noopener noreferrer" target="_blank">MediaDescriptions</a>

rain trutherI have a question regarding <a href="https://todon.nl/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accessibility</a> and <a href="https://todon.nl/tags/AltText" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AltText</a> / <a href="https://todon.nl/tags/ImageDescription" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ImageDescription</a> / <a href="https://todon.nl/tags/MediaDescription" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MediaDescription</a>.I need to come up with an image description for the attached image for my job. I'm at a complete loss. This is alt text nightmare mode.Are there established methods for describing complex figures such as this one? I would be very happy about some input from people who actually need image descriptions.

Jupiter Rowland@<a href="https://mastodon.radio/@M0YNG" rel="nofollow noopener noreferrer" target="_blank">Christopher M0YNG</a> Just out of curiosity: What would be an appropriate textual description for a video? A description of what the video is about? Or a detailed, time-coded description of the actual visuals throughout the whole video plus a detailed, time-coded transcript of the audio in the video? If the latter, what details are required, regardless of topic and content? CC: @<a href="https://stefanbohacek.online/@stefan" rel="nofollow noopener noreferrer" target="_blank">Stefan Bohacek</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VideoDescription" rel="nofollow noopener noreferrer" target="_blank">VideoDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VideoDescriptions" rel="nofollow noopener noreferrer" target="_blank">VideoDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener noreferrer" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescriptions" rel="nofollow noopener noreferrer" target="_blank">MediaDescriptions</a>

Jupiter RowlandI'm thinking about adding at least one of my channels to <a href="https://communitywiki.org/trunk" rel="nofollow noopener noreferrer" target="_blank">Trunk</a>. I mean, it isn't like I don't have enough followers; they've risen above 500 again. But Trunk would help people follow me for a better reason than just one cool post or comment, all still without having to figure out how to check my profile. That said, Trunk requires you to volunteer on at least one list, in at least one topic. That's where things get difficult. For one, there's <a href="https://communitywiki.org/trunk/grab/Described%20Media" rel="nofollow noopener noreferrer" target="_blank">Described Media</a>. I'm not even kidding: It's a list for people who describe the media which they post. People who add alt-text to their images. Even though everybody in the Fediverse is expected to do it all the time, at least if their posts reach Mastodon in some way. I do it. But I don't do it "the standard Mastodon way". For one, Mastodon's limitations, especially the 500-character limit for posts, don't apply to me. I don't have any character limit in my posts. Thus, nothing forces me to describe and even explain an image only in alt-text because I've got plenty of space in my posts. Besides, <a href="https://hub.netzgemeinde.eu/item/95b6e36d-7fcd-4791-8cc1-c93e8b9975a3" rel="nofollow noopener noreferrer" target="_blank">my images require absolutely massive image descriptions</a>, especially taking all those typical image description guidelines into consideration. That's because none of them are prepared for the edge-cases that are my images. And with "absolutely massive", I don't mean, "800 characters? Are you nuts?! Who's gonna read that?!?" I mean up to <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener noreferrer" target="_blank">over 60,000 characters</a>, and I can guarantee you this is not a typo. Maybe even more in the future. I'm not quite convinced that I'm a good example of a provider of media descriptions, partly because by adhering to general image description rules, I break most of Mastodon's image description rules, partly because next to nobody has the patience to read one image description that's longer than 120 toots or have it read to them by a screen reader, partly also because my own image descriptions become obsolete so quickly whenever I discover something new that I should do in image descriptions. Even if none of this mattered, I don't post images often. Maybe once every couple months. That's because I have to schedule my image posts due to how much time they consume. The 60,000-character description took me two full days to research and write, breakfast to after dinner. And it might become even rarer in the future. I've started <a href="https://streams.elsmussols.net/channel/jupiter_rowland" rel="nofollow noopener noreferrer" target="_blank">a dedicated (streams) channel</a> to be able to post images with sensitive content, including but not limited to eyes and faces. But posting these will eat up the time I could also use to post perfectly safe images on this Hubzilla channel. The Described Media list is rather for people who routinely whip up 200 characters of alt-text in under a minute or so, but who do so at least daily. An even more obvious list, at least at first glance, would be <a href="https://communitywiki.org/trunk/grab/3D%20Virtual%20&%20Augmented%20Reality" rel="nofollow noopener noreferrer" target="_blank">3D Virtual & Augmented Reality</a>, seeing as the primary topic of this channel is <a href="https://hub.netzgemeinde.eu/item/ba1b1cb6-7c18-410e-8752-df4b4face2e0" rel="nofollow noopener noreferrer" target="_blank">OpenSim</a>. In fact, in the long run, I could add two or three channels to this list. But OpenSim does not fit on it. The list is for actual virtual reality, for new virtual reality and augmented reality developments of the 2020s. "The Metaverse" as envisioned by most. It absolutely requires VR or AR headsets, full stop. OpenSim has been using the term "metaverse" routinely since as early as 2007, the year of its inception. But the list is not about "metaverse". It's about VR. And OpenSim is what's commonly called a "pancake". It's made for desktop and laptop computers and their 2-D screens. It does not really work on VR headsets. It does not work on stand-alone VR headsets with integrated graphics hardware at all. That's mainly because VR headsets require a constantly guaranteed frame rate of 60fps. It isn't simplified and cartoonish and geared towards mobile graphics hardware like Horizons or Rec Room or the like. Instead, it's largely photo-realistic, high-detail stuff with high-resolution textures. You may get 60fps out of a dedicated graphics unit on a not-too-highly-detailed sim when you're alone. But have more than a few avatars around, and your fps will drop below 60. Join a party or any other event with a couple dozen avatars, and you're heading for slideshow-level fps. That's because the avatars aren't made by the OpenSim devs and optimised for high performance. They mostly entirely consist of user-supplied stuff and optimised for good looks. Some two years ago, one average avatar had more vertices than an entire scene in World of Warcraft. They've only gotten much, much more complex since then. A liquid-cooled 4090Ti overclocked to kingdom come won't give you 60fps at 1080p at <a href="https://osgrid.org" rel="nofollow noopener noreferrer" target="_blank">OSgrid</a>'s Event Plaza on a Friday night. So, what chances does a stand-alone, passively-cooled headset based on phone hardware have if it has to whip up even more pixels? And none of this is even taking recently-introduced Physically-Based Rendering into account which absolutely requires dedicated graphics hardware with no less than 4GB of dedicated VRAM, preferably at least 8GB. That is, you couldn't use OpenSim on a stand-alone headset anyway. There are only two OpenSim-compatible viewers available right now, they're only available for desktop operating systems, and their highly complex UIs (pull-down menus like you've last seen in Photoshop etc.) are entirely geared towards desktop and laptop computers. In brief: OpenSim is not VR, and it's unlikely to ever truly become VR. Okay, I still have the option to ask one of the four Trunk admins to add an extra "Virtual Worlds" list, arguing that OpenSim, just like Second Life, is not VR and thus doesn't fit onto a VR & AR list. But they might argue that it's close enough to VR & AR for a separate list not being justified. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener noreferrer" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescriptions" rel="nofollow noopener noreferrer" target="_blank">MediaDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenSim" rel="nofollow noopener noreferrer" target="_blank">OpenSim</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenSimulator" rel="nofollow noopener noreferrer" target="_blank">OpenSimulator</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener noreferrer" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener noreferrer" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VR" rel="nofollow noopener noreferrer" target="_blank">VR</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualReality" rel="nofollow noopener noreferrer" target="_blank">VirtualReality</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AR" rel="nofollow noopener noreferrer" target="_blank">AR</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AugmentedReality" rel="nofollow noopener noreferrer" target="_blank">AugmentedReality</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Trunk" rel="nofollow noopener noreferrer" target="_blank">Trunk</a>

Kevin Karhan :verified:<a href="https://chaos.social/@obrhoff" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@obrhoff</a> <a href="https://ieji.de/@BlippyTheWonderSlug" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BlippyTheWonderSlug</a> there's no <a href="https://infosec.space/tags/AltText" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AltText</a> and since I do usually use the :fediverse: on the go in <a href="https://infosec.space/tags/EDGEland" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EDGEland</a>, I don't load media per default, so an <a href="https://infosec.space/tags/ImageDescription" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ImageDescription</a> / <a href="https://infosec.space/tags/MediaDescription" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MediaDescription</a> would be nice.Plus I do have blind and deaf followers so <a href="https://infosec.space/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accessibility</a> is quite important.

Jupiter RowlandThis sounds like good advice... <a href="https://social.growyourown.services/@FediTips" rel="nofollow noopener noreferrer" target="_blank"></a><a href="https://social.growyourown.services/@FediTips" rel="nofollow noopener noreferrer" target="_blank">Fedi.Tips</a> wrote the following <a href="https://social.growyourown.services/@FediTips/112276178981480628" rel="nofollow noopener noreferrer" target="_blank">post</a> Mon, 15 Apr 2024 17:28:51 +0100 If you're posting a video clip or an audio clip attached to a post, remember to include a text description which describes the sound. This is important so that the video or audio is accessible to deaf people. Also, if it's a video, it's important to describe both the sound and the visuals so that it's accessible to everyone. Text descriptions for audio and video are added just like text descriptions for images (exact steps vary depending on which app you use). <a href="https://social.growyourown.services/tags/FediTips" rel="nofollow noopener noreferrer" target="_blank">#FediTips</a> <a href="https://social.growyourown.services/tags/Accessibility" rel="nofollow noopener noreferrer" target="_blank">#Accessibility</a> ...but in my case, this would go out of hand. So much that I've completely discarded the idea of posting in-world videos. I'm someone who has taken most of a day to describe three still images in a post in <a href="https://hub.netzgemeinde.eu/item/8c2b4728-dda5-498b-9f84-2f11e163a4a5" rel="nofollow noopener noreferrer" target="_blank">a combined almost 77,000 characters</a> which take over an hour to read. No, you haven't misread any of this. And <a href="https://hub.netzgemeinde.eu/item/95b6e36d-7fcd-4791-8cc1-c93e8b9975a3" rel="nofollow noopener noreferrer" target="_blank">yes, this effort is necessary in my case.</a> Of course, if I were to describe a video, I'd have to go as much into details. However, there'd be a whole lot more to describe. The video would constantly change. It would show much much more than a still image. There'd be audio that'd require detailed description instead of just name-dropping. All of it. Yes, including panning position. Movements of my avatar would have to be described. Movements of the camera around my avatar as well as independently from my avatar would have to be described. All movements would of course require distances, angles, speeds and changes of speed The description would require a time code: Everything that happens would have to be mentioned including when exactly it happens, and since things might happen quickly or in quick succession, I'm talking about at least tenths of seconds. Ten minutes of in-world video would take me weeks to describe, and the description would be the length of a novel and take a whole day to read. Mastodon users would never see the post with the video because, as far as I know, Mastodon automatically rejects all external posts that exceed 100,000 characters, and I'm talking about millions of characters here. I don't even know if Hubzilla would let me post that much, and Hubzilla doesn't have any character limits except for what the Web server can handle. Nobody would ever read this, so the whole effort would be in vain. But anything less than this would be critically lacking. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener noreferrer" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescriptions" rel="nofollow noopener noreferrer" target="_blank">MediaDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VideoDescription" rel="nofollow noopener noreferrer" target="_blank">VideoDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VideoDescriptions" rel="nofollow noopener noreferrer" target="_blank">VideoDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a>

Jupiter Rowland@<a href="https://universeodon.com/@FreakyFwoof" rel="nofollow noopener noreferrer" target="_blank">Andre Louis</a> What kind of description do you have in mind? Only a brief mention what the audio is? Or a full verbatim transcript of all words in the audio plus full descriptions of all the other sounds in the audio, time-coded in seconds and milliseconds and, if it's music, additionally in bars, quarters and even shorter notes? #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener noreferrer" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescriptions" rel="nofollow noopener noreferrer" target="_blank">MediaDescriptions</a>

Jupiter Rowland@<a href="https://qoto.org/@freeschool" rel="nofollow noopener noreferrer" target="_blank">FreeSchool=Learn Respect Love</a> <blockquote>So I'm happy with that explanation and seems like you've put yourself in with half a chance to do such a small video and even prepped it now! Even this as audio with pics... even here native... I'd listen (not sure elsewhere if I'd click). So as side-note I'll be happy to help you produce such a thing and even invite you to send similar points by audio (your text above as script already pretty much lol) and I'll arrange it and send back to you complete!</blockquote> I'm not going to produce any videos. That'd be way too much of an effort, especially meeting Mastodon's accessibility standards plus my own standards. If this sounds weird, allow me to elaborate. This is not a general-purpose personal channel. This channel is mainly about 3-D virtual worlds. I sometimes post pictures from these virtual worlds. But whenever I do that, I add an image description that's amongst the longest and most extensive anywhere in the Fediverse. I have to put the image description into the post text itself for several reasons, one reason being that they're too long for alt-text. Not only does Mastodon only support alt-text up to 1,500 characters internally, it also cuts off any alt-text from outside that's longer. And mine are longer. I think I have <a href="https://hub.netzgemeinde.eu/item/95b6e36d-7fcd-4791-8cc1-c93e8b9975a3" rel="nofollow noopener noreferrer" target="_blank">very good reasons for writing such long image descriptions</a>. I've actually thought about making in-world videos one day and uploading them to PeerTube. I've decided against it. Accessibility would make it too much of an effort, and it'd make the videos essentially unwatchable. I'd include an audio description that describes the visuals in the videos on at least the same level of detail as my image descriptions. So with an audio description added, <a href="https://www.w3.org/WAI/media/av/description/#video-without-space--creating-a-separate-described-video---if-descriptions-do-not-fit-in-audio-spaces" rel="nofollow noopener noreferrer" target="_blank">the video would have to pause every few seconds for several minutes to give me some time to describe what's on-screen at that point, or what has just appeared on-screen, and explain it if necessary</a>. If I didn't stop the video, the audio would not have a chance to catch up with the ever-changing visuals. Imagine this: <ul><li>Two and a half seconds of actually moving pictures. </li><li>Voiceover describes the camera movement. </li><li>A building comes into view. </li><li>Video stops. </li><li>Voiceover describes the building and explains what needs to be explained to someone who doesn't know anything about anything in the video. </li><li>Ten minutes later, the video starts moving again.</li></ul> The audio description would inflate a ten-minute video to something between six and ten hours. Okay, now, a video about the Fediverse would not be a video about a virtual world that nobody knows. But still, I expect there to be blind or visually-impaired users who come across such a video, play it and wonder, "What is being shown on the screen? What does this video and all that stuff in it look like?" I mean, the visuals wouldn't carry any additional information. They'd be purely illustrational. They wouldn't contribute any content to the explanation, only enhance it. Content-wise, the explanation would work all the same with and without these visuals. But not describing them feels kind of ableist, kind of like not letting non-sighted people experience the video in the exact same way as sighted people. And I always expect there to be non-sighted people who want to have all visuals in a video described in audio. So I might spend weeks making one 10-minute video which would then be inflated to 30 minutes or an hour by the audio description. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener noreferrer" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AudioDescription" rel="nofollow noopener noreferrer" target="_blank">AudioDescription</a>

Jupiter RowlandA couple of times in the past, I've considered making virtual-world videos once I have a sufficiently powerful graphics card and a screen with a solution that won't make me the laughing stock of the Fediverse. I think I have the graphics card now. I was going to publish them on PeerTube which is part of the Fediverse in case you don't know yet. I no longer am. Fulfilling the accessibility requirements in the Fediverse in a sufficiently informative way would not only be an out-right titanic effort. It would make my videos borderline unwatchable. I'm someone who <a href="https://hub.netzgemeinde.eu/item/c8a14063-b4e2-48fa-baf9-cb4faef7225b" rel="nofollow noopener noreferrer" target="_blank">posts a picture of a shelf with a few dozen boxes on it and describes it with over 40,000 words</a>. I have to because people wouldn't even get what's in the picture in the first place if I didn't. Imagine what I'd do in a video that shows much more than that. Much much more. Very early in the video, it'd freeze so I could explain where it would have been made which would take a few minutes. Once everything in-world is visible for the first time, the video would freeze for half an hour or more while I describe and explain absolutely everything within the video frame. Whenever I move or turn, or the camera moves or turns, and something new comes into view, the video would freeze again for several minutes of description and explanation. And so forth. In fact, the video freezes would end up quite long because I would have to speak slowly, clearly and in Simple English. That wouldn't make my descriptions any shorter, though. A five-minute clip would be inflated to six hours or more. The effort to get there would be gargantuan. Even short videos would take me weeks to write the audio description. Then they'd take me some more weeks to re-phrase everything in Simple English. The recording would take several days itself. Of course, I would have to transcribe what I have said in the original video to make subtitles. Then I would have to weave the transcriptions into the audio description script to create special subtitles for deaf-blind users. You never know what they might be interested in, no matter how niche your videos are. And then it'd all be in vain. Nobody would watch the videos, either because they'd be way too long or because nobody is interested in the topic or both. Thus, there wouldn't be any comments on them. So I wouldn't know if I had done everything right by being 100% compliant with WCAG 2.2 and the Fediverse accessibility requirements. Maybe I've missed something and not been thorough enough, but I wouldn't know. Or maybe I've completely overdone it and rendered the video unwatchable by being utterly overcompliant with accessibility requirements, and a tiny fraction of what I've done would have been sufficient. But since nobody would ever comment, I wouldn't know. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusion" rel="nofollow noopener noreferrer" target="_blank">Inclusion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener noreferrer" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescriptions" rel="nofollow noopener noreferrer" target="_blank">MediaDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AudioDescription" rel="nofollow noopener noreferrer" target="_blank">AudioDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AudioDescriptions" rel="nofollow noopener noreferrer" target="_blank">AudioDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a>

Lime Green Gnome<a href="https://mastodon.gamedev.place/@maxim" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@maxim</a> <a href="https://mstdn.social/tags/MediaDescription" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MediaDescription</a> : snip of game: character running & shooting, figure playing string instrument, large boat. Text: Pixelart Game ERRA EXORDIUM Sumerian Mythology Dieselpunk Setting Made in Ukraine

Recent searches

Search options

Administered by:

Server stats:

#MediaDescription