- From: Karen Lewellen <klewellen@shellworld.net>
- Date: Wed, 18 Dec 2019 00:00:59 -0500 (EST)
- To: caroline <woodward.caroline@gmail.com>
- cc: w3c-wai-ig@w3.org
Well speaking personally, there are so many screen readers available, with individual preferences naturally and understandably impossible to anticipate, I fear seeking a pattern leans too much into the one size fits all concept of access. For example, the sample you provided in your post was not spoken as one of two. The code itself was spoken. I personally feel that helpful to realize that individuals using screen readers have the capacity to understand context. If they know what they are reading, then they can choose the best method for their screenreader to articulate the information for their individual needs. Does that make sense? creating a guide based on the performance of one screen reader is not helpful for individuals using any of the more than 20 more I can think of off the top of my head smiles. Just my stance, Kare On Tue, 17 Dec 2019, caroline wrote: > I was wondering if there is some sort of documentation out there that helps > writers and developers know what the screenreaders will say when certain > code is used. For example when <li> is used JAWS automatically tells the > user, 1 of 2... > > I'm trying to work out how to set copy writers up for success and avoid > duplicating descriptions that may already be programmed to be said. Maybe > I'm using the wrong key words? I also thought about starting one if it > doesn't exist, is there something nuts about this thought that I'm > overlooking? > > Thanks for any input! >
Received on Wednesday, 18 December 2019 05:01:33 UTC