accessibility

问题 I want to be able to perform lens magnificaiton on top of the windows taskbar. So far I've been unsuccessful in implementing this seeing as the taskbar will always open on top of my window. Windows built-in magnifier is able to do this so I'm hoping it is indeed possible. I've attached two screenshots showing Windows built-in magnifier and how it is able to magnify the taskbar and how my application will render below the taskbar. Windows built-in Magnifier: My application: Is there any way to

问题 The way to provide an accessible name for an <img> element is via its alt attribute. Similarly, the way to provide an acessible name for an <svg> element is via its <title> element. If I have an img tag within an a tag, the accessible name of the link is the accessible name of the img . However, if I have an svg within an a tag, the link has has no accessible name even if the svg does. Why is this? This is apparent within both Lighthouse audits and also the Accessibility tab of Firefox dev

问题 Accessibility issue after upgrading to ag grid version 23 When I check through site improve acceesibility check, I get below error: I'm getting an error for form control label missing. Add the text withing form element within the label tag or WAI-ARIA 'aria-label' or 'aria-labelledby' that is already present. I didnt get a solution anywhere even in community. Kindly let me know if it is possible to add label text in ag-grid version 23 screenshot of console showing the empty label error

问题 I am working with objective-c/swift and interface builder trying to make my application navigation accessible. I cannot figure out how to get my header to work when you use the accessibility rotor and select "headings." My heading title is set in Interface Builder (IB). Within IB its set in a Navigation Bar > UINavigationItem > Title attribute. I think what I want to do is find a way to add the UIAccessibilityTraitHeader to the UINavigationItem , but you cant do that in IB. I also tried

问题 Currently I am using dropzone.js like such: <cfform name='UploadFiles' action="uploadfiles.cfm" class="dropzone"> I am not able to access this control via 'Tab' and 'Enter, which is an accessibility issue. How can I make this keyboard accessible? 回答1: I achieved keyboard accessibility by adding a <button> element in the Dropzone message. See the snippet: Dropzone.autoDiscover = false; // Putting a <button> element in the dropzone message which can be targeted by the keyboard. // Note:

问题 This should be pretty simple but for some reason it isn't working, I'm getting the proper console.logs at the right time, but the focus isn't going to the correct place, please refer to my jsfiddle https://jsfiddle.net/bqt0np9d/ function checkTabPress(e) { "use strict"; // pick passed event of global event object e = e || event; if (e.keyCode === 9) { if (e.shiftKey) { console.log('back tab pressed'); firstItem.onblur=function(){ console.log('last a focus left'); lastItem.focus(); }; e

问题 This should be pretty simple but for some reason it isn't working, I'm getting the proper console.logs at the right time, but the focus isn't going to the correct place, please refer to my jsfiddle https://jsfiddle.net/bqt0np9d/ function checkTabPress(e) { "use strict"; // pick passed event of global event object e = e || event; if (e.keyCode === 9) { if (e.shiftKey) { console.log('back tab pressed'); firstItem.onblur=function(){ console.log('last a focus left'); lastItem.focus(); }; e

问题 I have an activity that has a fragment. That fragment gets the accessibility focus correctly. But when a replace the first fragment with another one, the second one is not getting the focuse automatically, I have to touch the fragment to get the focus. This is the way a do the replace: val fragmentTransaction = supportFragmentManager.beginTransaction() fragmentTransaction.replace(R.id.container, myFragment) fragmentTransaction.commit() container.sendAccessibilityEvent(AccessibilityEvent.TYPE

问题 I'm encountering a strange issue with VoiceOver. Goals: Set a UIStackView containing multiple UILabel 's as my navigationItem.titleView . Mark the stack view as an accessibility element and set its accessibilityLabel to an appropriate value. Set the stack view as the initial VoiceOver focus by calling UIAccessibility.post(notification: .screenChanged, argument: navigationItem.titleView) inside viewDidAppear(animated:) . Expected Result: When the view controller appears the focus appears to be

问题 Many (most?) sites aiming for accessibility and standards compliance use unordered lists for their navigation. Does this make the site more accessible or does it just provide useful elements for styling? I don't mind them, and I have been using unordered lists in this way. It's just that, when I remove the styling from a page to try to gauge it's accessibility, it strikes me that it could just as well could be plain links. Where does this come from? 回答1: The best markup for your site's