accessibility

问题 I am getting a weird crash when running my app with VoiceOver enabled. The app has a sidebar interface (like Facebook). When tapping on one of the UITableViewCell s in the sidebar UITableView , I swap out the view controller (create a new one based on which cell was tapped and deallocate the old one). While VoiceOver is enabled, I sometimes get a crash when I tap the cell. This crash does not occur every time (it is about once every two or three tries) and this is not the only thing that

问题 What is the best tested way to hide any text from sighted user but not from popular screen readers? and without affecting SEO. for example if i adding any hidden text only for screen-reader users then that text should not be crawl by search engine when search engine will crawl that page. 回答1: The jQuery UI CSS framework does this by positioning elements far off-screen, e.g. .ui-helper-hidden-accessible { position: absolute; left: -99999999px; } 回答2: I'm using the system Drupal 7 class which

问题 I've been doing screen reader optimization for the last 2 years without issue, but now I'm developing an application that has audio playback as a core piece of functionality. As I understand, there's no way to defer playback while a screen reader is running and all of my audio streams are talking over each other right now. I've been through the WAI-ARIA specs many times to the point that I doubt the feature I'm looking for is included there. Is there any overall screen reader API accessible

问题 I'm building an HTML webpage that contains the following content: In order to proceed, please enter this code: GJBQTCXU "GJBQTCXU" is a code comprised of a string of letters; however, screen readers attempt to pronounce this as a single word. How can I stop them from attempting to pronounce this nonsensical word and instead get it to read one letter at a time: "G J B Q T C X U". As clarification, I'm building this page so that screen readers automatically do the right thing. I know that users

问题 I'm currently working on the accessibility of our project, and here is UICollectionView that is put into a custom UITableViewCell. This CollectionView has tens of cells that are arranged in multiply rows rather than one row. It raises an issue that when you have voiceOver on and move the focus between the collectionViewCells by swiping left or right, the system thought you are swiping between tableViewCells, since collectionView is in the tableView, and the contentOffSet of the tableView will

问题 I'm currently working on the accessibility of our project, and here is UICollectionView that is put into a custom UITableViewCell. This CollectionView has tens of cells that are arranged in multiply rows rather than one row. It raises an issue that when you have voiceOver on and move the focus between the collectionViewCells by swiping left or right, the system thought you are swiping between tableViewCells, since collectionView is in the tableView, and the contentOffSet of the tableView will

问题 I'm currently working on the accessibility of our project, and here is UICollectionView that is put into a custom UITableViewCell. This CollectionView has tens of cells that are arranged in multiply rows rather than one row. It raises an issue that when you have voiceOver on and move the focus between the collectionViewCells by swiping left or right, the system thought you are swiping between tableViewCells, since collectionView is in the tableView, and the contentOffSet of the tableView will

问题 We have an issue where the Apple VoiceOver screen reader is reading words as acronyms. Here's an example: "NEW & USED" will read as "N-E-W and Used" We have honed in on the issue a bit and are seeing that words which are 3 characters or less and uppercase get read as acronyms. The text is uppercase via CSS text-transform: uppercase; . Has anyone found a way to control VoiceOver to and make it read the words? 回答1: You could markup those words in this way <span aria-label="new & used">NEW &

问题 The App I am working on has a name which is mispronounced by the talkback. I am able to fix this within the app by changing the spelling. But if I change the spelling in the android:label in the manifest, it is misspelled on the app icon on the phone. Does anyone have a way around this? 回答1: There is no way to do this. The fix would be for the LaunchScreen to have the ability to read an alternative label, and place it in the content description for the textView that represents your

问题 I'm trying to make a form accessible. Should I make my inputs have both required and aria-required attributes, or just one? <label for="textbox1">Input</label> <input id="textbox1" type="text" name="Text Box" required> Or like this? <label for="textbox1">Input</label> <input id="textbox1" type="text" name="Text Box" aria-required="true"> Or like this? <label for="textbox1">Input</label> <input id="textbox1" type="text" name="Text Box" aria-required="true" required> The article Accessible