accessibility

问题 This is for an "Add to basket" control for which one of my colleagues has designed a nice graphic. Obviously it should generate a post request, which a simple hyperlink isn't going to do. Amazon achieves it using an image input. But what are the pros and cons of <input type="image" src="atb.png" alt="Add to Basket" /> versus <button type="submit"><img src="atb.png" alt="Add to Basket" /></button> (and using CSS to control the appearance)? I guess it boils down to these questions: Do all

问题 I've looked up some documentations and examples under the http://developers.itextpdf.com/examples. I know iText is able to generate tagged pdf from scratch, but is it possible to insert alternative text to images in an existing tagged pdf (without changing anything else)? I need to implement this feature in a program without using GUI applications (such as Adobe Acrobat Pro). Thanks. 回答1: Please take a look at the AddAltTags example. In this example, we take a PDF with images of a fox and a

问题 We use KIF for our functional testing, and it uses the accessibility label of elements to determine where to send events. I'm currently trying to test the behaviour of a UISegmentedControl, but in order to do so I need to set different accessibility labels for the different segments of the control. How do I set the accessibility label for a particular segment? 回答1: I'm just getting started with KIF myself, so I haven't tested this, but it may be worth a try. I'm sure I'll have the same issue

问题 We use KIF for our functional testing, and it uses the accessibility label of elements to determine where to send events. I'm currently trying to test the behaviour of a UISegmentedControl, but in order to do so I need to set different accessibility labels for the different segments of the control. How do I set the accessibility label for a particular segment? 回答1: I'm just getting started with KIF myself, so I haven't tested this, but it may be worth a try. I'm sure I'll have the same issue

问题 Consider the following: <label>Range from <input name='min_value'/> to <input name='max_value' /> </label> Is this semantically correct since the W3C recommendations state that a label is associated with exactly one form control? Clicking into the second input shifts focus immediately to the first input? Can this be prevented? How would one markup a min/max input combination to show that two inputs belong together? 回答1: No, it's not correct (since, as you note, a label is associated with

问题 Consider the following: <label>Range from <input name='min_value'/> to <input name='max_value' /> </label> Is this semantically correct since the W3C recommendations state that a label is associated with exactly one form control? Clicking into the second input shifts focus immediately to the first input? Can this be prevented? How would one markup a min/max input combination to show that two inputs belong together? 回答1: No, it's not correct (since, as you note, a label is associated with

问题 The standard material design select list (dropdown) support accessibility. I can get to the dropdown with a TAB (keyboard), navigate the list items with the arrows (keyboard) and by pressing again on tab it will navigate to other component on the screen. Means, the behavior is: TAB navigate between the components on the screen and arrows navigate between the items in the list. Example: <div class="mdl-textfield mdl-js-textfield mdl-textfield--floating-label getmdl-select getmdl-select__fix

问题 The standard material design select list (dropdown) support accessibility. I can get to the dropdown with a TAB (keyboard), navigate the list items with the arrows (keyboard) and by pressing again on tab it will navigate to other component on the screen. Means, the behavior is: TAB navigate between the components on the screen and arrows navigate between the items in the list. Example: <div class="mdl-textfield mdl-js-textfield mdl-textfield--floating-label getmdl-select getmdl-select__fix

问题 For the event TYPE_VIEW_CLICKED on android.widget.Button the event.getSource() method return null. Ideally, this event should have a source attached. Also from Android API 18 onwards, accessibility events propagated through the sendAccessibilityEvent without a source are not sent. The documentation on which events have sources attached is missing! Is there any other reliable way to get the AccessibilityNodeInfo of the event ? i.e Events which have related views. For Eg TYPE_WINDOW_CONTENT

问题 I am developing app for blind community. I want to give an option for the user to explore the screen by scraping finger through the screen (exploring by touch). I am unable to find any api to build this functionality. I am trying to achieve this in android 2.3.3 (api level 10). I know in Android 4.1 talkback with 'touch by explore' functionality comes by default, but I want to give this feature to the users who are using below android 4.1 devices. Any ideas are appreciated. 回答1: You may want