Before beginning dev work, we strongly recommend working closely with a UX designer to produce a clear, comprehensive component spec.Review the PR template in advance so that you understand contribution requirements in advance, or go ahead and open a draft PR so you can use the PR template as you work.Ensure your proposed changes follow accessibility guidelines & best practices. Before beginning actual development work, ensure your proposed changes do not cause accessibility regressions or introduce new accessibility issues.Before beginning actual development work, carefully review existing components and helpers to be sure that there does not already exist something that meets your needs.Components in the NoRedInk app which are NOT in the component library but which are shared or could be shared across multiple interfaces may be added to the component library over time by any team, ideally with any necessary accessibility improvements, in accordance with the noredink-ui versioning policy.

Note that after 19 February, 2024, there may be new accessibility problems not captured in that project due to the lack of an accessibility team reviewing component changes.) (There is a project of accessibility issues in the disbanded accessibility team's backlog. Existing components that do not conform to WCAG 2.1 AA accessibility guidelines should be updated to be conformant.For new components, UX designers & stakeholders are responsible for making their best faith effort to follow the Accessibility Guidelines for Product Development and outside accessibility resources to include accessibility details in their spec and code.

Similarly, no existing components will be modified such that the component falls out of conformance with these guidelines.

No new components will be added to the component library if they do not conform to WCAG 2.1 AA accessibility guidelines.

No red ink hack