Accessibility
!a11y@programming.dev 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
Good advice. I splashed out on the kinesis advantage. A two week holiday and switching to the ergo keyboard cured my tennis elbow. It's very expensive and took a long time to get used to but I wouldn't go back.
I also installed Tridactyl Firefox extension for vim bindings. I don't use it often but it is handy when you are coding in vim and need to keep switching to a browser to read documentation.
Edit: The annoying thing about the kinesis is that it only comes in US layout. So when I use it as a UK device I have to do some funny business to get a backslash.
Kinesis keyboards are sooo expensive. I'd buy one if I could, but I'm ok with the described setup for now.