Add a new option - noTabInterference. #856
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Setting this option prevents tabs from being processed by the control, and are instead used to switch between controls. This makes pages more accessible because it prevents the grid from becoming a keyboard trap.
roblarsen
added a commit
that referenced
this pull request
Dec 3, 2013
Add a new option - noTabInterference.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setting this option prevents tabs from being processed by the control,
and are instead used to switch between controls. This makes pages more
accessible because it prevents the grid from becoming a keyboard trap.
Keyboard traps are not permitted by WCAG 2.0 guideline 2.1.1 even at an A level of accessiblity, and so without this change, ng-grid cannot be used in environments that mandate compliance with WCAG.