Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Oh, I can definitely talk about this! I'm a FE engineer (10yr industry) with expertise in accessibility (aka a11y), and have directly made contributions to that space
The good news is that the modern web has very rich support for a11y. ARIA is the technology for assistive web, which is very well supported by all major browsers and can support both static and dynamic content. WCAG provides a foundational set of guidelines for accessible web, but the major players (such as Google) often have their own accessibility guidelines with stricter requirements than what WCAG provides. Visual accessibility modes such as high contrast, dark mode, and zoom are also very well supported by the major OS's, and are nowadays configurable for your needs. The best screen reader in my opinion is VoiceOver. The worst is JAWS.
Imo most problems arise at the user and implementation levels. Smaller companies and inexperienced devs may not care about making their websites accessible, which can actually create broken DOM trees that screen readers struggle to parse. Similarly, very few users provide alt text for images (which is what screen readers see). The blame here is on the people rather than the technology.
One upcoming technology I'm actually excited for is AI assisted screen readers, which can look at a website and fill in the blanks where ARIA struggles, like parsing images and graphs. It can also parse websites that lack accessibility information. I've seen demos where you can even ask it questions about the content, like asking for an explanation of the trend in a graph.
Happy to answer any questions.