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

VACMS-20320: adds CSS for better browser validation UX #20321

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

omahane
Copy link
Contributor

@omahane omahane commented Jan 22, 2025

Description

Relates to #20320

Testing done

Manually

Screenshots

Events before the CSS change

Screenshot 2025-01-22 at 10 08 30

Events after the CSS change

Screenshot 2025-01-22 at 10 05 53

QA steps

Set up QA Content Publisher

  • Log in as an admin
  • Assign the following Roles to QA Content Publisher
    • Content creator - VAMC
    • Content publisher
  • Assign the following Section to QA Content Publisher
    • VA Boston health care

Fill out Event form incompletely to show new CSS

  • Log in as QA Content Publisher
  • Create a new Event
  • Confirm that no fields are have a red border on page load
  • Fill in no fields and click Save
  • Confirm that the following fields have a red border:
    • Name
    • Date and Time Start
    • Date and Time End
    • Facility location
    • Revision log message
    • Note: this is consistent with the fields that are highlighted by Clientside Validation

Fill out Story form incompletely to show Clientside Validation as unaffected

  • Create a new Event
  • Confirm that no fields are have a red border on page load
  • Fill in no fields and click Save
  • Confirm that fields have a red border and red messaging underneath

Select Team for PR review

  • CMS Team
  • Public websites
  • Facilities
  • User support
  • Accelerated Publishing

@omahane omahane requested review from a team as code owners January 22, 2025 16:14
@va-cms-bot va-cms-bot temporarily deployed to Tugboat January 22, 2025 16:14 Destroyed
Copy link

Checking composer.lock changes...

@omahane omahane requested a review from a team as a code owner January 22, 2025 16:22
@va-cms-bot va-cms-bot temporarily deployed to Tugboat January 22, 2025 16:22 Destroyed
Copy link

Checking composer.lock changes...

@omahane omahane force-pushed the VACMS-20320-browser-validation-css branch from 52d23ba to a43d8d9 Compare January 22, 2025 16:31
@va-cms-bot va-cms-bot temporarily deployed to Tugboat January 22, 2025 16:31 Destroyed
Copy link

Checking composer.lock changes...

@laflannery
Copy link
Contributor

@omahane your screenshot above has the Event fields as proper and aligned, but I'm seeing them not, it's how they are currently in Prod. Should this alignment be updated?
Screenshot 2025-01-22 at 11 51 07 AM

@va-cms-bot
Copy link
Collaborator

Cypress Accessibility Violations

/test-data-aspernatur

ID: button-name
Impact: critical
Tags: cat.name-role-value, wcag2a, wcag412, section508, section508.22.a, TTv5, TT6.a, EN-301-549, EN-9.4.1.2, ACT
Description: Ensure buttons have discernible text
Help: Buttons must have discernible text
Nodes:

  • HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Page introduction' field" data-proofing-help="Add an introduction that helps visitors understand if information on the page is relevant to them."> <span aria-hidden="true">i</span> </button>
    Impact: critical
    Target: .field--name-field-intro-text-limited-html > .field__label > .proofing-element-help[role="tooltip"]
    Summary: Fix any of the following:
    Element does not have inner text that is visible to screen readers
    aria-label attribute does not exist or is empty
    aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
    Element has no title attribute
    Element does not have an implicit (wrapped) <label>
    Element does not have an explicit <label>
    Element's default semantics were not overridden with role="none" or role="presentation"

  • HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Generate a table of contents from major headings' field" data-proofing-help="By checking this box, all h2's below this point on the page will be linked with with anchor links. This helps users navigate content on very long pages. Do not check this box unless there is at least 2 h2's on the page.">
    Impact: critical
    Target: .field--name-field-table-of-contents-boolean > .field__label > .proofing-element-help[role="tooltip"]
    Summary: Fix any of the following:
    Element does not have inner text that is visible to screen readers
    aria-label attribute does not exist or is empty
    aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
    Element has no title attribute
    Element does not have an implicit (wrapped) <label>
    Element does not have an explicit <label>
    Element's default semantics were not overridden with role="none" or role="presentation"

  • HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Main content' field" data-proofing-help="The main body of the page, which appears below the featured content."> <span aria-hidden="true">i</span> </button>
    Impact: critical
    Target: button[data-proofing-help-title="About 'Main content' field"]
    Summary: Fix any of the following:
    Element does not have inner text that is visible to screen readers
    aria-label attribute does not exist or is empty
    aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
    Element has no title attribute
    Element does not have an implicit (wrapped) <label>
    Element does not have an explicit <label>
    Element's default semantics were not overridden with role="none" or role="presentation"

@github-actions github-actions bot added the CMS Team CMS Product team that manages both editor exp and devops label Jan 22, 2025
@omahane omahane merged commit 3e62942 into main Jan 22, 2025
21 checks passed
@omahane omahane deleted the VACMS-20320-browser-validation-css branch January 22, 2025 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMS Team CMS Product team that manages both editor exp and devops
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants