eslint-plugin-vuejs-accessibility icon indicating copy to clipboard operation
eslint-plugin-vuejs-accessibility copied to clipboard

An eslint plugin for checking Vue.js files for accessibility

Results 20 eslint-plugin-vuejs-accessibility issues
Sort by recently updated
recently updated
newest added

We sometimes have components that combine form elements and labels: ``` ``` `id` in this case is a property set on the custom component. Unfortunately the plugin ignores `:for` completely...

bug

`eslint-plugin-jsx-a11y`'s `label-has-for` has recently been deprecated and replaced by [`label-has-associated-control`](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/master/docs/rules/label-has-associated-control.md). This plugin should probably follow suit. I find the default behavior of `label-has-for` to be confusing, since using both wrapping...

good first issue

Hello. ✋ I was recently trying out [Svelte tutorial](https://svelte.dev/tutorial/select-bindings) and encountered the following error. > A11y: on:blur must be used instead of on:change, unless absolutely necessary and it causes no...

good first issue

The `form-control-has-label` rule currently looks for `input` and `textinput` elements, however custom input components (in our use case, [bootstrap-vue](https://github.com/bootstrap-vue/bootstrap-vue)'s `b-form-input` component) don't seem to be checked for labels. Is it...

good first issue

The `role-has-required-aria-props` rule incorrectly flags ARIA 1.1 comboboxes because aria-controls is on the text input and not the parent container with the combobox role. In the ARIA 1.1 combobox pattern...

I want to add aria-hidden to the \; or replace \ with \;And replace \ with \ Additional context Our company uses Sonar to monitor code quality,sonar always tells us...

good first issue

When the error show on the rule is the `Avoid ARIA if it can be achieved without`, it's pretty straight forward what needs to be done to fix it, right?...

good first issue

As this breaks the forth rule of aria :D Reference: - https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-hidden_attribute - https://www.w3.org/TR/using-aria/#fourth

good first issue

For "click-events-have-key-events", the element must also be tabbable, right? otherwise there is no point in adding a keyboard event if the element can't be focused, or am I wrong?