screen-readers

问题 I'm creating a website for a reading service for the blind and visually impaired and I'm using JavaScript (with jQuery) to print some stuff to some of the pages after the page has loaded. Will the screen reader read the content that is printed to the page with jquery after the page has been loaded? From this page - "Generally, [screen readers] access the DOM (Document Object Model), and they use browser APIs (Application Programming Interfaces) to get the information they need." and we know

问题 We have a web-based app which uses a side-by-side experience for desktop users where the left side of the screen is a file browser and editor and the right side of the screen is an interactive preview. Users of our app will make constant and iterative changes on the left and and then interact with the preview on the right, switching back and forth many times in quick succession. Is there a "best practice" for allowing quick and easy navigation between these two interactive areas? I know this

问题 I learned that the <abbr> tag is supposed to be interpreted by screen readers in a way that its title attribute would replace its content when read by a screen reader. However, when I try that, neither MacOS (Firefox and Safari) Voiceover nor NVDA (Windows 10, Edge and Firefox) work that way. Here's the relevant code part: ... bla bla bla <abbr title="nervus">N.</abbr> peronaeus ... (that's a medical expression) IMO this should be read as "... bla bla bla nervus peronaeus ...", but it's read

问题 I learned that the <abbr> tag is supposed to be interpreted by screen readers in a way that its title attribute would replace its content when read by a screen reader. However, when I try that, neither MacOS (Firefox and Safari) Voiceover nor NVDA (Windows 10, Edge and Firefox) work that way. Here's the relevant code part: ... bla bla bla <abbr title="nervus">N.</abbr> peronaeus ... (that's a medical expression) IMO this should be read as "... bla bla bla nervus peronaeus ...", but it's read

来源： https://stackoverflow.com/questions/61118191/how-to-handle-version-numbers-for-screen-readers

问题 Screenreaders will read whatever string is set to the "alt" attribute. The use of this attribute is specifically for image tags. If I have a div like so: <div id=myCoolDiv tabindex="0"> 2 <div> Is there a way to have a screen reader pickup an attribute to read a string the same way an alt tag is used? So for the div listed below, the screen reader will say ie: "shopping cart items 2"? I tried using aria-label but the screenreader won't pick it up: <div id=myCoolDiv tabindex="0" aria-label=

问题 I'm developing an aplication for the visual impaired. As I'm using TTS, i want to disable all TalkBack notifications. I've read a lot of post, but nothing seems to work. Is there any way to do this ? Thanks all!! 来源： https://stackoverflow.com/questions/18177817/how-to-disable-talkback-notifications

问题 Let's say I have a list of articles on a preview page of a blog. I want the whole area of each entry to be clickable. In HTML5 this is a possible solution with valid markup: <a href="details/mypost"> <article> <header> <h1>My Post</h1> </header> <p>This is just the teaser. Read more here …</p> </article> </a> My questions are: Is this semantically a link or an article or somehow both regarding the w3 defintion? How is this content read by search engines and screen readers? Is it just a link

问题 I'm working on making a SWF application accessible for visually impaired people who use JAWS or Windows Eyes. I installed both JAWS and Windows Eyes demo versions. When running my swf (locally) in a browser on a html page, Capabilities.hasAccessibility turns out true, but Accessibility.active turns out false, every time - even when checking it after a couple of seconds. Is it because I am using demo versions or am I just missing out on something like setting a parameter for SWFObject perhaps?

问题 I'm working on making a SWF application accessible for visually impaired people who use JAWS or Windows Eyes. I installed both JAWS and Windows Eyes demo versions. When running my swf (locally) in a browser on a html page, Capabilities.hasAccessibility turns out true, but Accessibility.active turns out false, every time - even when checking it after a couple of seconds. Is it because I am using demo versions or am I just missing out on something like setting a parameter for SWFObject perhaps?