accessibility

问题 What differences are expected of XHTML5 versus HTML5? I understand that XHTML5 is the XML form of the language and HTML5 is the SGML form of the language, which means obvious minor syntax differences. Will there be any further differences? Will XHTML5 deprecate completely worthless elements that were not deprecated by HTML5? Will XHTML5 be written in schema instead of doctype? Will XHTML5 impose structural validations instead of merely stating what is a child of what? Will XHTML5 offer

问题 I've noticed in all of Bootstrap's examples using button elements, they include role="button" (and type="button" ), such as: <div class="dropdown"> <button id="dLabel" type="button" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Dropdown trigger <span class="caret"></span> </button> <ul class="dropdown-menu" role="menu" aria-labelledby="dLabel"> ... </ul> </div> Won't accessibility software already know that a button element is meant to act as a button? Is

问题 The confirmation dialogues in chrome are not accessible to JAWS screenreader (Version 18.0.2945). I experienced that with a simple onbeforeUnload dialog as well as with a javascript confirm dialog. The text in the dialog will not be read. Did anyone experience similar problems or knows an answer? 回答1: As of today, 18/09/2017, this is a jaws issue. The code works on all other major browsers. There is no solution at present. Just for your information, alert and prompt have the same problem.

问题 I'm working on a website design that needs to meet WCAG 2.0 AA requirements - and I'm not sure how to interpret the contrast ratio requirements: "1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following" (reference: https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#qr-visual-audio-contrast-contrast). Given that most (if not all) operating systems as well as browsers nowadays have contrast enhancement

问题 I have an overlay with accessible elements. When it disappears, I post UIAccessibilityScreenChangedNotification to cause VoiceOver update. VoiceOver then picks first element of the screen. How can I make it focus on a specific element by default after posting UIAccessibilityScreenChangedNotification ? 回答1: When you post the notification you can supply additional information which is either an NSString object that VoiceOver speaks or an accessibility element that VoiceOver moves to.

问题 I have an overlay with accessible elements. When it disappears, I post UIAccessibilityScreenChangedNotification to cause VoiceOver update. VoiceOver then picks first element of the screen. How can I make it focus on a specific element by default after posting UIAccessibilityScreenChangedNotification ? 回答1: When you post the notification you can supply additional information which is either an NSString object that VoiceOver speaks or an accessibility element that VoiceOver moves to.

问题 I simply can't get the answer to this question. The WCAG says it can be done by aria-hidden tag, but I've read it's not working at many screen readers. Can't get how display:none can help to hide some text only for screen readers(=visible to other devices than SR). This is also not clear how would screen reader act for display:none if it not supports css. Is there any technique or best practice or whatever I can use to hide some text only for screen readers? 回答1: aria-hidden should be used to

问题 How to judge what should be <h2> , h3 h4 h5 h6 or <p><strong>Some text</strong></p> If we don't have knowledge about context Only title of the page i can judge easily <h1> How to judge others I always get content from clients in MS word 2007 format and client always use fontsize to make things smaller and bigger. How we can best judge where client want Headings level and where he used bold text only for styling and where He really want to give emphasize on text. <p><strong>Some text here<

问题 I'm having a minor headache with the TalkBack screen reader service when reading phone numbers in a WebView, and I can't seem to find a solution. This is a snippet of some html code that I am reading into the WebView: <li>Call <a href="tel:18007848669">1-800-QUIT-NOW(1-800-784-8669)</a> for phone support</li> The screen reader reads this as "Call one to eight hundred quit now one to eight hundred link". Is there a way to force it/signal to read it differently? I need it to be read in a more

问题 The new Voice Control API is super cool, it's the one where you can speak to your iOS device and perform actions. (Video from Apple) My only gripe is that finding information on it is kinda difficult. I don't see any WWDC videos out there on it, and I can't find any other documentation. It's basically powered by accessibilityLabels. Since each accessibilityElement can really only have one accessibilityLabel it's (from what I can see) limited to that. Is that accurate? Is there a way to