Giters
FormidableLabs
/
eslint-plugin-react-native-a11y
React Native specific accessibility linting rules.
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
273
Watchers:
49
Issues:
54
Forks:
23
FormidableLabs/eslint-plugin-react-native-a11y Issues
Add support for new web-inspired a11y props
Closed
13 days ago
Comments count
1
role prop not supported unlike accessibilityRole
Closed
13 days ago
Comments count
1
Support for new Pressable component
Updated
a year ago
why is the accessibilityHint enforced as mandatory?
Updated
a year ago
Comments count
3
Adding eslint 8 as compatible peer dependency
Closed
2 years ago
Comments count
1
`react-native-a11y/has-valid-accessibility-state` crashes when destructuring within prop.
Updated
2 years ago
Error message for `-descriptors` rule is out of sync with accessibility-hint rule setting
Updated
2 years ago
Support ESLint 8
Closed
2 years ago
Comments count
1
Getting a warning even when passing AccessibilityState as an object
Closed
3 years ago
Comments count
2
Feature: Rule to require accessibilityRole prop
Closed
3 years ago
Comments count
2
accessibilityIgnoresInvertColors behaves the opposite way this plugin expects it to
Closed
3 years ago
Comments count
1
not get any warning
Closed
3 years ago
Comments count
8
Unable to resolve dependency tree
Closed
3 years ago
Comments count
3
[Feature Request] Extended accessibilityRole values? (RNW)
Closed
3 years ago
has-valid-accessibility-actions rule doesn't accept variables
Closed
3 years ago
Enforce "has-accessibility-props" on `Pressable`
Closed
3 years ago
Comments count
1
has-valid-accessibility-state rule doesn't accept functions calls and object properties
Closed
3 years ago
Inline functions/values are not recognized as valid accessibility actions
Closed
4 years ago
Comments count
1
accessibilityState doesn't recognize boolean value in checked variable
Closed
4 years ago
Comments count
2
accessibilityState doesn't recognise boolean value in variable
Closed
4 years ago
Comments count
3
Prop value validators should allow expressions as possible valid values
Closed
4 years ago
Comments count
2
Error with any custom components aliased as Image
Updated
4 years ago
Comments count
1
Support new accessibility API in RN 0.57
Closed
4 years ago
Comments count
7
Add links to rule definitions in rule error messages
Closed
4 years ago
Comments count
4
Deprecate accessibility-label
Closed
4 years ago
Deprecate accessibilityStates in favour of accessibilityState?
Closed
4 years ago
Comments count
2
Deprecate has-accessibility-props
Closed
4 years ago
Add accessibilityHint for View, Text, Touchable* on iOS
Closed
4 years ago
Comments count
1
Add support for accessibilityIgnoresInvertColors
Closed
4 years ago
Comments count
1
Remove touchable as a required word for custom touchable names
Closed
4 years ago
Add support for accessibilityActions
Closed
4 years ago
Add support for accessibilityValue
Closed
4 years ago
Add a script to automatically add rules to the README
Closed
4 years ago
Deprecate `accessibility-label`
Closed
5 years ago
Support all accessibilityRoles
Closed
5 years ago
Comments count
1
Should support all valid accessibilityStates
Closed
5 years ago
Comments count
1
The accessibilityStates does not allow an empty state.
Closed
5 years ago
Comments count
1
has-valid-accessibility-role lacks several valid accessibility roles
Closed
5 years ago
Add `yarn.lock` to source to make builds deterministic.
Closed
5 years ago
Consider merging into eslint-plugin-jsx-a11y
Closed
5 years ago
Comments count
6
Allow an array for accessibilityTraits
Closed
6 years ago
Comments count
3
Add an option to provide custom names to rules that rely on Touchable* component naming
Closed
6 years ago
Setup CI
Closed
6 years ago
Comments count
2
Allow accessible ={true} without an accessibilityLabel prop if it is implemented by children
Closed
6 years ago
Clear out unnecessary deps/files
Closed
6 years ago
Verify that importantForAccessibility values are valid
Closed
6 years ago
Verify that accessibilityLiveRegion values are valid
Closed
6 years ago
Update docs
Closed
6 years ago
Support react-native-platform-touchable in accessible-touchable
Closed
6 years ago
Comments count
2
Verify that accessibilityComponentType values are valid
Closed
6 years ago
Previous
Next