accessibility

问题 When using VirtualStringTree to add accessibility support it is required to include the unit VirtualTrees.Accessibility in the uses section. This works in Delphi. The equivalent of this in C++ Builder would be to include the #include "VirtualTrees.Accessibility.hpp" . But including the include file doesn't have any effect. I've traced the problem to the VirtualTrees.Accessibility.pas file and it executes a few lines of code to register the default accessibility provider in Delphi while this

问题 Getting or calculating the exact positions of(Td, TD, Tm, cm, T*) content stream in pdf? As a human I am able to calculate(whether it is replacing last Td or adding to last Td or multiplication with fontsize) the positions of tags in pdf content stream by comparing , where the glyphs are located in pdf and content stream position values. But I am unable to calculate perfect positions of glyph's programatically . Please see the screen short. In above image left side box is pdf ui glyphs and

问题 I have an EditText on an activity that requests focus when the activity launches. This is great for users who do not have TalkBack enabled. However, for accessibility (i.e. for users who have TalkBack enabled), I need to set the focus on the titlebar of the screen, instead of the EditText. I have tried several things but have been unsuccessful at setting the focus on the titlebar's textview (I have checked that titleTextView does not return null): Toolbar toolbar = (Toolbar)findViewById(R.id

问题 I have a UISwitch inside tableviewcell. The toggle makes a network request. A UIActivityIndicator replaces the switch until the response completes. So the UX flow is as such: off --> loader --> on Before the label is tapped the accessibility reads as such: label - value - hint ‘streaming - switch button off - double tap to toggle switch’ My code is as such: @IBAction func switchToggled(_ sender: Any) { toggle.isHidden = true activityIndicatorView.startAnimating() UIAccessibility.post

问题 I have a UISwitch inside tableviewcell. The toggle makes a network request. A UIActivityIndicator replaces the switch until the response completes. So the UX flow is as such: off --> loader --> on Before the label is tapped the accessibility reads as such: label - value - hint ‘streaming - switch button off - double tap to toggle switch’ My code is as such: @IBAction func switchToggled(_ sender: Any) { toggle.isHidden = true activityIndicatorView.startAnimating() UIAccessibility.post

问题 I am writing an AccessibilityService for Android and, up to API level 20, I have been using the AccessibilityEvent.getSource() method to obtain a traversable AccessibilityNodeInfo when onAccessibilityEvent(AccessibilityEvent event) is triggered. Although the resulting AccessibilityNodeInfo does not always reflect the content of the screen, it is still possible to work with it. Starting on API level 21, the new AccessibilityService.getWindows() is supposed to be not only able to better

问题 I am writing an AccessibilityService for Android and, up to API level 20, I have been using the AccessibilityEvent.getSource() method to obtain a traversable AccessibilityNodeInfo when onAccessibilityEvent(AccessibilityEvent event) is triggered. Although the resulting AccessibilityNodeInfo does not always reflect the content of the screen, it is still possible to work with it. Starting on API level 21, the new AccessibilityService.getWindows() is supposed to be not only able to better

问题 I have a mat-form-field with a text input control. I have a mat-label and I also put an aria-label attribute attr.aria-label on the input element directly. Is the mat-label sufficient for screen readers by itself? Is the attr.aria-label necessary or redundant? <mat-form-field appearance="outline" floatLabel="always"> <mat-label>Username</mat-label> <input attr.aria-label="Username" formControlName="Username" matInput> </mat-form-field> The same question goes for the mat-select control. <mat

问题 I have a mat-form-field with a text input control. I have a mat-label and I also put an aria-label attribute attr.aria-label on the input element directly. Is the mat-label sufficient for screen readers by itself? Is the attr.aria-label necessary or redundant? <mat-form-field appearance="outline" floatLabel="always"> <mat-label>Username</mat-label> <input attr.aria-label="Username" formControlName="Username" matInput> </mat-form-field> The same question goes for the mat-select control. <mat

问题 I am facing an issue with the NVDA screen reader where it's not reading the links or text while navigating. My CodePen HTML <nav role="navigation"> <ul class="list"> <li class="list-item"> <a class="link" href="#" aria-haspopup="true" aria-expanded="false">Home</a> <div class="sub-nav"> <ul class="sub-nav-list"> <li> <a href="">First list item in home</a> </li> <li> <a href="">Second</a> </li> </ul> </div> </li> <li class="list-item"> <a class="link" href="#" aria-haspopup="true" aria