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
This is the best summary I could come up with:
This includes a stark option, with black-and-white and detail-diminished backgrounds and characters' flattened shapes filled in with either horizontal or vertical striped lines.
But what started out as excitement in the fighting game and accessibility communities about expanded offerings has shifted into warnings about the potential for migraines, vertigo, or even seizures.
Accessibility consultant Ian Hamilton reposted a number of people citing migraines, nausea, or seizure concerns while also decrying the general nature of colorblind "filters" as an engineering-based approach to a broader design challenge.
He added in the thread that shipping a game that contained a potentially seizure-inducing mode could result in people inadvertently discovering their susceptibility, similar to an infamous 1997 episode of the Pokémon TV series.
James Berg, accessibility project manager at Xbox Game Studios, went further into explaining why moving solid lines on a video might cause issues for people affected by strobing.
"These color vision options are a rare part of the fighting game genre, but they are still being researched and we intend to expand on them in the future," Harada wrote.
The original article contains 676 words, the summary contains 178 words. Saved 74%. I'm a bot and I'm open source!