2016-08-22 23:27:33 +00:00
|
|
|
# Accessibility
|
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
Making accessible applications is important and we're happy to introduce new
|
|
|
|
functionality to [Devtron][devtron] and [Spectron][spectron] that gives
|
|
|
|
developers the opportunity to make their apps better for everyone.
|
2016-08-22 23:27:33 +00:00
|
|
|
|
|
|
|
---
|
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
Accessibility concerns in Electron applications are similar to those of
|
|
|
|
websites because they're both ultimately HTML. With Electron apps, however,
|
|
|
|
you can't use the online resources for accessibility audits because your app
|
|
|
|
doesn't have a URL to point the auditor to.
|
2016-08-22 23:27:33 +00:00
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
These new features bring those auditing tools to your Electron app. You can
|
|
|
|
choose to add audits to your tests with Spectron or use them within DevTools
|
|
|
|
with Devtron. Read on for a summary of the tools.
|
2016-08-22 23:27:33 +00:00
|
|
|
|
2017-08-24 14:22:28 +00:00
|
|
|
## Spectron
|
2016-08-22 23:27:33 +00:00
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
In the testing framework Spectron, you can now audit each window and `<webview>`
|
|
|
|
tag in your application. For example:
|
2016-08-22 23:27:33 +00:00
|
|
|
|
|
|
|
```javascript
|
|
|
|
app.client.auditAccessibility().then(function (audit) {
|
|
|
|
if (audit.failed) {
|
|
|
|
console.error(audit.message)
|
|
|
|
}
|
|
|
|
})
|
|
|
|
```
|
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
You can read more about this feature in [Spectron's documentation][spectron-a11y].
|
2016-08-22 23:27:33 +00:00
|
|
|
|
2017-08-24 14:22:28 +00:00
|
|
|
## Devtron
|
2016-08-22 23:27:33 +00:00
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
In Devtron, there is a new accessibility tab which will allow you to audit a
|
|
|
|
page in your app, sort and filter the results.
|
2016-08-22 23:27:33 +00:00
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
![devtron screenshot][devtron-screenshot]
|
2016-08-22 23:27:33 +00:00
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
Both of these tools are using the [Accessibility Developer Tools][a11y-devtools]
|
|
|
|
library built by Google for Chrome. You can learn more about the accessibility
|
|
|
|
audit rules this library uses on that [repository's wiki][a11y-devtools-wiki].
|
2016-08-22 23:27:33 +00:00
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
If you know of other great accessibility tools for Electron, add them to the
|
|
|
|
accessibility documentation with a pull request.
|
2017-08-22 16:01:33 +00:00
|
|
|
|
2017-08-24 14:22:28 +00:00
|
|
|
## Enabling Accessibility
|
2017-08-22 16:01:33 +00:00
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
Electron applications keep accessibility disabled by default for performance
|
|
|
|
reasons but there are multiple ways to enable it.
|
2017-08-24 14:22:28 +00:00
|
|
|
|
|
|
|
### Inside Application
|
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
By using [`app.setAccessibilitySupportEnabled(enabled)`][setAccessibilitySupportEnabled],
|
|
|
|
you can expose accessibility switch to users in the application preferences.
|
|
|
|
User's system assistive utilities have priority over this setting and will
|
|
|
|
override it.
|
2017-08-24 14:22:28 +00:00
|
|
|
|
|
|
|
### Assistive Technology
|
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
Electron application will enable accessibility automatically when it detects
|
|
|
|
assistive technology (Windows) or VoiceOver (macOS). See Chrome's
|
|
|
|
[accessibility documentation][a11y-docs] for more details.
|
2017-08-24 14:22:28 +00:00
|
|
|
|
2018-02-19 23:36:49 +00:00
|
|
|
On macOS, third-party assistive technology can switch accessibility inside
|
|
|
|
Electron applications by setting the attribute `AXManualAccessibility`
|
|
|
|
programmatically:
|
2017-08-22 16:01:33 +00:00
|
|
|
|
|
|
|
```objc
|
|
|
|
CFStringRef kAXManualAccessibility = CFSTR("AXManualAccessibility");
|
|
|
|
|
|
|
|
+ (void)enableAccessibility:(BOOL)enable inElectronApplication:(NSRunningApplication *)app
|
|
|
|
{
|
|
|
|
AXUIElementRef appRef = AXUIElementCreateApplication(app.processIdentifier);
|
|
|
|
if (appRef == nil)
|
|
|
|
return;
|
2018-01-12 15:24:48 +00:00
|
|
|
|
2017-08-22 16:01:33 +00:00
|
|
|
CFBooleanRef value = enable ? kCFBooleanTrue : kCFBooleanFalse;
|
|
|
|
AXUIElementSetAttributeValue(appRef, kAXManualAccessibility, value);
|
|
|
|
CFRelease(appRef);
|
|
|
|
}
|
|
|
|
```
|
2018-02-19 23:36:49 +00:00
|
|
|
|
|
|
|
[devtron]: https://electronjs.org/devtron
|
|
|
|
[devtron-screenshot]: https://cloud.githubusercontent.com/assets/1305617/17156618/9f9bcd72-533f-11e6-880d-389115f40a2a.png
|
|
|
|
[spectron]: https://electronjs.org/spectron
|
|
|
|
[spectron-a11y]: https://github.com/electron/spectron#accessibility-testing
|
|
|
|
[a11y-docs]: https://www.chromium.org/developers/design-documents/accessibility#TOC-How-Chrome-detects-the-presence-of-Assistive-Technology
|
|
|
|
[a11y-devtools]: https://github.com/GoogleChrome/accessibility-developer-tools
|
|
|
|
[a11y-devtools-wiki]: https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules
|
|
|
|
[setAccessibilitySupportEnabled]: ../api/app.md#appsetaccessibilitysupportenabledenabled-macos-windows
|