fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-10 00:12:09 +00:00
Code Issues Projects Releases Wiki Activity

New note: blindness month ama

Browse source
This commit is contained in:
Rohan Kumar 2022-10-07 11:35:57 -07:00
parent e618319e3a
commit cc9baf696d
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
content/notes/re-blindness-awareness-month-ama.md Normal file
View file

@ -0,0 +1,13 @@
---
title: "Re: blindness awareness month AMA"
date: 2022-10-07T11:35:57-07:00
replyURI: "https://mspsocial.net/@bright_helpings/109104639750302917"
replyTitle: "October is Blindness Awareness Month, AMA"
replyType: "SocialMediaPosting"
replyAuthor: "Erik"
replyAuthorURI: "https://cosmolinguist.dreamwidth.org"
---
The most common and major accessibility (<abbr title="accessibility">a11y</abbr>) issues tend to be documented and well-known among <abbr>a11y</abbr> practitioners; however, "smaller" or "niche" issues (for lack of a better term) tend to go unnoticed. For instance, I recently learned that over-use of soft-hyphens can trip up the speech synthesis of the NVDA screen reader, and styling superscripts/subscripts a certain way can stop screen readers from announcing them. I also learned about how performance issues can cause delays in screen readers, making content exposed to screen readers fall out-of-sync with the actual page. We won't learn about this in accessibility tutorials or W3C documentation! The only way to discover these issues is to use many screen readers for a long time.
What are some accessibility hazards---or even mild annoyances---you experience, that you _don't_ think most <abbr>a11y</abbr> practitioners learn about? Is there a common annoyance you wouldn't normally bring up because it seems "too minor"?