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-19813-Testing existing script for reporting axe violations when testing in … #19815

Conversation

keisterj-oddball
Copy link
Collaborator

@keisterj-oddball keisterj-oddball commented Nov 6, 2024

Description

Closes #19813

Testing done

Screenshots

QA steps

Verify accessibility violations contained in the cypress_accessibility_violations.json file in tugboat are reported as a comment on a pull request.

As user uid with user_role

  1. Do this
    • Validate that
  2. Then
    • Validate that
  3. Then validate Acceptance Criteria from issue
    • a
    • b
    • c

Definition of Done

  • Documentation has been updated, if applicable.
  • Tests have been added if necessary.
  • Automated tests have passed.
  • Code Quality Tests have passed.
  • Acceptance Criteria in related issue are met.
  • Manual Code Review Approved.
  • If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

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

Is this PR blocked by another PR?

  • DO NOT MERGE

Does this PR need review from a Product Owner

  • Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

  • Yes, and it's written in issue ____ and queued for publication.
    • Merge and ping the UX writer so they are ready to publish after deployment
  • Yes, but it hasn't yet been written
    • Don't merge yet -- ping the UX writer to write and queue content
  • No announcement is needed for this code change.
    • Merge & carry on unburdened by announcements

Copy link

github-actions bot commented Nov 6, 2024

Checking composer.lock changes...

Copy link

github-actions bot commented Nov 6, 2024

Checking composer.lock changes...

@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 6, 2024 21:30 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 7, 2024 09:00 Destroyed
Copy link

github-actions bot commented Nov 7, 2024

Checking composer.lock changes...

@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 7, 2024 19:49 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 8, 2024 17:13 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 8, 2024 20:35 Destroyed
Copy link

github-actions bot commented Nov 8, 2024

Checking composer.lock changes...

@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 9, 2024 08:59 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 10, 2024 08:55 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 11, 2024 08:51 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 12, 2024 08:53 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 12, 2024 17:32 Destroyed
Copy link

Checking composer.lock changes...

@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 12, 2024 19:33 Destroyed
Copy link

Checking composer.lock changes...

@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 12, 2024 21:20 Destroyed
Copy link

Checking composer.lock changes...

@keisterj-oddball keisterj-oddball marked this pull request as ready for review November 12, 2024 22:52
@keisterj-oddball keisterj-oddball requested a review from a team as a code owner November 12, 2024 22:52
@keisterj-oddball keisterj-oddball requested a review from a team as a code owner November 12, 2024 22:52
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 13, 2024 08:55 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 14, 2024 08:53 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 15, 2024 08:50 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 15, 2024 15:37 Destroyed
Copy link

Checking composer.lock changes...

Copy link
Contributor

@edmund-dunn edmund-dunn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing work!

@va-cms-bot
Copy link
Collaborator

Cypress Accessibility Violations

/test-data-in

ID: button-name
Impact: critical
Tags: cat.name-role-value, wcag2a, wcag412, section508, section508.22.a, ACT, TTv5, TT6.a
Description: Ensures 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'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'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's default semantics were not overridden with role="none" or role="presentation"

@keisterj-oddball keisterj-oddball merged commit 8b296d8 into main Nov 15, 2024
18 checks passed
@keisterj-oddball keisterj-oddball deleted the VACMS-19813-investigate-existing-script-for-reporting-accessibility-violations branch November 15, 2024 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Comprehensive Test Plan: Investigate Existing Script for Reporting Accessibility Violations
3 participants