<p>Adding ALT text to social cards media<br><a href="https://stefanbohacek.com/blog/adding-alt-text-to-article-thumbnails-on-social-media/" rel="nofollow" class="ellipsis" title="stefanbohacek.com/blog/adding-alt-text-to-article-thumbnails-on-social-media/"><span class="invisible">https://</span><span class="ellipsis">stefanbohacek.com/blog/adding-</span><span class="invisible">alt-text-to-article-thumbnails-on-social-media/</span></a></p><p><a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/webdev/" rel="tag">#WebDev</a> <a href="/tags/opengraph/" rel="tag">#OpenGraph</a></p>
a11y
<p>2024 was a nice year for <a href="/tags/opensource/" rel="tag">#opensource</a> contributions in my side <img src="https://neodb.social/media/emoji/framapiaf.org/blobnomcookie.png" class="emoji" alt=":blobnomcookie:" title=":blobnomcookie:"> </p><p>Improvement of l10n / i18n for <span class="h-card"><a href="https://mastodon.online/@IceCubesApp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>IceCubesApp</span></a></span> <span class="h-card"><a href="https://mastodon.social/@impressia" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>impressia</span></a></span> and also for Tella, Monal, <a href="/tags/osmand/" rel="tag">#OsmAnd</a> and Strongbox <a href="/tags/ios/" rel="tag">#iOS</a> apps.</p><p>Some <a href="/tags/a11y/" rel="tag">#a11y</a> guidelines on a11y-guidelines.orange.com have been updated.</p><p>I was mainly focused that year on the two design systems of <a href="/tags/orange/" rel="tag">#Orange</a>, with the last one taking a lot of my time (<a href="https://github.com/Orange-OpenSource/ouds-ios" rel="nofollow" class="ellipsis" title="github.com/Orange-OpenSource/ouds-ios"><span class="invisible">https://</span><span class="ellipsis">github.com/Orange-OpenSource/o</span><span class="invisible">uds-ios</span></a>).</p><p>Not that bad in the end <img src="https://neodb.social/media/emoji/framapiaf.org/blobcatcoffee.png" class="emoji" alt=":blobcatcoffee:" title=":blobcatcoffee:"></p><p><a href="/tags/iosdev/" rel="tag">#iosdev</a> <a href="/tags/viededev/" rel="tag">#VieDeDev</a></p>
Edited 1y ago
<p>As usual, another dumb implementation in <a href="/tags/fintech/" rel="tag">#FinTech</a> <a href="/tags/philippines/" rel="tag">#Philippines</a> scene.</p><p>A certain №1 (or №2?) <a href="/tags/bank/" rel="tag">#bank</a> is now blocking <a href="/tags/android/" rel="tag">#Android</a> <a href="/tags/accessibility/" rel="tag">#accessibility</a> features, they tagged it as "Compromised device". 🤦🏽🤷🏽</p><p><a href="/tags/a11y/" rel="tag">#a11y</a></p>
Edited 236d ago
<p>How should text-to-speech handle ruby annotations like furigana in Japanese or pinyin in Chinese so screen reader users get the intended experience?</p><p>We just published a new W3C draft note from the Internationalization Activity: Text-to-Speech Rendering of Electronic Documents Containing Ruby: User Requirements</p><p>This explores diverse reading strategies across writing systems and defines essential user needs.</p><p><a href="https://www.w3.org/TR/ruby-tts-req/" rel="nofollow"><span class="invisible">https://</span>www.w3.org/TR/ruby-tts-req/</a></p><p><a href="/tags/internationalization/" rel="tag">#Internationalization</a> <a href="/tags/a11y/" rel="tag">#A11y</a></p>
<p>GrapheneOS: Where Licenses Matter More Than People</p><p>GrapheneOS could have shipped real accessibility support. They had a screen reader. They had a libre speech engine — one they requested a feature from. They got that feature.</p><p>And then they said no.<br>Because the license was GPLv3.</p><p>They’ll ship sandboxed Google Play Services.<br>They’ll let you install GPLv3 software from their app store.<br>But a working screen reader for blind users?<br>Blocked. On principle.</p><p>This isn’t a technical limitation.<br>This is not a matter of priorities.<br>This is cruelty by ideology — and they’re proud of it.</p><p>So here it is. My full public dissection of the excuses, the hypocrisy, and the sheer contempt they’ve shown to the people who need privacy and security most: the disabled.</p><p>They chose licensing purity over basic humanity.<br>I chose to write this.</p><p><a href="https://fireborn.mataroa.blog/blog/grapheneos-where-licenses-matter-more-than-people/" rel="nofollow" class="ellipsis" title="fireborn.mataroa.blog/blog/grapheneos-where-licenses-matter-more-than-people/"><span class="invisible">https://</span><span class="ellipsis">fireborn.mataroa.blog/blog/gra</span><span class="invisible">pheneos-where-licenses-matter-more-than-people/</span></a></p><p><a href="/tags/grapheneos/" rel="tag">#GrapheneOS</a> <a href="/tags/accessibility/" rel="tag">#Accessibility</a> <a href="/tags/foss/" rel="tag">#FOSS</a> <a href="/tags/blind/" rel="tag">#Blind</a> <a href="/tags/disabilitytech/" rel="tag">#DisabilityTech</a> <a href="/tags/inclusion/" rel="tag">#Inclusion</a> <a href="/tags/gplv3/" rel="tag">#GPLv3</a> <a href="/tags/espeak/" rel="tag">#espeak</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/security/" rel="tag">#Security</a> <a href="/tags/freesoftware/" rel="tag">#FreeSoftware</a> <a href="/tags/disabilityrights/" rel="tag">#DisabilityRights</a> <a href="/tags/android/" rel="tag">#Android</a> <a href="/tags/rant/" rel="tag">#Rant</a> <a href="/tags/techshame/" rel="tag">#TechShame</a></p>
<p>If your app supports multiple languages you can test it on device in another language without changing your entire device's language with a per app setting. </p><p>It even works with widgets! </p><p>This is not the case with some per-app accessibility settings, which I did open feedback about.</p><p><a href="/tags/swiftui/" rel="tag">#SwiftUI</a> <a href="/tags/accessibility/" rel="tag">#accessibility</a> <a href="/tags/a11y/" rel="tag">#a11y</a></p>
Edited 1y ago
<p>« Econception logicielle, pourquoi et comment coder "green" » <img src="https://neodb.social/media/emoji/framapiaf.org/blobcatcoffee.png" class="emoji" alt=":blobcatcoffee:" title=":blobcatcoffee:"> </p><p><a href="https://speakerdeck.com/pylapp/econception-logicielle-pourquoi-et-comment-coder-green-masterclass-universite-toulouse-iii" rel="nofollow" class="ellipsis" title="speakerdeck.com/pylapp/econception-logicielle-pourquoi-et-comment-coder-green-masterclass-universite-toulouse-iii"><span class="invisible">https://</span><span class="ellipsis">speakerdeck.com/pylapp/econcep</span><span class="invisible">tion-logicielle-pourquoi-et-comment-coder-green-masterclass-universite-toulouse-iii</span></a></p><p><a href="/tags/ecodesign/" rel="tag">#ecodesign</a> <a href="/tags/ecoconception/" rel="tag">#ecoconception</a> <a href="/tags/opensource/" rel="tag">#opensource</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/i18n/" rel="tag">#i18n</a> <a href="/tags/androiddev/" rel="tag">#androiddev</a> <a href="/tags/iosdev/" rel="tag">#iosdev</a> <a href="/tags/webdev/" rel="tag">#webdev</a> <a href="/tags/viededev/" rel="tag">#VieDeDev</a></p><p>Support sous CC-BY-SA<br> <img src="https://neodb.social/media/emoji/framapiaf.org/cc.png" class="emoji" alt=":cc:" title=":cc:"> <img src="https://neodb.social/media/emoji/framapiaf.org/ccby.png" class="emoji" alt=":ccby:" title=":ccby:"> <img src="https://neodb.social/media/emoji/framapiaf.org/cc_sa.png" class="emoji" alt=":cc_sa:" title=":cc_sa:"></p>
<p>Si vous utilisez Firefox et Europresse pour lire des articles de presse (via le pass BNF, au hasard) et que vous n'en pouvez plus de cet horrible texte justifié et écrit trop petit, vous avez dû remarquer que le mode lecture de Firefox ne fonctionne pas sur ce site.</p><p>J'ai l'extension qu'il vous faut pour retrouver un confort de lecture parfait : <a href="https://addons.mozilla.org/fr/firefox/addon/activate-reader-view/" rel="nofollow">Activate reader view</a>. Elle force le mode lecture à être disponible. Et voilà 🥳</p><p><a href="/tags/bnf/" rel="tag">#BNF</a> <a href="/tags/europresse/" rel="tag">#Europresse</a> <a href="/tags/firefox/" rel="tag">#Firefox</a> <a href="/tags/accessibilité/" rel="tag">#accessibilité</a> <a href="/tags/a11y/" rel="tag">#a11y</a></p>
<p>Something I recently discovered to be possible in TiddlyWiki is using `clamp()` in the `font-size` settings. It's sweet!</p><p><a href="https://whtwnd.com/youronly.one/3lukcyypixm2z" rel="nofollow" class="ellipsis" title="whtwnd.com/youronly.one/3lukcyypixm2z"><span class="invisible">https://</span><span class="ellipsis">whtwnd.com/youronly.one/3lukcy</span><span class="invisible">ypixm2z</span></a></p><p><a href="/tags/css/" rel="tag">#CSS</a> <a href="/tags/tiddlywiki/" rel="tag">#TiddlyWiki</a> <a href="/tags/trick/" rel="tag">#Trick</a> <a href="/tags/tip/" rel="tag">#Tip</a> <a href="/tags/accessibility/" rel="tag">#Accessibility</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/wiki/" rel="tag">#Wiki</a></p>
<p>This year brought great improvements to <a href="/tags/accessibility/" rel="tag">#accessibility</a> in GNOME, including:</p><p>• Full accessibility of GNOME Web<br>• Tons of improvements to Calendar<br>• Screen reader integration for Notifications<br>• GTK apps integrated w/Windows & macOS accessibility<br>• Configure <a href="/tags/orca/" rel="tag">#Orca</a> screen reader from GNOME Settings<br>• Accessibility from the start on the login screen</p><p>Help us reach 1,500 <a href="/tags/friendsofgnome/" rel="tag">#FriendsOfGNOME</a> so we can focus on accessibility even more in 2026:</p><p><a href="https://donate.gnome.org" rel="nofollow"><span class="invisible">https://</span>donate.gnome.org</a></p><p><a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/gnome/" rel="tag">#GNOME</a> <a href="/tags/foss/" rel="tag">#FOSS</a> <a href="/tags/opensource/" rel="tag">#OpenSource</a></p>
<p>I may use this image in a future presentation. I have found it on the Fediverse but lost the originator, and of course I would want to credit them.</p><p>Could anyone point me to the post it was excerpted from please?</p><p><a href="/tags/a11y/" rel="tag">#a11y</a> <img src="https://neodb.social/media/emoji/piaille.fr/boost_request.png" class="emoji" alt=":boost_request:" title=":boost_request:"></p>
<p>Hi Folks,</p><p>I am looking for screen reader users to test a site taking approximately one hour. This is a paid gig - $50 via a gift card. Please ping me for more details. </p><p>Please boost for reach.</p><p>Thanks!</p><p><a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/accessibility/" rel="tag">#accessibility</a> <a href="/tags/screenreader/" rel="tag">#ScreenReader</a></p>
Edited 63d ago
<p>Something I recently discovered to be possible in TiddlyWiki is using `clamp()` in the `font-size` settings. It's sweet!<a href="https://whtwnd.com/youronly.one/3lukcyypixm2z" rel="nofollow">whtwnd.com/youronly....</a><a href="/tags/css/" rel="tag">#CSS</a> <a href="/tags/tiddlywiki/" rel="tag">#TiddlyWiki</a> <a href="/tags/trick/" rel="tag">#Trick</a> <a href="/tags/tip/" rel="tag">#Tip</a> <a href="/tags/accessibility/" rel="tag">#Accessibility</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/wiki/" rel="tag">#Wiki</a> <br><br><a href="https://whtwnd.com/youronly.one/3lukcyypixm2z" rel="nofollow">TiddlyWiki Legibility Tip: fon...</a></p>
<p>i want to hear from people who use screen readers: what makes alt text useful to you? what doesn't help?</p><p><a href="/tags/accessibility/" rel="tag">#accessibility</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/blind/" rel="tag">#blind</a> <a href="/tags/alttext/" rel="tag">#alttext</a></p>
<p>Just received our first prototype of a Nickel-metal Hydride battery charger with a USB plug. This board is made to charge from 1 to 6 cells in series and supports a thermister for sensing overheating batteries.</p><p>This circuit design is planned to be a part of a pen-like stylus with a camera and haptic feedback for blind people to feel visual art.</p><p><a href="https://codeberg.org/bcecoop/bce-pcb-bq25172dsgr" rel="nofollow" class="ellipsis" title="codeberg.org/bcecoop/bce-pcb-bq25172dsgr"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/bcecoop/bce-pcb-b</span><span class="invisible">q25172dsgr</span></a></p><p><a href="/tags/blind/" rel="tag">#blind</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/accessibility/" rel="tag">#accessibility</a> <a href="/tags/ee/" rel="tag">#ee</a> <a href="/tags/pcb/" rel="tag">#pcb</a> <a href="/tags/fosh/" rel="tag">#fosh</a> <a href="/tags/foss/" rel="tag">#foss</a> <a href="/tags/bce/" rel="tag">#bce</a> <a href="/tags/prototype/" rel="tag">#prototype</a> <a href="/tags/maker/" rel="tag">#maker</a> <a href="/tags/nimh/" rel="tag">#nimh</a> <a href="/tags/battery/" rel="tag">#battery</a> <a href="/tags/charger/" rel="tag">#charger</a></p>
<p>Hey all,</p><p>I have a friend who's been trying to get on Mastodon but tells me that it doesn't seem to play well with screen readers. I know there are plenty of people on the fedi who do use screen readers, but I have no experience with them myself, so I can't really direct him.</p><p>Can someone who does use a <a href="/tags/screenreader/" rel="tag">#ScreenReader</a> point me in the direction of some resources that might be useful?<br><a href="/tags/askfedi/" rel="tag">#AskFedi</a> <a href="/tags/a11y/" rel="tag">#a11y</a></p>
<p>So, in reading the notes for the latest Mona update, which came out last week, I seem to be having trouble understanding what they mean by choosing list style to make the tab bar easily navigable. Does anyone have any ideas on this? My tab bar seems to be jumping around a little bit. <a href="/tags/accessability/" rel="tag">#Accessability</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <span class="h-card"><a href="https://mastodon.social/@MonaApp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>MonaApp</span></a></span></p>
<p>We hereby challenge _all_ other messaging apps, FOSS or not, to provide a more convenient private onboarding experience than <a href="/tags/deltachat/" rel="tag">#deltachat</a> </p><p>1. Install app <br>2. "Create new profile" <br>3. Enter nick name, tap "Agree and continue"<br>4. Tap "+" and "new contact" and provide/scan qr code/link</p><p>Voila! A secure private chat, familiar to those coming from Whatsapp or Telegram (without "AI", with <a href="/tags/a11y/" rel="tag">#a11y</a>).</p><p>Note: chat identities are private and can not be queried or discovered. Servers keep no track or metadata</p>
Edited 155d ago
<p>Just placed an order for a new prototype PCB (Printed Circuit Board) for makers. This one charges NiMH (Nickel-metal Hydride) rechargeable batteries with charging speed options, support for up to 6 cells, temperature sensor, and USB-C plug.</p><p>This is a step toward our first accessibility product for blind people to feel visual art through a haptic pen-like stylus interface.</p><p><a href="https://codeberg.org/bcecoop/bce-pcb-bq25172dsgr" rel="nofollow" class="ellipsis" title="codeberg.org/bcecoop/bce-pcb-bq25172dsgr"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/bcecoop/bce-pcb-b</span><span class="invisible">q25172dsgr</span></a></p><p><a href="/tags/blind/" rel="tag">#blind</a> <a href="/tags/accessibility/" rel="tag">#accessibility</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/pcb/" rel="tag">#pcb</a> <a href="/tags/prototype/" rel="tag">#prototype</a> <a href="/tags/fosh/" rel="tag">#fosh</a> <a href="/tags/foss/" rel="tag">#foss</a> <a href="/tags/freehardware/" rel="tag">#freehardware</a> <a href="/tags/freesoftware/" rel="tag">#freesoftware</a> <a href="/tags/copyleft/" rel="tag">#copyleft</a> <a href="/tags/ee/" rel="tag">#ee</a></p>
<p>Entamez l'année 2026 avec de bonnes habitudes ! 🙌</p><p>Facilitez votre veille sur l'accessibilité numérique en vous abonnant à la newsletter Access42.</p><p>Chaque mois, vous recevrez une sélection d’actualités et de ressources sur l'accessibilité et le handicap :</p><p><a href="https://a42.fr/newsletter" rel="nofollow"><span class="invisible">https://</span>a42.fr/newsletter</a></p><p>Envie d'un aperçu ? Découvrez l'édition précédente :<br><a href="https://a42.fr/newsletter-63" rel="nofollow"><span class="invisible">https://</span>a42.fr/newsletter-63</a></p><p><a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/accessibilité/" rel="tag">#accessibilité</a> <a href="/tags/handicap/" rel="tag">#handicap</a> <a href="/tags/newsletter/" rel="tag">#newsletter</a></p>
<p>Too late for CSUNATC, but not too late to be the envy of your co-workers.</p><p>Available in multiple colors and styles (can add more if you have a request).</p><p>• Black text: <a href="https://aardrian.threadless.com/designs/pourf-neue-helvetica-black/mens/t-shirt/classic?variation=front&color=yellow_haze" rel="nofollow" class="ellipsis" title="aardrian.threadless.com/designs/pourf-neue-helvetica-black/mens/t-shirt/classic?variation=front&color=yellow_haze"><span class="invisible">https://</span><span class="ellipsis">aardrian.threadless.com/design</span><span class="invisible">s/pourf-neue-helvetica-black/mens/t-shirt/classic?variation=front&color=yellow_haze</span></a><br>• White text: <a href="https://aardrian.threadless.com/designs/pourf-neue-helvetica-white/mens/t-shirt/classic?variation=front&color=maroon" rel="nofollow" class="ellipsis" title="aardrian.threadless.com/designs/pourf-neue-helvetica-white/mens/t-shirt/classic?variation=front&color=maroon"><span class="invisible">https://</span><span class="ellipsis">aardrian.threadless.com/design</span><span class="invisible">s/pourf-neue-helvetica-white/mens/t-shirt/classic?variation=front&color=maroon</span></a></p><p><a href="/tags/wcag/" rel="tag">#WCAG</a> <a href="/tags/overlay/" rel="tag">#overlay</a> <a href="/tags/accessibility/" rel="tag">#accessibility</a> <a href="/tags/a11y/" rel="tag">#a11y</a></p>
<p>We've just received a new manufactured prototype of a nickel metal hydride battery charger that handles the charging from 1 to 6 cells from a standard USB-C cable.</p><p><a href="https://codeberg.org/bcecoop/bce-pcb-bq25172dsgr" rel="nofollow" class="ellipsis" title="codeberg.org/bcecoop/bce-pcb-bq25172dsgr"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/bcecoop/bce-pcb-b</span><span class="invisible">q25172dsgr</span></a></p><p><a href="/tags/blind/" rel="tag">#blind</a> <a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/accessibility/" rel="tag">#accessibility</a> <a href="/tags/fosh/" rel="tag">#fosh</a> <a href="/tags/foss/" rel="tag">#foss</a> <a href="/tags/pcb/" rel="tag">#pcb</a> <a href="/tags/ee/" rel="tag">#ee</a> <a href="/tags/bce/" rel="tag">#bce</a> <a href="/tags/pensee/" rel="tag">#pensee</a></p>
<p>Commentez les nouvelles traductions candidates en français des WCAG 2.1 et 2.2 jusqu’au 6 avril 2026 ! 📣</p><p>Cet appel à commentaires est public. Ça signifie que tout le monde peut faire part de ses remarques en envoyant un e-mail à la liste de diffusion du <span class="h-card"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span>.</p><p>On vous guide pas à pas sur notre site :</p><p><a href="https://a42.fr/relecture-trad-fr-wcag-03-26" rel="nofollow" class="ellipsis" title="a42.fr/relecture-trad-fr-wcag-03-26"><span class="invisible">https://</span><span class="ellipsis">a42.fr/relecture-trad-fr-wcag-</span><span class="invisible">03-26</span></a></p><p><a href="/tags/a11y/" rel="tag">#a11y</a> <a href="/tags/wcag/" rel="tag">#WCAG</a> <a href="/tags/w3c/" rel="tag">#W3C</a> <a href="/tags/accessibilité/" rel="tag">#accessibilité</a> <a href="/tags/numérique/" rel="tag">#numérique</a></p>
<p><span class="h-card"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> recharters its Internationalization <a href="/tags/workinggroup/" rel="tag">#WorkingGroup</a> through March 2029<br>▶️ <a href="https://www.w3.org/International/groups/wg/charter-2026.html" rel="nofollow" class="ellipsis" title="www.w3.org/International/groups/wg/charter-2026.html"><span class="invisible">https://</span><span class="ellipsis">www.w3.org/International/group</span><span class="invisible">s/wg/charter-2026.html</span></a></p><p>The group's new work includes HTML Ruby Markup Extensions (better support for phonetic annotations), Ruby Text-to-Speech (<a href="/tags/a11y/" rel="tag">#a11y</a> support for <a href="/tags/ruby/" rel="tag">#ruby</a> annotations) and Message Resources (for easier localization) <a href="/tags/i18n/" rel="tag">#i18n</a> <span class="h-card"><a href="https://w3c.social/@webi18n" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>webi18n</span></a></span></p><p>📢 If you believe the Web should speak your language, join or rejoin the group!<br><a href="https://www.w3.org/groups/wg/i18n-core/join/" rel="nofollow" class="ellipsis" title="www.w3.org/groups/wg/i18n-core/join/"><span class="invisible">https://</span><span class="ellipsis">www.w3.org/groups/wg/i18n-core</span><span class="invisible">/join/</span></a></p>
