You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -209,10 +210,13 @@ The default CSS for `ngHide`, the inverse method to `ngShow`, makes ngAria redun
209
210
`display: none`. See explanation for {@link guide/accessibility#ngshow ngShow} when overriding the default CSS.
210
211
211
212
<h2><span id="ngclick">ngClick</span> and <span id="ngdblclick">ngDblclick</span></h2>
212
-
If `ng-click` or `ng-dblclick` is encountered, ngAria will add `tabindex` if it isn't there already.
213
-
Even with this, you must currently still add `ng-keypress` to non-interactive elements such as `div`
214
-
or `taco-button` to enable keyboard access. Conversation is currently ongoing about whether ngAria
215
-
should also bind `ng-keypress`.
213
+
If `ng-click` or `ng-dblclick` is encountered, ngAria will add `tabindex="0"` if it isn't there
214
+
already.
215
+
216
+
For `ng-click`, keypress will also be bound to `div` and `li` elements. You can turn this functionality on or off with the `bindKeypress` configuration option.
217
+
218
+
For `ng-dblclick`, you must manually add `ng-keypress` to non-interactive elements such as `div`
219
+
or `taco-button` to enable keyboard access.
216
220
217
221
<h3>Example</h3>
218
222
```html
@@ -223,7 +227,6 @@ Becomes:
223
227
```html
224
228
<div ng-click="toggleMenu()" tabindex="0"></div>
225
229
```
226
-
*Note: ngAria still requires `ng-keypress` to be added manually to non-native controls like divs.*
0 commit comments