[HN Gopher] A beginner's guide to web accessibility
       ___________________________________________________________________
        
       A beginner's guide to web accessibility
        
       Author : saranshk
       Score  : 25 points
       Date   : 2021-03-21 18:47 UTC (4 hours ago)
        
 (HTM) web link (bootcamp.uxdesign.cc)
 (TXT) w3m dump (bootcamp.uxdesign.cc)
        
       | Jaygles wrote:
       | When I was working on a team with an accessibility requirement.
       | The bulk of the work wasn't coloring work, nor writing
       | alternative texts, but ensuring that the website could be
       | navigated well using a screen reader.
       | 
       | We used JAWS[0] and tested every change and new feature with it
       | to ensure users of it could make sense of the website. This was a
       | lengthy process that took a lot of effort and learning on the
       | part of devs to pick up JAWS.
       | 
       | The tough part of it was it being a subjective process. No one
       | can tell you if the final experience was "correct" or not.
       | 
       | This part of web accessibility isn't mentioned as often, but its
       | just as important. Likely because not many people really know
       | about it.
       | 
       | Edit: I think part of it is the high cost of products like JAWS.
       | The current price of a home license is $1,000. A business license
       | is $1,285.
       | 
       | [0] https://www.freedomscientific.com/products/software/jaws/
        
         | steerpike wrote:
         | Most accessibility shops and devs tend to use the free NVDA
         | screenreader[0] for accessibility testing because of the costs
         | associated with JAWS. There are differences between the two
         | (and the other well used screenreader Window-eyes) but NVDA is
         | a damn good product with a decent user base that certainly
         | helps in finding potential hiccups in complex frontend
         | applications. Usually this happens when one of the
         | screenreaders hits something on a webpage that triggers
         | 'interaction mode'[1]
         | 
         | [0] https://www.nvaccess.org/about-nvda/
         | [1]https://tink.uk/understanding-screen-reader-interaction-
         | mode...
        
       | indysigners wrote:
       | If you prefer reader mode, like I do, any Medium-based platform
       | is a PITA cause all images are blurred. Anyone who is on a crappy
       | connection will have them same. What a fuxxing shame! Can we stop
       | using this crappy platform please?
        
       ___________________________________________________________________
       (page generated 2021-03-21 23:01 UTC)