2017-02-28 02:28:23 +00:00
|
|
|
/**
|
|
|
|
* Copyright (c) 2015-present, Facebook, Inc.
|
|
|
|
*
|
2018-02-17 02:24:55 +00:00
|
|
|
* This source code is licensed under the MIT license found in the
|
|
|
|
* LICENSE file in the root directory of this source tree.
|
2017-02-28 02:28:23 +00:00
|
|
|
*
|
|
|
|
* @providesModule AccessibilityInfo
|
|
|
|
* @flow
|
|
|
|
*/
|
|
|
|
'use strict';
|
|
|
|
|
|
|
|
var NativeModules = require('NativeModules');
|
|
|
|
var Promise = require('Promise');
|
|
|
|
var RCTDeviceEventEmitter = require('RCTDeviceEventEmitter');
|
|
|
|
|
|
|
|
var AccessibilityManager = NativeModules.AccessibilityManager;
|
|
|
|
|
|
|
|
var VOICE_OVER_EVENT = 'voiceOverDidChange';
|
2017-05-30 11:35:52 +00:00
|
|
|
var ANNOUNCEMENT_DID_FINISH_EVENT = 'announcementDidFinish';
|
2017-02-28 02:28:23 +00:00
|
|
|
|
|
|
|
type ChangeEventName = $Enum<{
|
|
|
|
change: string,
|
2017-05-30 11:35:52 +00:00
|
|
|
announcementFinished: string
|
2017-02-28 02:28:23 +00:00
|
|
|
}>;
|
|
|
|
|
|
|
|
var _subscriptions = new Map();
|
|
|
|
|
|
|
|
/**
|
Migrate to new documentation format
Summary:
Now that the Component and API docs are no longer auto-generated, we need to consolidate on a new format for our jsdoc comments. Any help from the community will be appreciated.
In this initial pull request, we'll be tackling the following docs:
- `AccessibilityInfo`, an API doc.
- `ActivityIndicator`, a Component doc.
- `View`, a Component doc.
This top comment will serve as a style guide, and when in doubt, please refer to the individual commits in this PR.
Each commit should update a single component or API, along with any relevant markdown files.
- Documentation in the JavaScript source files should be succinct. Any verbosity should be moved over to the markdown docs in the website...
- ...by adding a link to the relevant method/prop on the website to every comment block.
- Avoid markdown style links in JavaScript source files, opt for plain old URIs.
Let code document itself:
- If a method is Flow typed, the comment block does not need to repeat this information.
- If a param can be one of several values, and the type definition is easily determined from the code, the values should not be repeated in the comment block. Again, move this to the markdown doc if not present already.
Closes https://github.com/facebook/react-native/pull/16790
Differential Revision: D6353840
Pulled By: hramos
fbshipit-source-id: 9712c459acc33092aae9909f3dd0b58a00b26afc
2017-11-17 00:44:29 +00:00
|
|
|
* Sometimes it's useful to know whether or not the device has a screen reader
|
|
|
|
* that is currently active. The `AccessibilityInfo` API is designed for this
|
|
|
|
* purpose. You can use it to query the current state of the screen reader as
|
|
|
|
* well as to register to be notified when the state of the screen reader
|
|
|
|
* changes.
|
2017-02-28 02:28:23 +00:00
|
|
|
*
|
Migrate to new documentation format
Summary:
Now that the Component and API docs are no longer auto-generated, we need to consolidate on a new format for our jsdoc comments. Any help from the community will be appreciated.
In this initial pull request, we'll be tackling the following docs:
- `AccessibilityInfo`, an API doc.
- `ActivityIndicator`, a Component doc.
- `View`, a Component doc.
This top comment will serve as a style guide, and when in doubt, please refer to the individual commits in this PR.
Each commit should update a single component or API, along with any relevant markdown files.
- Documentation in the JavaScript source files should be succinct. Any verbosity should be moved over to the markdown docs in the website...
- ...by adding a link to the relevant method/prop on the website to every comment block.
- Avoid markdown style links in JavaScript source files, opt for plain old URIs.
Let code document itself:
- If a method is Flow typed, the comment block does not need to repeat this information.
- If a param can be one of several values, and the type definition is easily determined from the code, the values should not be repeated in the comment block. Again, move this to the markdown doc if not present already.
Closes https://github.com/facebook/react-native/pull/16790
Differential Revision: D6353840
Pulled By: hramos
fbshipit-source-id: 9712c459acc33092aae9909f3dd0b58a00b26afc
2017-11-17 00:44:29 +00:00
|
|
|
* See http://facebook.github.io/react-native/docs/accessibilityinfo.html
|
2017-02-28 02:28:23 +00:00
|
|
|
*/
|
|
|
|
var AccessibilityInfo = {
|
|
|
|
|
|
|
|
/**
|
Migrate to new documentation format
Summary:
Now that the Component and API docs are no longer auto-generated, we need to consolidate on a new format for our jsdoc comments. Any help from the community will be appreciated.
In this initial pull request, we'll be tackling the following docs:
- `AccessibilityInfo`, an API doc.
- `ActivityIndicator`, a Component doc.
- `View`, a Component doc.
This top comment will serve as a style guide, and when in doubt, please refer to the individual commits in this PR.
Each commit should update a single component or API, along with any relevant markdown files.
- Documentation in the JavaScript source files should be succinct. Any verbosity should be moved over to the markdown docs in the website...
- ...by adding a link to the relevant method/prop on the website to every comment block.
- Avoid markdown style links in JavaScript source files, opt for plain old URIs.
Let code document itself:
- If a method is Flow typed, the comment block does not need to repeat this information.
- If a param can be one of several values, and the type definition is easily determined from the code, the values should not be repeated in the comment block. Again, move this to the markdown doc if not present already.
Closes https://github.com/facebook/react-native/pull/16790
Differential Revision: D6353840
Pulled By: hramos
fbshipit-source-id: 9712c459acc33092aae9909f3dd0b58a00b26afc
2017-11-17 00:44:29 +00:00
|
|
|
* Query whether a screen reader is currently enabled.
|
|
|
|
*
|
|
|
|
* Returns a promise which resolves to a boolean.
|
|
|
|
* The result is `true` when a screen reader is enabledand `false` otherwise.
|
|
|
|
*
|
|
|
|
* See http://facebook.github.io/react-native/docs/accessibilityinfo.html#fetch
|
2017-02-28 02:28:23 +00:00
|
|
|
*/
|
|
|
|
fetch: function(): Promise {
|
|
|
|
return new Promise((resolve, reject) => {
|
|
|
|
AccessibilityManager.getCurrentVoiceOverState(
|
|
|
|
resolve,
|
|
|
|
reject
|
|
|
|
);
|
|
|
|
});
|
|
|
|
},
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Add an event handler. Supported events:
|
|
|
|
*
|
|
|
|
* - `change`: Fires when the state of the screen reader changes. The argument
|
|
|
|
* to the event handler is a boolean. The boolean is `true` when a screen
|
|
|
|
* reader is enabled and `false` otherwise.
|
2017-05-30 11:35:52 +00:00
|
|
|
* - `announcementFinished`: iOS-only event. Fires when the screen reader has
|
Migrate to new documentation format
Summary:
Now that the Component and API docs are no longer auto-generated, we need to consolidate on a new format for our jsdoc comments. Any help from the community will be appreciated.
In this initial pull request, we'll be tackling the following docs:
- `AccessibilityInfo`, an API doc.
- `ActivityIndicator`, a Component doc.
- `View`, a Component doc.
This top comment will serve as a style guide, and when in doubt, please refer to the individual commits in this PR.
Each commit should update a single component or API, along with any relevant markdown files.
- Documentation in the JavaScript source files should be succinct. Any verbosity should be moved over to the markdown docs in the website...
- ...by adding a link to the relevant method/prop on the website to every comment block.
- Avoid markdown style links in JavaScript source files, opt for plain old URIs.
Let code document itself:
- If a method is Flow typed, the comment block does not need to repeat this information.
- If a param can be one of several values, and the type definition is easily determined from the code, the values should not be repeated in the comment block. Again, move this to the markdown doc if not present already.
Closes https://github.com/facebook/react-native/pull/16790
Differential Revision: D6353840
Pulled By: hramos
fbshipit-source-id: 9712c459acc33092aae9909f3dd0b58a00b26afc
2017-11-17 00:44:29 +00:00
|
|
|
* finished making an announcement. The argument to the event handler is a
|
|
|
|
* dictionary with these keys:
|
2017-05-30 11:35:52 +00:00
|
|
|
* - `announcement`: The string announced by the screen reader.
|
Migrate to new documentation format
Summary:
Now that the Component and API docs are no longer auto-generated, we need to consolidate on a new format for our jsdoc comments. Any help from the community will be appreciated.
In this initial pull request, we'll be tackling the following docs:
- `AccessibilityInfo`, an API doc.
- `ActivityIndicator`, a Component doc.
- `View`, a Component doc.
This top comment will serve as a style guide, and when in doubt, please refer to the individual commits in this PR.
Each commit should update a single component or API, along with any relevant markdown files.
- Documentation in the JavaScript source files should be succinct. Any verbosity should be moved over to the markdown docs in the website...
- ...by adding a link to the relevant method/prop on the website to every comment block.
- Avoid markdown style links in JavaScript source files, opt for plain old URIs.
Let code document itself:
- If a method is Flow typed, the comment block does not need to repeat this information.
- If a param can be one of several values, and the type definition is easily determined from the code, the values should not be repeated in the comment block. Again, move this to the markdown doc if not present already.
Closes https://github.com/facebook/react-native/pull/16790
Differential Revision: D6353840
Pulled By: hramos
fbshipit-source-id: 9712c459acc33092aae9909f3dd0b58a00b26afc
2017-11-17 00:44:29 +00:00
|
|
|
* - `success`: A boolean indicating whether the announcement was
|
|
|
|
* successfully made.
|
|
|
|
*
|
|
|
|
* See http://facebook.github.io/react-native/docs/accessibilityinfo.html#addeventlistener
|
2017-02-28 02:28:23 +00:00
|
|
|
*/
|
|
|
|
addEventListener: function (
|
|
|
|
eventName: ChangeEventName,
|
|
|
|
handler: Function
|
|
|
|
): Object {
|
2017-05-30 11:35:52 +00:00
|
|
|
var listener;
|
|
|
|
|
|
|
|
if (eventName === 'change') {
|
|
|
|
listener = RCTDeviceEventEmitter.addListener(
|
|
|
|
VOICE_OVER_EVENT,
|
|
|
|
handler
|
|
|
|
);
|
|
|
|
} else if (eventName === 'announcementFinished') {
|
|
|
|
listener = RCTDeviceEventEmitter.addListener(
|
|
|
|
ANNOUNCEMENT_DID_FINISH_EVENT,
|
|
|
|
handler
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2017-02-28 02:28:23 +00:00
|
|
|
_subscriptions.set(handler, listener);
|
|
|
|
return {
|
|
|
|
remove: AccessibilityInfo.removeEventListener.bind(null, eventName, handler),
|
|
|
|
};
|
|
|
|
},
|
|
|
|
|
2017-05-26 10:07:49 +00:00
|
|
|
/**
|
Migrate to new documentation format
Summary:
Now that the Component and API docs are no longer auto-generated, we need to consolidate on a new format for our jsdoc comments. Any help from the community will be appreciated.
In this initial pull request, we'll be tackling the following docs:
- `AccessibilityInfo`, an API doc.
- `ActivityIndicator`, a Component doc.
- `View`, a Component doc.
This top comment will serve as a style guide, and when in doubt, please refer to the individual commits in this PR.
Each commit should update a single component or API, along with any relevant markdown files.
- Documentation in the JavaScript source files should be succinct. Any verbosity should be moved over to the markdown docs in the website...
- ...by adding a link to the relevant method/prop on the website to every comment block.
- Avoid markdown style links in JavaScript source files, opt for plain old URIs.
Let code document itself:
- If a method is Flow typed, the comment block does not need to repeat this information.
- If a param can be one of several values, and the type definition is easily determined from the code, the values should not be repeated in the comment block. Again, move this to the markdown doc if not present already.
Closes https://github.com/facebook/react-native/pull/16790
Differential Revision: D6353840
Pulled By: hramos
fbshipit-source-id: 9712c459acc33092aae9909f3dd0b58a00b26afc
2017-11-17 00:44:29 +00:00
|
|
|
* Set accessibility focus to a react component.
|
|
|
|
*
|
|
|
|
* @platform ios
|
|
|
|
*
|
|
|
|
* See http://facebook.github.io/react-native/docs/accessibilityinfo.html#setaccessibilityfocus
|
2017-05-26 10:07:49 +00:00
|
|
|
*/
|
|
|
|
setAccessibilityFocus: function(
|
|
|
|
reactTag: number
|
|
|
|
): void {
|
|
|
|
AccessibilityManager.setAccessibilityFocus(reactTag);
|
|
|
|
},
|
|
|
|
|
2017-05-30 11:35:52 +00:00
|
|
|
/**
|
Migrate to new documentation format
Summary:
Now that the Component and API docs are no longer auto-generated, we need to consolidate on a new format for our jsdoc comments. Any help from the community will be appreciated.
In this initial pull request, we'll be tackling the following docs:
- `AccessibilityInfo`, an API doc.
- `ActivityIndicator`, a Component doc.
- `View`, a Component doc.
This top comment will serve as a style guide, and when in doubt, please refer to the individual commits in this PR.
Each commit should update a single component or API, along with any relevant markdown files.
- Documentation in the JavaScript source files should be succinct. Any verbosity should be moved over to the markdown docs in the website...
- ...by adding a link to the relevant method/prop on the website to every comment block.
- Avoid markdown style links in JavaScript source files, opt for plain old URIs.
Let code document itself:
- If a method is Flow typed, the comment block does not need to repeat this information.
- If a param can be one of several values, and the type definition is easily determined from the code, the values should not be repeated in the comment block. Again, move this to the markdown doc if not present already.
Closes https://github.com/facebook/react-native/pull/16790
Differential Revision: D6353840
Pulled By: hramos
fbshipit-source-id: 9712c459acc33092aae9909f3dd0b58a00b26afc
2017-11-17 00:44:29 +00:00
|
|
|
* Post a string to be announced by the screen reader.
|
|
|
|
*
|
|
|
|
* @platform ios
|
|
|
|
*
|
|
|
|
* See http://facebook.github.io/react-native/docs/accessibilityinfo.html#announceforaccessibility
|
2017-05-30 11:35:52 +00:00
|
|
|
*/
|
|
|
|
announceForAccessibility: function(
|
|
|
|
announcement: string
|
|
|
|
): void {
|
|
|
|
AccessibilityManager.announceForAccessibility(announcement);
|
|
|
|
},
|
|
|
|
|
2017-02-28 02:28:23 +00:00
|
|
|
/**
|
|
|
|
* Remove an event handler.
|
Migrate to new documentation format
Summary:
Now that the Component and API docs are no longer auto-generated, we need to consolidate on a new format for our jsdoc comments. Any help from the community will be appreciated.
In this initial pull request, we'll be tackling the following docs:
- `AccessibilityInfo`, an API doc.
- `ActivityIndicator`, a Component doc.
- `View`, a Component doc.
This top comment will serve as a style guide, and when in doubt, please refer to the individual commits in this PR.
Each commit should update a single component or API, along with any relevant markdown files.
- Documentation in the JavaScript source files should be succinct. Any verbosity should be moved over to the markdown docs in the website...
- ...by adding a link to the relevant method/prop on the website to every comment block.
- Avoid markdown style links in JavaScript source files, opt for plain old URIs.
Let code document itself:
- If a method is Flow typed, the comment block does not need to repeat this information.
- If a param can be one of several values, and the type definition is easily determined from the code, the values should not be repeated in the comment block. Again, move this to the markdown doc if not present already.
Closes https://github.com/facebook/react-native/pull/16790
Differential Revision: D6353840
Pulled By: hramos
fbshipit-source-id: 9712c459acc33092aae9909f3dd0b58a00b26afc
2017-11-17 00:44:29 +00:00
|
|
|
*
|
|
|
|
* See http://facebook.github.io/react-native/docs/accessibilityinfo.html#removeeventlistener
|
2017-02-28 02:28:23 +00:00
|
|
|
*/
|
|
|
|
removeEventListener: function(
|
|
|
|
eventName: ChangeEventName,
|
|
|
|
handler: Function
|
|
|
|
): void {
|
|
|
|
var listener = _subscriptions.get(handler);
|
|
|
|
if (!listener) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
listener.remove();
|
|
|
|
_subscriptions.delete(handler);
|
|
|
|
},
|
|
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
module.exports = AccessibilityInfo;
|