Axe: Keyboard
User guide
- Getting Started
Api
Concepts
Configurations
Configuring webhint
Connectors
Development flow integration
Extensions
Formatters
Hints
- Avoid CSS limits
- Avoid HTTP redirects
- axe accessibility check
- Babel configuration hint set
- Compatibility of CSS, HTML and JavaScript features
- Correct `Content-Type` header
- Correct manifest extension
- Correct viewport
- Detect CSS Reflows
- Disallowed HTTP headers
- External links disown opener
- Has web app manifest
- Highest document mode
- HTTP cache
- Leading '.' in `classList.add` or `classList.remove`
- Manifest has name
- Minify JavaScript
- Modern DOCTYPE
- No `createElement` with SVG
- No `P3P` headers
- No broken links
- No byte-order mark
- No Inline CSS Styles
- No protocol-relative URLs
- No small error pages
- No vulnerable libraries
- Nu HTML test
- Optimal compression
- Optimize images
- Performance budget
- Prefixed CSS first
- scoped-svg-styles
- Specify button type
- SSL server test
- TypeScript configuration hints set
- Unneeded HTTP headers
- Use `Strict-Transport-Security` header
- Use `X-Content-Type-Options` header
- Use Apple touch icon
- Use charset `utf-8`
- Use HTTPS
- Use subresource integrity
- Valid `Set-Cookie` header
- Valid `theme-color`
- Valid manifest
- webpack configuration hints set
Parsers
Server configurations
Troubleshoot
- Api
- Concepts
- Configurations
- Configuring webhint
- Connectors
- Development flow integration
- Extensions
- Formatters
- Hints
- Parsers
- Server configurations
- Troubleshoot
Axe: Keyboard (keyboard
)
axe/keyboard
contains accessibility rules
from the axe keyboard category.
See the “Can the hint be configured?” section of
hint-axe
for examples of enabling, disabling, and changing the
severity of individual rules.
Default rules (WCAG 2.1 Level A and Level AA)
- Page must have means to bypass repeated blocks (bypass)
- Frames with focusable content must not have tabindex=-1 (frame-focusable-content)
- Interactive controls must not be nested (nested-interactive)
- Scrollable region must have keyboard access (scrollable-region-focusable)
Additional rules (off by default)
- accesskey attribute value should be unique (accesskeys)
- Elements in the focus order should have an appropriate role (focus-order-semantics)
- All page content should be contained by landmarks (region)
- The skip-link target should exist and be focusable (skip-link)
- Elements should not have tabindex greater than zero (tabindex)