Community and contribution – Contribution criteria

You have evidence that the component or pattern would be useful for many NHS digital teams or services.

Evidence could be screenshots or links to versions in different services.

We do not already have something similar in the service manual.

If you're proposing that it replace an existing component or pattern, it should be better than the existing version.

You have tested it in user research and shown that it works with a representative sample of users, including people with disabilities.

If there is not enough research yet to show that it's usable, it can still be published as "experimental". But it must be clearly based on relevant user research from other organisations and best practice, and meet the other criteria.

It uses existing design system styles and components where relevant.

The guidance and any content in examples follow the content guide.

If there is code, it follows the NHS.UK frontend coding standards in GitHub and is ready to merge into the NHS.UK frontend library.

The component or pattern is versatile enough to be used in a range of different services.

For example, a versatile date input component could be set up to ask for:

• a year only
• a month and year only
• a precise date
• any other combination

The component or pattern has been tested and works with a range of browsers, assistive technologies and devices.

Where appropriate, you have involved a clinician in the design of the component or pattern and have addressed any clinical safety issues they raised.

To manage clinical safety risks, the service manual team may ask you to get approval from a clinician trained in clinical safety or we may ask for advice from another clinician before approving a component or pattern.