cityofaustin / cityofaustin/techstack

Post-MVP multipage forms considerations

Open
#3,661 0 comments 0 reactions 0 assignees View on GitHub
Feature: Forms
Dominant language
No language data
Stars
11
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Reviewed:
https://janis-3288-content-padding.netlify.com/en/health-safety/health-records-certificates-2/birth-death-certificates/multi-page-form-test

## Suggestions
Continue button is occasionally cutoff in the iframe, see below:
Screen Shot 2019-12-16 at 12 49 07 PM

Dropdowns don't have any kind of field label, so the user has to open the dropdown to learn what information it's asking for:
Screen Shot 2019-12-16 at 12 49 45 PM

Dropdowns for dates are inconsistent: sometimes they're represented as numbers, sometimes by the month name, but we should be consistent.

The calendar icon could use a label so that it's clear that this is actually a button as opposed to a field label, maybe something like "view calendar"

Also adding to this list: calendar picker styling
![image](https://user-images.githubusercontent.com/5839508/71681213-b4f86500-2d51-11ea-9e16-7a66e874b5cc.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the linked multipage form test and the screenshots in this issue, focusing on the iframe's Continue button, dropdown labels, date representations, calendar-button label, and picker styling. Done means these concerns are addressed consistently across the reviewed multipage forms and the updated interface is checked against the reported examples.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.