Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve UX of browser-based validations #20320

Closed
6 of 13 tasks
omahane opened this issue Jan 22, 2025 · 1 comment
Closed
6 of 13 tasks

Improve UX of browser-based validations #20320

omahane opened this issue Jan 22, 2025 · 1 comment
Assignees
Labels
Drupal engineering CMS team practice area Editor experience Pertaining to CMS user experience as Editors Enhancement Issue type: New feature or request Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status Public Websites Scrum team in the Sitewide crew sitewide

Comments

@omahane
Copy link
Contributor

omahane commented Jan 22, 2025

User Story or Problem Statement

As an editor who is filling out content, I want as consistent a user experience as possible when I forget to fill out required fields.

Acceptance Criteria

  • Make the UX more like Clientside Validation by adding red borders to fields that are required
  • Do not adversely affect the Clientside Validation
  • Do not add borders to fields that wouldn't get them with Clientside Validation
    • Note: <select> fields seem to be immune to the CSS or Clientside Validation

Implementation steps

With the implementation of Clientside Validation changes to exempt certain forms, the UX has changed a bit to make it less easy to see which required fields an editor missed before submitting the form. Adding a CSS change could align them better.

Clientside Validation UX

Image

Proposed UX for required fields on forms not using Clientside Validation

Image

Design principles

Veteran-centered

  • Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.
  • Accessible, plain language: Provide guardrails and guidelines to ensure content quality.
  • Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.
  • Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.

Editor-centered

  • Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.
  • Efficient: Remove distractions and create clear, straightforward paths to get the job done.
  • Approachable: Offer friendly guidance over authoritative instruction.
  • Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
  • Empowering: Provide clear information to help editors make decisions about their work.
@omahane omahane added Enhancement Issue type: New feature or request Needs refining Issue status labels Jan 22, 2025
@jilladams jilladams added Drupal engineering CMS team practice area sitewide Editor experience Pertaining to CMS user experience as Editors Facilities Facilities products (VAMC, Vet Center, etc) Public Websites Scrum team in the Sitewide crew labels Jan 22, 2025
@omahane omahane self-assigned this Jan 22, 2025
@jilladams
Copy link
Contributor

On submit with empty required fields, I get the red outline. The tooltip does say "Please fill out this field" at first, and that goes away after you click on the field.

Image'

Closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal engineering CMS team practice area Editor experience Pertaining to CMS user experience as Editors Enhancement Issue type: New feature or request Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status Public Websites Scrum team in the Sitewide crew sitewide
Projects
None yet
Development

No branches or pull requests

2 participants