Accessibility

DevHub aims to keep developer workflows usable with keyboard, touch, and assistive technology.

Current practices

Controls use accessible names, visible focus, semantic headings, keyboard navigation, and responsive layouts. Color is not intended to be the only state indicator.

Testing

Automated component and Playwright tests cover core navigation and tool flows. Manual desktop, mobile, keyboard, focus, empty, and error-state checks remain part of release validation.

Feedback

Accessibility problems can be reported through the repository issue tracker with the affected route, browser, assistive technology, and reproduction steps.