• xthexder@l.sw0.com
    link
    fedilink
    arrow-up
    2
    ·
    20 hours ago

    I’m curious what parts would be challenging to use with a screen reader? If a site just has basic links and no JS, I can’t really think of anything unless the tab layout is somehow completely shuffled due CSS.

    • Vincent@feddit.nl
      link
      fedilink
      arrow-up
      1
      ·
      9 hours ago

      A comprehensive answer is out of scope and probably best given by a true accessibility specialist, but for example, if you only use <div> tags for everything, a lot of the screen reader’s affordances for navigating are unusable. Images that carry information but not in their alt text are another simple example.

      And then there are parts where JS could actively help. For example, if you have a tabbed interface, but clicking a tab results in a full page refresh, the screen reader loses all context.

      Also keep in mind that there’s more to assistive technology than just screen readers, e.g. sufficient colour contrast and keyboard navigability are important to many people. Too many websites still get those basics wrong.

      • xthexder@l.sw0.com
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        32 minutes ago

        Thanks for responding. I’m not really a web dev, so I haven’t thought about it much.

        The tab layout and <div> examples were definitely not things I was thinking about. I guess that’s a good incentive to use tags like <section> and <article>` instead of divs with CSS classes.

        I’m actually a bit color blind myself, so I appreciate sites being high contrast and not relying on color alone for indicators. A surprising number of sites completely break when trying to zoom in and make text bigger too, which is often due to bad floating layouts. Especially if it’s resized with JS…