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

Sec508 Compliance Results Review for Remediation - Registrar #2835

Open
4 tasks
Tracked by #2577
PaulKuykendall opened this issue Sep 20, 2024 · 1 comment
Open
4 tasks
Tracked by #2577

Sec508 Compliance Results Review for Remediation - Registrar #2835

PaulKuykendall opened this issue Sep 20, 2024 · 1 comment

Comments

@PaulKuykendall
Copy link

PaulKuykendall commented Sep 20, 2024

Issue description

We have received an initial report of findings for Section 508 compliance from our Trusted Tested in OAST and need to review these findings and create a remediation plan, including creation of all necessary dev tickets.

All report files are located on Google Drive here.
Summary Report
Complete Report (pdf from html)

Remediation Plan (template to be completed)

Acceptance criteria

  • Initial Report has been reviewed by Product, Design and Dev, as necessary.
  • Remediation Plan completed
  • Identify any existing "accessibility" tickets in the backlog that would address these remediation items
  • Dev tickets created, as necessary, to execute on the remediation plan.

Additional context

The 508 team have completed the 508 compliance review of the dotgov Registrar as requested via ticket  ICTR0044555.

Attached is the 508 report outlining the 508 violations identified for dotgov Registrar. Based on the 508 assessment we have determined that remediation is required for this system/site.

NEXT STEPS

Please forward the defects to the development team to develop a plan for remediation. Afterward, please complete the attached CISA 508 Remediation Plan.doc and send it back to me.

Once the issues are addressed by your team, please reply to this email with the updated Remediation Plan (there is no need to enter a new ACMS ticket). I will conduct a re-evaluation of the site to verify the previously identified issues are corrected and ensure no new defects are encountered.

RESOURCES

ANDI Accessibility Testing Tool
To expedite the remediation/retest process, your team’s developers should add ANDI to their browser’s Favorite Bar (no admin rights needed). This will allow them to perform quick 508 unit tests while making changes to fix the identified 508 defects. Unit testing will reduce the back and forth communication between our 508 Testing Team and the development team.
Helpful Links
CISA Section 508 Program (sharepoint.com)
Technology needs of people who have disabilities (dhs.gov)
How to prioritize, monitor, and resolve Section 508 defects to minimize legal risk (dhs.gov)
How to obtain a Section 508 Compliance Determination (CDF) (dhs.gov)
How to address Section 508 in change control (dhs.gov)
How to provide an Alternative Means (dhs.gov)
How to address Section 508 during operations & maintenance (dhs.gov)

Links to other issues

Blocks:

@PaulKuykendall
Copy link
Author

Updated links in description to point back to Google Drive.

@PaulKuykendall PaulKuykendall self-assigned this Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🔖 Planned
Development

No branches or pull requests

3 participants