accessibility

问题 I am a designer trying to design my typography for mobile apps. I have a question regarding how "accessibility" will affect the font sizes. As in Android, you can change the font size scale from tiny to huge. By default it is "Small". As I play around with the font size, it seems to me that some font sizes within an app will change and some will not. How can I tell which font will be affected by accessibility and which will not? Similar to iOS as well, how well accessibility affect the font

问题 I am making my application accessibility compliant. for this providing correct data to the accessibility framework by giving android:contentDescription="your string" in xml. Also I have Seen the Android Developer guide on Making Applications Accessible for an overview of what steps you need to take to ensure your application works correctly with accessibility services. Now problem is testing these all in each and every screen taking more time. my app has 30 screens and each time to go to any

问题 The web site that we're writing needs to be "Accessible". The trouble is, while we understand the general conepts (semantic latout, alt text on images, light on Javascript, etc etc), we don't really have much knowledge of what screen reader products or other accessible browser are actually on the market and/or in general use, nor how to test against them. So the questions are: What products do we need to know about? Would it be sensible (or even useful) to get hold of them to test against?

问题 I'm only adding a click event handler on my <button> . document.getElementsByTagName("button")[0].addEventListener("click", event => { event.preventDefault(); console.log("Click:", event); }); <button>Press <kbd>Enter</kbd> on me</button> (Demo link) Nevertheless, when I tab to the button in Firefox, then press Enter , I see the click event being fired. However, I cannot see this behaviour documented anywhere. Is this standard behaviour, and can I count on it working in all browsers? 回答1:

问题 I'm only adding a click event handler on my <button> . document.getElementsByTagName("button")[0].addEventListener("click", event => { event.preventDefault(); console.log("Click:", event); }); <button>Press <kbd>Enter</kbd> on me</button> (Demo link) Nevertheless, when I tab to the button in Firefox, then press Enter , I see the click event being fired. However, I cannot see this behaviour documented anywhere. Is this standard behaviour, and can I count on it working in all browsers? 回答1:

问题 I am trying to throttle my video capture framerate for my application, as I have found that it is impacting VoiceOver performance. At the moment, it captures frames from the video camera, and then processes the frames using OpenGL routines as quickly as possible. I would like to set a specific framerate in the capture process. I was expecting to be able to do this by using videoMinFrameDuration or minFrameDuration, but this seems to make no difference to performance. Any ideas? NSArray

问题 Is it good practice not to use much javascript/jquery? Should we avoid it as much as possible (for good accessibility)? When is it OK to use JavaScript and when is it not in web design and development? In what scenarios and with what conditions? Update: I'm asking regarding public websites. 回答1: I have to respectfully disagree with the posters that say that you shouldn't use JavaScript, or use it sparingly, or have it degrade gracefully. The reason is that the vast majority of people nowadays

问题 In striving for WCAG 2.0 Compliance, I'm finding quite a bit of varied information regarding proper treatment of buttons, specifically what is required to consider the button accessible and compliant. What is the appropriate way to mark-up a <button> ? What attributes or combination do they need to have? My buttons fall into three categories: Buttons that have text that describes their intended action. (e.g. "Learn More" to launch a modal with more product information) Buttons that have text

问题 I am converting HTML to a PDF using iText 7. I need the PDF to be accessible (508 compliant with appropriate tags, etc), but, no matter what markup I put on a table, accessibility checkers give the same error: "Table header cell has no associated subcells". I've tried setting scope, headers, etc... nothing seems to work. Here is an example of one of the tables but all of them have the same issue: <table class="problems" summary="Patient's diagnosed problems and associated ICD codes."> <thead>

问题 This question asked how to know if Android Talkback is active; that worked until Jelly Bean. Starting from Android 4.1, that steps no longer work, because the mentioned cursor is empty. Having this said, I want to ask is if there is a way to do the same checking in Jelly Bean. EDIT I tried to search for TalkBack code and I found it here. For checking if TalkBack is active, I am using the following code: Intent screenReaderIntent = new Intent("android.accessibilityservice.AccessibilityService"