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

VBA: Perform Foundational testing of the FE for Staging Review #16369

Closed
10 tasks done
Tracked by #16268
mmiddaugh opened this issue Dec 11, 2023 · 9 comments
Closed
10 tasks done
Tracked by #16268

VBA: Perform Foundational testing of the FE for Staging Review #16369

mmiddaugh opened this issue Dec 11, 2023 · 9 comments
Assignees
Labels
accessibility Issues related to accessibility CY24-Q2 Calendar year Q2 2024 priority Facilities Facilities products (VAMC, Vet Center, etc) product Regional office CMS managed VBA product owned by the Facilities team sitewide UX VA.gov frontend CMS team practice area

Comments

@mmiddaugh
Copy link
Contributor

mmiddaugh commented Dec 11, 2023

Description or Additional Context

We need to perform a11y testing 5 days before staging review.

  • Foundational accessibility testing is required before staging review. This includes
    • Use of color and color contrast
    • Automated testing with axe by Deque
    • Content zoom and reflow
    • Keyboard navigation
  • Advanced accessibility testing is recommended before staging review.

Reference

Acceptance Criteria

  • A Tugboat VBA is created with facility services, to be used for both Foundational testing, and Staging Review
  • A11y testing is complete, including (at a minimum)
    • Use of color and color contrast
    • Automated testing with axe by Deque
    • Content zoom and reflow
    • Keyboard navigation
  • Results are documented via Accessibility testing artifact template
    • Any known a11y issues that won't complete for Staging Review are noted in Additional Findings field
  • Defects are documented in issues in backlog and flagged for prioritization
  • Platform cc a11y ticket is attached as artifact for Collab cycle
@mmiddaugh mmiddaugh added accessibility Issues related to accessibility Facilities Facilities products (VAMC, Vet Center, etc) VA.gov frontend CMS team practice area labels Dec 11, 2023
@xiongjaneg xiongjaneg self-assigned this Feb 26, 2024
@davidmpickett davidmpickett added Needs refining Issue status Regional office CMS managed VBA product owned by the Facilities team labels Apr 3, 2024
@jilladams jilladams added Blocked Issues that are blocked on factors other than blocking issues. and removed Needs refining Issue status labels Apr 11, 2024
@davidmpickett davidmpickett added the CY24-Q2 Calendar year Q2 2024 priority label Apr 11, 2024
@jilladams jilladams removed the Blocked Issues that are blocked on factors other than blocking issues. label May 17, 2024
@jilladams jilladams added the UX label May 29, 2024
@eselkin
Copy link
Contributor

eselkin commented May 31, 2024

This requires the script be created for the generation of VBA content, correct?

@davidmpickett davidmpickett self-assigned this Jun 3, 2024
@davidmpickett
Copy link
Contributor

@davidmpickett
Copy link
Contributor

Currently blocked by Tugboat issues: https://dsva.slack.com/archives/CT4GZBM8F/p1717517716070159

@davidmpickett
Copy link
Contributor

I will be using my Tugboat Demo environment for this. This morning I rebuilt the tugboat and I ran the script to add the test content and ran a content release. Hopefully these will be stable links for the duration of the next week.

@davidmpickett
Copy link
Contributor

Created the testing artifact from template: department-of-veterans-affairs/va.gov-team#86174

@davidmpickett
Copy link
Contributor

davidmpickett commented Jun 18, 2024

Things to fix:

  • Multiple email addresses breaking template?

Screenshot 2024-06-18 at 12 38 34 PM

Screenshot 2024-06-18 at 12 34 42 PM

@davidmpickett
Copy link
Contributor

@omahane @eselkin
While reviewing this, I found a tiny tech debt defect thing that is probably fine to ignore forever, but just wanted to document it for posterity #18361

If anything, the action to take here might be updating @omahane test content csv to not have nulls for Office Visits to prevent other people from seeing this issue and flagging it.

@davidmpickett
Copy link
Contributor

@mmiddaugh @Agile6MSkinner - I have now created ticket stubs for all the issues I noticed while testing. Some of them weren't accessibility specific, so I added those to the VBA epic, but not the accessibility testing artifact. Let me know if you have any questions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues related to accessibility CY24-Q2 Calendar year Q2 2024 priority Facilities Facilities products (VAMC, Vet Center, etc) product Regional office CMS managed VBA product owned by the Facilities team sitewide UX VA.gov frontend CMS team practice area
Projects
None yet
Development

No branches or pull requests

5 participants