deps: add eslint plugin for a11y #9471
barmacAnnotations
30 errors
|
Build (ubuntu-latest):
client/src/app/EmptyTab.js#L124
Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md
|
|
Build (ubuntu-latest):
client/src/app/notifications/Notification.js#L106
onMouseOver must be accompanied by onFocus for accessibility
|
|
Build (ubuntu-latest):
client/src/app/notifications/Notification.js#L107
onMouseOut must be accompanied by onBlur for accessibility
|
|
Build (ubuntu-latest):
client/src/app/panel/Panel.js#L120
`tabIndex` should only be declared on interactive elements
|
|
Build (ubuntu-latest):
client/src/app/panel/tabs/linting/LintingTab.js#L116
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
|
Build (ubuntu-latest):
client/src/app/panel/tabs/linting/LintingTab.js#L116
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
|
Build (ubuntu-latest):
client/src/app/panel/tabs/log/LogTab.js#L137
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
|
Build (ubuntu-latest):
client/src/app/panel/tabs/log/LogTab.js#L165
Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md
|
|
Build (ubuntu-latest):
client/src/app/primitives/TabLinks.js#L128
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
|
Build (ubuntu-latest):
client/src/app/primitives/TabLinks.js#L128
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
|
Build (macos-12):
client/src/app/EmptyTab.js#L124
Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md
|
|
Build (macos-12):
client/src/app/notifications/Notification.js#L106
onMouseOver must be accompanied by onFocus for accessibility
|
|
Build (macos-12):
client/src/app/notifications/Notification.js#L107
onMouseOut must be accompanied by onBlur for accessibility
|
|
Build (macos-12):
client/src/app/panel/Panel.js#L120
`tabIndex` should only be declared on interactive elements
|
|
Build (macos-12):
client/src/app/panel/tabs/linting/LintingTab.js#L116
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
|
Build (macos-12):
client/src/app/panel/tabs/linting/LintingTab.js#L116
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
|
Build (macos-12):
client/src/app/panel/tabs/log/LogTab.js#L137
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
|
Build (macos-12):
client/src/app/panel/tabs/log/LogTab.js#L165
Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md
|
|
Build (macos-12):
client/src/app/primitives/TabLinks.js#L128
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
|
Build (macos-12):
client/src/app/primitives/TabLinks.js#L128
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
|
Build (windows-2022):
client/src/app/EmptyTab.js#L124
Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md
|
|
Build (windows-2022):
client/src/app/notifications/Notification.js#L106
onMouseOver must be accompanied by onFocus for accessibility
|
|
Build (windows-2022):
client/src/app/notifications/Notification.js#L107
onMouseOut must be accompanied by onBlur for accessibility
|
|
Build (windows-2022):
client/src/app/panel/Panel.js#L120
`tabIndex` should only be declared on interactive elements
|
|
Build (windows-2022):
client/src/app/panel/tabs/linting/LintingTab.js#L116
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
|
Build (windows-2022):
client/src/app/panel/tabs/linting/LintingTab.js#L116
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
|
Build (windows-2022):
client/src/app/panel/tabs/log/LogTab.js#L137
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|
|
Build (windows-2022):
client/src/app/panel/tabs/log/LogTab.js#L165
Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md
|
|
Build (windows-2022):
client/src/app/primitives/TabLinks.js#L128
Visible, non-interactive elements with click handlers must have at least one keyboard listener
|
|
Build (windows-2022):
client/src/app/primitives/TabLinks.js#L128
Avoid non-native interactive elements. If using native HTML is not possible, add an appropriate role and support for tabbing, mouse, keyboard, and touch inputs to an interactive content element
|