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
Honestly, for such a crucial element, it is infuriating how bad some software gets them. Between narrow, auto-hiding scrollbars and developers who don't understand how rage-inducing scroll-jacking is, it is enough to make me back out of a site / application and either discard what I was going or find an alternative immediately.
Out of interest, why do you use a Wacom tablet as your primary input design, and how do you find using it that way?
I started by using it just when I wanted to free hand / annotate some stuff in various documents or whiteboards. Got so used to it that I eventually stopped using the mouse and haven't plugged one in my work PC in years.
I just like how it's an absolute position mapping of my screen as opposed to a mouse that sends relative movement.
I annotate lots of network diagrams and do lots of whiteboarding. Handwriting with a mouse just sucks.
Now with muscle memory, I can click on anything without dragging or looking.
I'm also more confortable for long periods of time when holding a pen then I am holding a mouse.
There is a scroll circle thingy in the tablet, but that means changing my grip on the pen a bit and I still prefer functional scrollbars because I can just click where I want to go or otherwise just know how far down I already am.
(On the plus side, document preview scrollbars like in VS Code is great)
Other than shitty UIs, there's very few bugs, but some applications do like to glitch the fuck out with absolute positioning (the webex call in progress floating window just bounces around if you try to drag it). 1-2px wide UI elements are dumb.
The Wacom is also probably why I haven't switched to an ultrawide screen for work because the mapping feels squished. (Unless they made an ultrawide ratio tablet, I guess)
I do use a mouse on my home PC though, gaming with a Wacom tablet just doesn't make much sense.