Accessibility
[email protected] is a community for discussing digital accessibility, sharing techniques and best practices, and talking about accessibility experiences; both good and bad.
Guidelines
- Please keep submissions on topic and try to share high quality content.
- Follow all instance-wide rules, which can be found on the sidebar here: programming.dev
- Don't be a jerk. Just because something you post doesn't explicitly break a rule does not entitle you to post whatever you want, and mods will remove any posts or comments we consider to have been made in bad faith.
- Don't editorialize titles. When sharing something, try to keep the title of whatever article you are sharing, unless it is clearly a clickbait title, and you wish to substitute a simple matter-of-fact title. Please do remove website and author names from the title.
What is Digital Accessibility?
Digital accessibility is the practice of removing barriers that prevent interaction with, or access to, digital systems by people with disabilities. This involves designing and developing websites, mobile applications, software, hardware, and other digital platforms in a way that they can be used by individuals with a range of abilities, including those with visual, auditory, physical, speech, cognitive, and neurological disabilities.
Digital accessibility not only benefits those with disabilities but also enhances the overall user experience, making digital content more usable and understandable for all. In many jurisdictions, it's a legal requirement under disability discrimination laws.
How does one improve digital accessibility in their products?
Key components of digital accessibility include accessible website design, multimedia with features like captions or transcripts, properly formatted digital documents, and accessible software and apps. It also extends to hardware design.
Other Accessibility Related communities:
Useful Resources
- Mozilla Developer Network Accessibility Reference
- UK Government's Guidance and tools for digital accessibility
view the rest of the comments
The post link goes to the news.
The GitHub repo has a link to the site https://orange-opensource.github.io/Tota11ylost/
top right has a language menu with English, Spanish, French
Seems like that's the full thing. Dunno what you mean by demo?
https://orange-opensource.github.io/Tota11ylost/ shows no language menu for me.
I meant demo as in the the project being hosted for others to see and use vs. the source files that are self-hostable.
Unfortunately, the language links are JavaScript links, not href/URL links, so I can't link them. I don't even see JS event handlers on the individual items. lol
Maybe that's the first "digital disability escape game" challenge? /s
Feel free to report a bug on their GitHub repository ; the web site must provide somehow French, English and Spanish content.
What do you mean? Having a quick look in the source code shows that the three languages items are plain HTML hyperlinks. I am not used to front web development, could you bring more details please?
The link in your screenshot links to
#. That's not a share-able languaged link. And I suspect all three have that same href?The only semantically correct reason to link to
#is to jump to the top without JavaScript scroll functions.Links with JavaScript functionality using a
<awithhref#is a relatively common misuse.Feel free to submit an issue in the repository 😁
It seems there are troubles maybe with mobile view port. Feel free to report a bug on their GitHub repository ; the web site must provide somehow French, English and Spanish content.
It seems there is an issue with language selector for small width screens. A bug declaration has been submitted to the original GitHub repository: https://github.com/Orange-OpenSource/Tota11ylost/issues/2 Thank you for your comments!
FYI the bug has been fixed 😁