* Fix reference definitions should be needed * typo * typo * typo and style * Fix reference definitions should be needed * Fix typo * restore to previous
1.9 KiB
Accessibility
Accessibility concerns in Electron applications are similar to those of websites because they're both ultimately HTML.
Manually enabling accessibility features
Electron applications will automatically enable accessibility features in the presence of assistive technology (e.g. JAWS on Windows or VoiceOver on macOS). See Chrome's accessibility documentation for more details.
You can also manually toggle these features either within your Electron application or by setting flags in third-party native software.
Using Electron's API
By using the app.setAccessibilitySupportEnabled(enabled)
API, you can manually expose Chrome's accessibility tree to users in the application preferences.
Note that the user's system assistive utilities have priority over this setting and
will override it.
Within third-party software
macOS
On macOS, third-party assistive technology can toggle accessibility features inside
Electron applications by setting the AXManualAccessibility
attribute
programmatically:
CFStringRef kAXManualAccessibility = CFSTR("AXManualAccessibility");
+ (void)enableAccessibility:(BOOL)enable inElectronApplication:(NSRunningApplication *)app
{
AXUIElementRef appRef = AXUIElementCreateApplication(app.processIdentifier);
if (appRef == nil)
return;
CFBooleanRef value = enable ? kCFBooleanTrue : kCFBooleanFalse;
AXUIElementSetAttributeValue(appRef, kAXManualAccessibility, value);
CFRelease(appRef);
}