!communitypromo@lemmy.ca • !newcommunities@lemmy.world • !fedigrow@lemmy.zip • !newtolemmy@lemmy.ca
Hi !
Welcome to our fedihack monthly thread ! I hope you are well :)
Here we will talk about features, ui, concept, wiki, communivation and improve our beloved software accross the web and app as :
- bug report
- news features where you want some help
- beautiful ui, graphic help
- accessibility improvement, tips
- a personal project where you seek a new team
Well, i hope we will find something fun to discuss and do together. :)
You must log in or register to comment.
i’ve been experimenting with building an alternative UI for hubzilla and wanted tips on how accessibility can be supported. So far i’ve found online tools like https://www.accessibilitychecker.org/ and using them i get the feedback that my framework is 67% accessibility friendly.
Any experienced folks who can point in the right direction or share tips would be helpful.
And for what the UI would look like (its still in alpha stage) you can check out my profile.Check the WCAG (Web Content Accessibility Guidelines). There’s a tool in the Firefox devtools that checks for some WCAG standards.
Some basics:
- Always provide alt text for images
- Contrast between background and text should be sufficient
- Text should be easily readable (min. 16px font-size) and understandable
- Site should be usable without CSS enabled
- Check if you can navigate your UI without using a mouse
Site should be usable without CSS enabled
css or js? but this seems almost impossible to enforce considering that i’m using a js framework and without css website would just be a mess.
I’m not updated on what current day screenreaders can do. I’d assume they can deal with JS these days, but I don’t know for sure.
Screenreaders read all text on a page out loud for people with visual impairments. How your site looks doesn’t matter to screenreader software. The semantic structure of the HTML matters.
