accessibility

问题 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

问题 I have a form with some read only fields depending on the customer role. As a rule, I use read only fields for those inputs. have you had any problems with this approach using and assistive technology? Any other problems or benefits? 回答1: I have been using a screen reader since internet explorer 3.0 and have had no issues with read only fields. My screen reader announces that the field is read only before it reads the value so I know that I am unable to edit the field. 来源： https:/

问题 I'm trying to find a best practise in terms of accessibility on Tables in relation to other components. In an app that's mainly a set of JTables and JTextFields, I tried to make it accessibility with keyboard as well as mouse. My thoughts are on the best way to help the user to navigate around between components using the VK_TAB key. My first goal was to stop JTables "swallow" the VK_TAB key when the user tries to navigate to a neighbor JTextField using a solution from Coderanch. I tried to

问题 There is an accessibility option ("Ignore colors specified on webpages") in IE that removes all of the CSS color/background-colors from a webpage in order to make it easier to view for some users. This can cause issues by removing helpful images that simply cannot be output in the foreground. Does anyone know if there is a way to detect the state of this setting in an end-users browser? Ultimately it could be used to display alternative styles depending on the state of this setting, so if it

问题 Is there some way to extract "alternate text" for a specific image using PDFBox? I have a PDF file which, as described at http://www.w3.org/WAI/GL/2011/WD-WCAG20-TECHS-20110621/pdf.html#PDF1, has had alternate text added to an image. Using PDFBox I can find my way through the object model to the image itself (a PDXObjectImage) through PDFDocument.getDocumentCatalog().getAllPages() [iterator] .getResources.getImages() but I can not see any way to get from the image itself to the alternate text

问题 Is there some way to extract "alternate text" for a specific image using PDFBox? I have a PDF file which, as described at http://www.w3.org/WAI/GL/2011/WD-WCAG20-TECHS-20110621/pdf.html#PDF1, has had alternate text added to an image. Using PDFBox I can find my way through the object model to the image itself (a PDXObjectImage) through PDFDocument.getDocumentCatalog().getAllPages() [iterator] .getResources.getImages() but I can not see any way to get from the image itself to the alternate text

问题 Issue: I have an accessibility issue that I am struggling with. I have an angular web application. A page loading spinner/indicator is shown when content is loading. And when the page content has loaded the spinner is hidden. This "div" is never removed from DOM. Content of the loading div are not read (by NVDAor jaws) when the loading div is shown. <div class='loading' aria-live='polite' aria-label='Do not refresh the page' tabindex="-1">Do not refresh the page</div> I wouldn't like to

问题 Here is my very simple code for creating a UITextView . UITextView *textView = [[UITextView alloc] initWithFrame:self.view.bounds]; textView.editable = NO; textView.text = @"Using iOS 3.0 and later, VoiceOver is available to help users with visual impairments use their iOS-based devices. The UI Accessibility programming interface, introduced in iOS 3.0, helps developers make their applications accessible to VoiceOver users. Briefly, VoiceOver describes an application’s user interface and

问题 Typically, HTML headings are only able to go up to <h6> before it becomes invalid. As far as I can tell, the following is a completely valid way to create a <h7> element in HTML: <h6 aria-level="7">This is a heading level 7 element</h6> I have tested this in NVDA in Chrome, Firefox and Internet Explorer and it works as intended. I don't really have access to any other screen readers though. Can someone with access to lots of screen reader / browser combinations confirm whether the above is

问题 We have a web-based app which uses a side-by-side experience for desktop users where the left side of the screen is a file browser and editor and the right side of the screen is an interactive preview. Users of our app will make constant and iterative changes on the left and and then interact with the preview on the right, switching back and forth many times in quick succession. Is there a "best practice" for allowing quick and easy navigation between these two interactive areas? I know this