RetroFed Forums
Your home away from modern life.
Search Categories Forum list Register Log in
About RetroFed
About this forum

!a11y@programming.dev is a community for discussing digital accessibility, sharing techniques and best practices, and talking about accessibility experiences; both good and bad.

Lemmy

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:

  • !transcribing@programming.dev

Useful Resources

3 members · 57 topics · 1 posts

RetroFed

Welcome to the nostalgia-filled piefed instance of yesteryear.

Open Registration with Application questionnaire.

If you have a question or comment you can post in !meta@retrofed.com or message @DosDude@retrofed.com or @Die4Ever@retrofed.com

In case of downtime and/or emergency, we will post updates on @DosDude@mastodon.social

Some rules we try to uphold:

  • Be civil. Bigotry is not welcome. This includes (but is not limited to): transphobia, queerphobia, racism, ageism and ableism. We do not promote hate.
  • Communities need to be Retro or Retro-adjacent.
  • Please don't upload pornographic content. (use an external image host for that)
72 registered users
Administrators: DosDude, Die4Ever
Visit retrofed.com
Accessibility !a11y@programming.dev
Moderators: bugsmith, Pierre-Yves Lapersonne, Toda
New Topic RetroFed Forums Forum Index » Accessibility
 Topics  Replies  Author  Score  Last Post 
"﷽" U+FDFD: ARABIC LIGATURE BISMILLAH AR-RAHMAN AR-RAHEEM (Unicode Character) (unicodeplus.com) 0 bugsmith 2 »
Coloring for Colorblindness (davidmathlogic.com) 0 codeinabox 4 »
Your Browser Can Already Speak a Page (adrianroselli.com) 1 codeinabox 4 »
Low-Vision Programmers Can Now Design 3D Models Independently (spectrum.ieee.org) 0 CombatWombat 5 »
role=presentation is no alternative for aria-hidden=true (www.matuzo.at) 0 codeinabox 2 »
Put aria-hidden=true on decorative SVGs (www.matuzo.at) 0 codeinabox 3 »
aria-haspopup might not do what you think it does (www.matuzo.at) 0 codeinabox 3 »
Notes on relying on the ARIA Authoring Practices Guide (www.stefanjudis.com) 0 codeinabox 1 »
You Know What? Just Don’t Split Words into Letters (adrianroselli.com) 0 codeinabox 2 »
Apple, What Have You Done? (onlinegoddess.net) 0 bugsmith 1 »
I Learned The First Rule of ARIA the Hard Way (css-tricks.com) 0 codeinabox 1 »
EasySpeak: Free, local and Wayland-native desktop voice control software for Linux (GPL 3.0) (fosstodon.org) 0 Novi Sad 1 »
You Can't Opt-Out of Accessibility (vale.rocks) 0 codeinabox 1 »
Don't leave the screen reader hungry (htmhell.dev) 0 codeinabox 1 »
Accessibility, The Origin of Innovation (stuff.interfree.ca) 0 🇨🇦Samuel Proulx🇨🇦 1 »
A11y Considerations in Math on the Web (htmhell.dev) 0 codeinabox 1 »
Accessible by Design: The Role of the 'lang' Attribute (htmhell.dev) 0 codeinabox 1 »
Selfish reasons for building accessible UIs (nolanlawson.com) 0 Novi Sad 1 »
Yes, let's teach LLMs accessibility, but also provide the companies using them with better strategies (hidde.blog) 0 codeinabox 1 »
Skyscanner Empathy Lab (www.youtube.com) 0 codeinabox 1 »
A simple ncurses launcher that opens directories and apps (files.catbox.moe) 0 FarraigePlaisteaċ (sé/é) 1 »
Overview of Apple Accessibility Nutrition Labels for App Store (developer.apple.com) 0 Pierre-Yves Lapersonne 1 »
WCAG 3.0’s Proposed Scoring Model: A Shift In Accessibility Evaluation (www.smashingmagazine.com) 0 Pierre-Yves Lapersonne 1 »
CAPTCHAs are over (in ticketing) (behind.pretix.eu) 0 bugsmith 1 »
How the low-vision community embraced AI smart glasses (www.theverge.com) 0 cm0002 1 »
New Topic Page 1   Next

About this forum

!a11y@programming.dev is a community for discussing digital accessibility, sharing techniques and best practices, and talking about accessibility experiences; both good and bad.

Lemmy

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:

  • !transcribing@programming.dev

Useful Resources

3 members · 57 topics · 1 posts
Powered by RetroFed · PieBB frontend · All times are Europe/Amsterdam