accessibility

问题 When designing and building the UI for an application that uses AJAX, when do you consider graceful degradation (for users who have JavaScript disabled, or are using a screen reader)? At the end, once the AJAX version of the site is completely finished At every stage of development I don't Something else... 回答1: These days, Progressive Enhancement is generally preferred over Graceful Degradation - i.e. the exact opposite approach. 回答2: The method I'm employing so far is to write it so it

问题 I use a webfont to display some icons on a website. This is fantastic because they scale, and i can print them if i want to... But the problem is that blind people see them as normal letters or characters. The following example returns me a nice Icon + text. <span>i</span> Info <span>t</span> Contact etc... A blind person will just read: iInfo, tContact etc... Is it possible somehow to target only braille- & screen-readers with CSS? I found this on the w3 website, but I'm not sure if the work

问题 What benefits are offered by HTML5 over HTML 4.01 or XHTML 1.0 Strict for accessibility? 回答1: Some stuff that comes to mind - there's probably lots more: The most important thing to note about accessibility in HTML 5 is not so much features as a change in philosophy. HTML 5 goes to some trouble to encourage web authors not to put information into places where ordinary users can't see it, such as alt and summary attributes, and instead encourages them to put the information into the normal

问题 What benefits are offered by HTML5 over HTML 4.01 or XHTML 1.0 Strict for accessibility? 回答1: Some stuff that comes to mind - there's probably lots more: The most important thing to note about accessibility in HTML 5 is not so much features as a change in philosophy. HTML 5 goes to some trouble to encourage web authors not to put information into places where ordinary users can't see it, such as alt and summary attributes, and instead encourages them to put the information into the normal

问题 Can we make Print button without JavaScript? to open browser print window. 回答1: HTML has no built-in "print" action for an anchor tag or input button (or anything else), so JavaScript is your way. You could also include instructions for your users on how to print using File->Print or the other various alternatives. 回答2: Althought as @Pablo says there is no print functionality that can be used without javascript, here is something that will make it a little nicer just in case there was a user

问题 So I'm currently trying to check if a user is using a screen reader on our site. The reason I would like to check if they are is because our site provides a training module in which if they are using a screen reader, I would like to show a button that would allow them to download a printable version of the training. Here is what I have tried so far: internal class UnsafeNativeMethods { public const uint SPI_GETSCREENREADER = 0x0046; [DllImport("user32.dll", SetLastError = true)] [return:

问题 I want to add accessibilityLabel for some of my CALayer's. Here is the example: CALayer *testLayer = [CALayer layer]; [self.view.layer addSublayer:testLayer]; testLayer.backgroundColor = [UIColor purpleColor].CGColor; testLayer.isAccessibilityElement = YES; testLayer.accessibilityLabel = @"Some text"; testLayer.frame = CGRectMake(0, 300, 100, 100); This approach doesn't work for me. Is it possible to make accessibility working for CALayers? I don't want to use accessibility container in

问题 If I have a java class which is package-private (declared with "class", not "public class"), there is really no difference if the methods inside are declared public or protected or package-private, right? So which should I use, or when should I use which? I'm a bit confused. 回答1: If I have a java class which is package-private (declared with "class", not "public class"), there is really no difference if the methods inside are declared public or protected or package-private, right? Well maybe

问题 My Android app contains a custom slider control based on the SeekBar , and I want to attach a custom text phrase to my control to explain its use for Accessibility. I have done this successfully using View.setContentDescription(text) , and TalkBack correctly speaks the phrase when I request focus on my slider control from Activity.onCreate . So far, so good. However, when I touch the control, which I believe sets the AccessibilityFocus on my Android API 16 test device, extra words are being

问题 My Android app contains a custom slider control based on the SeekBar , and I want to attach a custom text phrase to my control to explain its use for Accessibility. I have done this successfully using View.setContentDescription(text) , and TalkBack correctly speaks the phrase when I request focus on my slider control from Activity.onCreate . So far, so good. However, when I touch the control, which I believe sets the AccessibilityFocus on my Android API 16 test device, extra words are being