accessibility

问题 I have an app that contains a view with a cell that uses the built-in cell.textLabel and a custom UITextField in cell.contentView. I am working with Voiceover and accessibility and the desired behavior would be that whenever I tap anywhere in the cell, the accessibility element for the UITextField would be selected. The behavior that I am actually seeing is that the cell.textLabel accessibility labels are taking over. When I don't have cell.textLabel set to anything, everything works as

问题 I have an HTML table like this one: table { border-collapse: collapse; } table thead th:nth-child(1) { width: 180px } table thead th:nth-child(2) { width: 150px } table thead th:nth-child(3) { width: 170px } table thead tr { border-bottom:2px solid #222; } table tbody tr { border-top:1px solid #ddd; } table tbody tr:hover { background: #def; } table tbody td { height: 40px; } <div> <table> <thead> <tr> <th>Heading 1</th> <th>Heading 2</th> <th>Heading 3</th> </tr> </thead> <tbody> <tr> <td

问题 UITableViewCells scrolling speed increases dramatically when you do custom drawing, however, Accessibility breaks. How should one add accessibility support to a cell like this? 回答1: Old question, but iOS has built in support for this kind of accessibility. Take a look at the UIAccessibilityContainer informal protocol which will allow you to define rects in your view and label them appropriately. Thus, if you draw a big X at 0,0 with a size of 44x44, then you can set the accessibilityLabel for

问题 I am trying to make the screen reader (NVDA) to read my currency value (US dollar) $47.49 as "47 Dollars 49 Cents", but the screen reader is reading my currency value as "Dollar 4749". <div class="perVendorCarDetails"> <span class="carCurrencySymbol">$</span> <span class="carPriceDollar">38</span> <span class="carPriceDot">.</span> <span class="carPriceCents">57</span> </div> 回答1: Your example is spoken by NVDA/Firefox as "dollar thirty-eight dot fifty seven." This is not good. If you just

问题 I have seen several behaviors: No element is focused. The close icon (usually at top right of overlay) is focused. Some other element inside of the overlay is focused. If conforming to ADA / ARIA standards, should any element be in focus? 回答1: The current recommend behavior is to focus the first focusable element in the dialog. However, there has been some debate on that implementation recently as it poses problems for users who use screen magnification software and screen readers. in cases

问题 I have a dialog, that has few textviews. For each textview I have set different content description and text. For eg. <TextView android:id="@+id/tv_3" android:layout_width="wrap_content" android:layout_height="wrap_content" android:contentDescription="TV 3" android:text="Text Number 3" /> When I show the dialog to the user, Talkback reads the text (ie. Text Number 3) of each textview and not the content description (ie. TV 3). However if I hover on any textview, Talkback reads the content

问题 Concerning the macOS Accessibility API, is there anyway to create an AXUIElementRef that corresponds to either an NSView or an NSWindow? There appears to have been a way of doing this back in the days of Carbon using AXUIElementCreateWithHIObjectAndIdentifier but that function isn't available anymore. The only method I'm aware of is to use the Accessibility API to recursively search the entire hierarchy of UI elements of your application looking for one that matches the NSView or NSWindow.

问题 I am doing accessibility testing. I created an email text box and added some validation as well. I want after typing wrong email as I move to next element screen reader should read the inline errors. I came across using aria-describeby and aria-live attribute but don't know how to use it in this code . <asp:panel defaultbutton="btnEmail" cssclass="row" runat="server"> <biw:labelui associatedcontrolid="TextEmail" text="Email Address" runat="server" /> <biw:textbox id="TextEmail" width="200"

问题 This is happening in several places for multiple class types but I'll stick with a button example for now. So I have a button which I want talkback to announce as "Play". The content description is set to "Play". However, talkback is also announcing the class too, so it reads as "Play Button". I tried a solution I found elsewhere by overloading the onInitializeAccessibilityNodeInfo method private void setupContentDescriptors() { mPlayPauseButton.setAccessibilityDelegate(new View

问题 I have a custom keyboard app and currently am working on a voice over support update, but am having an issue with the delete (backspace) button. My keyboard is now working exactly like the apple default keyboard with Voice Over in "Touch Typing" mode. When the user taps on w, a, s then space, VoiceOver will say "was" after the space button is tapped. Myb only issue is with the delete key, when the user taps on it, VoiceOver says "Bottom of documnet" rather than the deleted character. I have