screen-readers

Screen Readers For Testing Website Accessibility

由 白昼怎懂夜的黑 提交于 2019-11-30 06:23:30
问题 My website is designed to meet the accessibility guidelines. I'm HOPING that this means screen readers should work well with them... But I have two questions: Is this a fair assumption to make? Are there any free/cheap screen readers clients I can use to test or online emulators? 回答1: Just because something meets the guideline doesn't mean it's guaranteed to be accessible, all screen readers have there different quirks. I'm a totally blind individual so comments on screen readers are below.

How can I make screen readers respond to showing and hiding content in a dynamic web application?

由 ＊爱你＆永不变心＊ 提交于 2019-11-30 05:28:17
问题 I would like to create an accessible web page which contains a number of components that can be hidden and shown as the user interacts with the page. When a component is shown I expect a screen reader (in this case NVDA) to read the contents of the component. As an example: <html> <body> <div id="comp1" style="display:none;" role="region" tabindex="-1" aria-expanded="false"> <div>This is component 1</div> <button type="button" onclick="ShowComponent(comp2)">Show 2</button> </div> <div id=

Does it matter <strong> in <em> or <em> in <strong>?

由 萝らか妹 提交于 2019-11-29 18:31:04
问题 Does it matter <strong> in <em> <p><strong><em>Some text</em></strong></p> or <em> in <strong> ? <p><em><strong>Some text</strong></em></p> Which is semantically correct and more accessible? Update: How screen reader would behave in both situation? 回答1: Syntactically correct but not semantically correct. <strong> is an "higher order" form, so to speak, of <em> . If you're looking for the effect of <b> and <i> , use CSS. Remember to not choose elements because of how they look but what they

Placeholder VS Label for input in HTML5

由 帅比萌擦擦* 提交于 2019-11-29 18:03:46
问题 I'm Making a form with multiple inputs where I need to give lable of form element inside input itself and I'm using like this An example <form class="TTWForm"> <input type="email" name="email" required="required" placeholder="Email Address"> </form> And above code is Valid in W3C validator for HTML5. Does Label not require in HTML 5? If I'm using HTML5 Placeholder to show label inside input is that ok? Does label still required along with placeholder to make it screen reader compatible? 回答1:

HTML Accessibility, are empty elements allowed?

由 拥有回忆 提交于 2019-11-29 16:24:28
Simple question. I was told that the use of, for example, this <span class="fa-stack fa-lg"> <i class="fa fa-cloud fa-stack-2x"></i> <i class="fa fa-cog fa-stack-1x"></i> </span> (which will result in a cloud with a cog at its center), is forbidden for proper accessible html, because the two <i> tags are empty. But then, how can you do that sort of stuff without resorting to an image ? My goal is to achieve the fewest images possible in a page, its only achievable with font icons. unor Is it valid to have an empty element (like <span></span> )? Yes. Is it accessible to have an empty element?

Which screen reader would be best to test site accessibility and how to configure that? [closed]

由 陌路散爱 提交于 2019-11-29 09:21:31
Which screen reader would be best to test site accessibility and how to configure that screen reader to test website (or default screen-reader setting would be ok) and which browser should be used to test accessibility with screen-readers? Free or commercial it doesn't matter . Which can give best testing then site should be accessible in whole world as much as possible with all other screen readers? my purpose is to make site as much as possible. Jared I will preface this answer by stating I’m a totally blind individual who uses Jaws as there only screen reader. I've played around with NVDA

Is it possible to use javascript to detect if a screen reader is running on a users machine?

由 六眼飞鱼酱① 提交于 2019-11-29 05:28:35
I want to detect whether a screen reader is running on a user's machine to avoid sound clashing with audio tag in html. If so, please provide details on how this could be done. BrendanMcK You should probably not try to do anything special even if you could detect that a screenreader is running. Even if you get it right for one group of screenreader users, you may get it wrong for another group. It's best to concentrate on writing good clean HTML5 in the first place. Note that not all screenreader users use text-to-speech; many use braille output. Additionally, other types of accessibility

Screen Readers For Testing Website Accessibility

由 China☆狼群 提交于 2019-11-28 17:57:24
My website is designed to meet the accessibility guidelines. I'm HOPING that this means screen readers should work well with them... But I have two questions: Is this a fair assumption to make? Are there any free/cheap screen readers clients I can use to test or online emulators? Jared Just because something meets the guideline doesn't mean it's guaranteed to be accessible, all screen readers have there different quirks. I'm a totally blind individual so comments on screen readers are below. Note this is a rather long post so I’ve summarized it at the top. In summary if you want to make sure

HTML Accessibility, are empty elements allowed?

由 拜拜、爱过 提交于 2019-11-28 10:24:07
问题 Simple question. I was told that the use of, for example, this <span class="fa-stack fa-lg"> <i class="fa fa-cloud fa-stack-2x"></i> <i class="fa fa-cog fa-stack-1x"></i> </span> (which will result in a cloud with a cog at its center), is forbidden for proper accessible html, because the two <i> tags are empty. But then, how can you do that sort of stuff without resorting to an image ? My goal is to achieve the fewest images possible in a page, its only achievable with font icons. 回答1: Is it

Do multiple h1's cause screen readers problems?

由 风格不统一 提交于 2019-11-28 08:52:22
问题 When I put a website I am building through a W3C checker it asks me to consider only using h1's as a top level heading and points out a section where I have a h1 inside of a section. It also mentions that screen readers will treat them all as top level elements, however, according to HTML5 specs, sections effectively "reset" the headings so you can start another hierarchy from 1-6 within them. Should I only be using h2-h6 within sections if we are trying to focus on W3C validation and
订阅 screen-readers