!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. :)

  • squirrel@cake.kobel.fyi
    link
    fedilink
    English
    arrow-up
    2
    ·
    25 days ago

    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
    • Saiwal@utsukta.org
      link
      fedilink
      arrow-up
      1
      ·
      25 days ago

      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.

      • squirrel@cake.kobel.fyi
        link
        fedilink
        English
        arrow-up
        1
        ·
        25 days ago

        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.