# Feature OP-13042 - Use Primer forms for better error handling

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-13042

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List | a11y report 2026 |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Accessibility, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | Yes |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

### Acceptance criteria

*   [ ] The rails form builder is adapted to use the Primer forms

  

### Accessibility Goal (from WCAG Guidelines)

**Perceivable**

*   [ ] [1.3.1](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships) Information, structure, and relationships/dependencies conveyed through presentation can be extracted with different user agents, assistive technologies, or have text representations

**Operable**

*   [ ] [2.1.2](https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap) If focus can be moved to a component using keyboard, it cen be moved away using keyboard only
*   [ ] [2.3.1](https://www.w3.org/WAI/WCAG21/Understanding/three-flashes-or-below-threshold)/[2.3.2](https://www.w3.org/WAI/WCAG21/Understanding/three-flashes) Flashes are no more than three times in any one second period
*   [ ] [2.4.3](https://www.w3.org/WAI/WCAG21/Understanding/focus-order) Focusable components receive focus in an order that preserves meaning an operability
*   [ ] [2.4.6](https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels) Headings and labels describe topic or purpose
*   [ ] [2.4.7](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible) Keyboard foucs indication is visible to the user

**Understandable**

*   [ ] [3.2.4](https://www.w3.org/WAI/WCAG21/Understanding/consistent-identification) Components that have the same functionality within a set of Web pages are identified consistently (Icons, check marks, references)
*   [ ] [3.3.1](https://www.w3.org/WAI/WCAG21/Understanding/error-identification) Input errors are described to the user in text
*   [ ] [3.3.3](https://www.w3.org/WAI/WCAG21/Understanding/error-suggestion) Input errors have suggestions with regards how to correct that error
*   [ ] [3.3.4](https://www.w3.org/WAI/WCAG21/Understanding/error-prevention-legal-financial-data)/[3.3.6](https://www.w3.org/WAI/WCAG21/Understanding/error-prevention-all) Errors can be prevented
    *   [ ] Submissions are reversible
    *   [ ] Data entered by the user is checked for errors and user is able to correct them
    *   [ ] A mechanism exists for reviewing, confirming, and correcting information before finalizing them

**References**

[https://www.w3.org/TR/2008/REC-WCAG20-20081211](https://www.w3.org/TR/2008/REC-WCAG20-20081211)

https://www.w3.org/WAI/WCAG21/Understanding/

[https://www.digitala11y.com/wcag-checklist/](https://www.digitala11y.com/wcag-checklist/)
