Accessibility
govuk-react renders the same HTML as govuk-frontend, which the GOV.UK Design System team tests with users of assistive technologies. Its behaviour follows govuk-frontend’s, including keyboard support, focus management and announcements, and its tests check it in real browsers.
Using accessible components doesn’t make a service accessible. Your service still needs to meet the accessibility requirements for public sector websites and apps, and the Design System’s guidance on each component and pattern still applies.
Render on the server
Render pages on the server, so they work before JavaScript loads and when it fails. The Service Manual explains why services should use progressive enhancement. See Without JavaScript.
Forms
Make forms submit to the server, so they work without JavaScript, and show errors as the Design System’s validation pattern describes. See Forms.
Client-side routing
If you use a client-side router, move focus to the new page and update its title after each navigation, because the browser doesn’t. See asChild and router links.
Ids
Ids must be unique on the page. When a component renders more than once, pass id={useId()} to its Field, or idPrefix to grouped controls, so the labels, hints and error messages stay linked to the right control.