• dan@upvote.au
    link
    fedilink
    arrow-up
    13
    ·
    edit-2
    1 day ago

    Web is a bit easier than native since the browsers handle all the platform-specific details across all common platforms, and you mostly just have to follow some guidelines that aren’t overly technical or arcane. Some examples:

    • Use ARIA roles where appropriate
    • Ensure sufficient contrast between text and background colours. Should at least meet the WCAG level AA which is a 4.5:1 contrast ratio, but ideally meet AAA which is a 7:1 ratio for body text and a 4.5:1 ratio for headings.
    • Ensure you use <label> tags to label for all your <input>s, alt attributes on all images, title attributes where appropriate (e.g. on <table>s to describe the data contained inside the table), etc.

    If you use Firefox, its developer tools have an “Accessibility” tab that can audit for common issues - things like missing labels on checkboxes and radio buttons, colours that don’t meet WCAG contrast ratio requirements, etc.

    It’s a good time to learn more about building accessible sites and apps given it’s becoming a legal requirement in some jurisdictions. For example, the European Accessibility Act (EAA) goes into effect later this year, and it mandates that sites and mobile apps for various industries (like ecommerce, airlines and other transport, media streaming, social media, banks, and some others) meet accessibility guidelines.

    I’m on an all Linux machine and the only accessibility software I know of is Orca and it’s so and so last time I tried it.

    It’s probably worth spinning up a Windows VM to test in NVDA. It’s one of the most popular screen readers and probably the most popular open-source one, but only works on Windows since it deeply hooks into the Microsoft Speech API, accessibility APIs, and and other Windows APIs.

    • Zelaf@sopuli.xyz
      link
      fedilink
      arrow-up
      3
      ·
      14 hours ago

      Dan… I fucking love you. Thank you for this writeup. Not only is it helpful but it gives me encouragement to continue finding ways and figure things out.

      I couple years back when I did my photography education we had an assignment to create a photo book as our final “exam” thing. I decided to document and show the daily life of a blind man and his tools and what he’s had to go through as his blindness got worse over the years. He showed me how he uses his computer and phone and such so I really really saw the importance of accessibility.

      Somewhat luckily I’ve been able to keep the forms somewhat sane due to using component libraries which implement accessibility well. I always make my things in SvelteKit which does have good support for accessibility and I always keep my colours contrasty with as close to as AAA as possible because it’s easier on my own eyes too hahaha.

      There’s a national deaf-blind association nearby and I’ve been thinking of going there to chat about accessibility and website usage with them one day.

      I’m working on digitizing the book I made into a website and of course want to make that website extroniously accessible so even a blind person can hear through descriptive wording of what’s happening in the images. I also plan to make a scrolly-type thing using as little JS as possible which is nicely achievable now with the CSS scroll modifiers that’s been added over the years.

      It’s going to be exciting to see how everything will work out. I can’t thank you enough, while my only computer is a Steam Deck where running VMs is a bit so and so I’m gonna see if I can use some public computer or see if someone in the association can help me test things out and fix things from there.