cds-snc / cds-snc/platform-forms-client

Include definition of "publishing" in form builder flow

Open
#7,419 1 comment 0 reactions 1 assignee Claimed by @YedidaZalik View on GitHub
:vertical_traffic_light: Moderate content policy
Dominant language
TypeScript
Stars
46
Forks
16
Avg merge
1d 8h
Merged PRs (30d)
85

Description

As a form builder I need to access the definition of publishing within the publishing flow as I may not read or remember it from the policy documents

Form builders need to fully understand that forms become public once published
- [ ] Defining the meaning of "publishing" so it is clear to clients; including clarifying that live forms become public, but don't appear in Google?
- [ ] Determining where the definition of "publishing" should be shared with clients
- [ ] Updating Terms of Use with how data about forms such as form title and publish date (but NOT responses submitted by end-users) could be used by CDS for analysis
- [ ] Updating Publishing page if additional clarity is needed

**Acceptance criteria**
- [ ] *feature* provides equal service in French and English.
- [ ] *feature* works on Chrome, Firefox, Edge, Safari, and Opera.
- [ ] *component* provides and auto-fill response if the field is saved on the end-users browser.
- [ ] *component* provides error messages and validation.
- [ ] *goal* can be completed using a screen reader.
- [ ] *visual elements* observe colour contrast requirements.
- [ ] manual accessibility testing meet WCAG 2.1 AA requirements.
- [ ] risk register is updated to reflect new risks and their treatments. Treatments are implemented or a new card is created.
- [ ] *feature* collects the data intended, stores, and submits it in the correct format via email, API, or other retrieval method

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.