The recommended way of doing this is to query the AccessibilityManager for the enabled state of accessibility services. AccessibilityManager am = (AccessibilityManager) getSystemService(ACCESSIBILITY_SERVICE); boolean isAccessibilityEnabled = am.isEnabled(); boolean isExploreByTouchEnabled = am.isTouchExplorationEnabled();
I use a js-framework (spine.js in my case) in my latest site. Still I make sure that non-js browsers (certainly not over zealous: think SEO) can navigate my site and digest the contents. As an example I’m going with a search-page with products being shown. Products can be paged, filtered, sorted. Of course this is … Read more
You can use the accessibility APIs for that. Make sure that the “Enable access for assistive devices” setting is checked (in System Preferences / Universal Access). The following code snippet will determine the bounds (in screen coordinates) of the selected text in most applications. Unfortunately, it doesn’t work in Mail and Safari, because they use … Read more
Ok, somebody explained this to me. It’s a Mac problem. Mozilla is being true to operating system settings in Mac OS. There are two distinct ways around this on the user side. Both seem to work: In System Preferences → Keyboard, in the Shortcuts pane, check the “all controls” radio at the bottom. In Firefox, … Read more
As far as I know it is not possible to actually suppress showing the title tag. There are some workarounds however. Assuming you mean you want to preserve the title property on your links and elements, you could use Javascript to remove the title property at onmouseover() and set it again at onmouseout(). // Suppress … Read more
The WAI-ARIA specification defines several ways by which screen readers can “watch” a DOM element. The best supported method is the aria-live attribute. It has modes off, polite,assertive and rude. The higher the level of assertiveness, the more likely it is to interrupt what is currently being spoken by the screen reader. The following has … Read more
For your code to be valid you can’t put any tag inside a <ul> other than an <li>. You can however, put any block level element inside the <li>, like so: <ul> <li> <h2>…</h2> <p>…</p> <p>…</p> </li> </ul>
I found a solution worked for me by calling Settings.Secure.putString(getContentResolver(), Settings.Secure.ENABLED_ACCESSIBILITY_SERVICES, “pkgname/classname”); Settings.Secure.putString(getContentResolver(), Settings.Secure.ACCESSIBILITY_ENABLED, “1”); Where the pkgname is your package name and the classname is the class name of your accessibility service. If you need to enable several services or you don’t want to destory the previous settings you might want to use : … Read more
This doesn’t answer your question, but it’s good to know about a new API call that appeared in 10.9 and lets you display the authorization screen or bypass it: NSDictionary *options = @{(id)kAXTrustedCheckOptionPrompt: @YES}; BOOL accessibilityEnabled = AXIsProcessTrustedWithOptions((CFDictionaryRef)options); Passing YES will force the authorization screen to appear, passing NO will silently skip it. The return … Read more
http://www.w3.org/TR/html4/interact/forms.html#h-17.5 Buttons created with the BUTTON element function just like buttons created with the INPUT element, but they offer richer rendering possibilities: the BUTTON element may have content. For example, a BUTTON element that contains an image functions like and may resemble an INPUT element whose type is set to “image”, but the BUTTON element … Read more