While we believe #Accessibility should be a key component of any project from the outset, one of the advantages of open source is that those with the knowledge are able to contribute to projects to help address shortcomings. @wireshark is "The world's most popular #network protocol analyzer", and a fellow #OpenSource project. Do we know any #A11y coders with an interest in #Networking willing to give them a hand with accessibility? See their post here: https://fosstodon.org/@wireshark@ioc.exchange/114269660077710254 #FOSS
Perhaps that is an unwarranted prejudice. The BBC are generally pretty good with their #a11y practice though.
This is a nice approach to #responsive #tables in #HTML from the BBC
https://www.bbc.co.uk/sport/football/scottish-championship/table
At wider screen sizes, you see the whole thing. Narrower screen sizes have a 'freeze columns' Excel-type effect.
I haven't tested it with ATs myself, I assume they have ;)
If you want to know how a spoon, ai, Matrix and accessibility are connected, then check out the #btconf talk description by @tink with the title “There Is No Spoon” https://beyondtellerrand.com/events/dusseldorf-2025/speakers/leonie-watson#talk
I am working on creating a handbook that describes the assistive technologies available in the FreeBSD operating system, which will be freely available online for anyone to consult. Currently, the effort is focused on gathering and documenting accessibility features for visual impairments, and it is sponsored by the @FreeBSDFoundation
If you are interested in the topic, a public repository is available for suggestions and corrections: https://gitlab.com/alfix/freebsd-accessibility
Windows Narrator is adding a speech viewer / log:
https://blogs.windows.com/windows-insider/2025/03/28/announcing-windows-11-insider-preview-build-26120-3653-beta-channel/#:~:text=Introducing%20speech%20recap%20in%20Narrator
Do not treat it as a proxy for what is actually announced:
https://adrianroselli.com/2020/08/speech-viewer-logs-of-lies.html
[Nouvel article] Framamèmes
Un générateur de mèmes libres et accessibles ! Si vous me suivez en #stream, vous allez enfin pouvoir retrouver et utiliser les différentes mèmes que j'ai redessinés ces dernières semaines
Lire cet article : https://grisebouille.net/framamemes
Le livre best of : https://editions.ptilouk.net/gb10ans
Soutien : https://ptilouk.net/#soutien
I am involved in a web project that includes existing 3rd party videos. I want to make this as accessible as possible.
*Videos are set. I can't change them in any way.
- I've seen AblePlayer recommended most consistently as an accessible browser. Is that status still current?
- Is building the site with an accessible video player "enough"? Can more be done to improve accessibility?
I'm asking here because I'm aware I don't know what I don't know.
More below. 1/n
@ashleemboyer the topic of "which tools will work best for collaboration/work/discussion" is one that keep bubbling up (almost as often as the dreaded "isn't it ironic that the acronym #a11y is itself inaccessible?"). there have been many attempts at using various approaches - from the original (horrid) closed mailing lists of old, to the more open public ones, to forums/discussion boards, shared google docs, and indeed github ... 1/
seeing discussions around how "members of the public (tm)" are prevented from taking part in standards development, because tools like github (where discussion/development happens) may not be familiar to them. while i understand the sentiment, i'd hazard a guess that these members of the public won't understand how the sausage is made, and will be frustrated by the consensus-driven standards development ... it's not just a "let me tell you about MY lived experience" thing #a11y #accessibility
We're looking for someone to join the @TetraLogical team as an accessibility Specialist.
If you're resident in the UK, you can apply on Linkedin:
https://www.linkedin.com/jobs/view/4197046475/
Or directly:
https://misc.tetralogical.com/careers/2025-03-accessibility-specialist/
So #Github released their accessibility documentation and, this will be a helpful resource to so many! https://accessibility.github.com/documentation/guide/repos/ #Git #A11y #Accessibility
According to a person who tested it, screen readers do not, in fact, stop reading alt text at 125 characters in length. This appears to be a myth caudified through a recommendation that they be about that long.
https://yatil.net/blog/there-is-no-character-limit-for-alt-text
Any other #a11y folks who can confirm or deny?