Skip to main content

Welcome to the Accessibility Evaluation Audit (AEA) Process!

Kaffeinated Kodemonkey POCC Seal

At Kaffeinated Kodemonkey, we uphold the highest standards of accessibility, ensuring that all our products meet ADA Compliance requirements. Our commitment to accessibility is reflected in our rigorous Accessibility Evaluation Audit (AEA) process, where we utilize a range of A11y tools, screen readers, and assistive technologies.

As an A11y Developer, Lead Moneky or Kodemonkey, your role is pivotal in guaranteeing that the product not only meets but exceed accessibility standards. Following the A11y Evaluation Audit Guidelines, you will assess the product using screen readers, mobile devices, assistive technologies, WAVE, and any other specified tools outlined in the project scope.

Before embarking on any project, it's essential to thoroughly review the project scope. This will provide clarity on the required level of compliance, whether it's WCAG/508, WCAG only, AA, or AAA. Additionally, take note of any unique testing methods suggested or required for the project.

Getting started with the AEA process:

Understanding the challenges of manually evaluating every page, especially on large sites, we have streamlined the AEA process. We will provide a list of URLs required for review within the Project Space, along with the following critical areas for assessment:

  • Site templates
  • Interactive forms
  • Dynamic content pages
  • Pages with dialog modals and alert notifications
  • Key entry and exit pages (including account login and recovery pages)
  • Any pages that process payments
  • Help and assistance pages

Instructions

All AEA will be conducted using the DHS Trusted Tester Process outlined below.

Before you get started you will want to:

  • Read Project Scope
  • Create a dir/folder on you computer to save the json file and any other associated documents.
  • Upong completion you will send this dir/folder to your Lead

Remember, the Project Scope serves as a comprehensive guide, outlining any special instructions and providing essential information required to complete the AEA Report successfully.

* The AEA is the evaluation and basis for all AEA documents.

  1. Launch A11y Evaluation Audit to record test results
  2. Selecta previous JSON File or load a new JSON file: First time use Trusted Tester v.5.1.1 (for web) or Trusted Tester v.4 (for software) (TT5.1.1 or TT4)
  3. Select Load File button.
  4. Referande the Project Scope to complete each form and the required fields.
  5. Add/Edit Test Results as needed
  6. Save the file as-is in JSON format
  7. Upon completion submit the JSON file to The A11y Dev Team.

Reference the Project Scope to complete required fields as indicated by a red asterisk. *

Select the ‘Show Testing Information Section’ Show/Hide Button
This expands the section to reveal all fields. The same button is also used to collapse and hide the section.
Input Company Name *
Complete the required form field which has a character limit.
Input Tester’s First Name *
Complete the required form field.
Input Tester’s Last Name *
Complete the required form field.
Input Trusted Tester ID
This form field is optional but users are encouraged to provide a Trusted Testers certification number.
Input Tester’s Email *
Complete the required form field. Users have the option to use a government or a private email address.
Input Testing Scope
This form field is optional but is commonly used as a description or list of what was tested.
Verify Testing Method and Version
When the JSON file is loaded (refer to 2.1), these form fields are auto-populated and are read-only.

This section does not contain any required fields but Trusted Testers are encouraged to complete this section.

Select the ‘Show Test Environment Section’ Show/Hide Button
This expands the section to reveal all fields. The same button is also used to collapse and hide the section.
Select the Browser Compatibility View
Use the dropdown menu to select:
  • None
  • Turned On
  • Turned Off
Choose Browser Type and Version
Select the type of browser used by navigating to the dropdown menu to select the browser type. More than one browser type and version can be selected.
Choose the Operating System and Version
Select the operating system used by navigating to the dropdown menu to select the version used. More than one operating system and version can be selected. If ‘Other Operating System’ is selected, additional form fields for the Name and Version will become available.

This step cannot be completed without first uploading a JSON file

Locate the Test Results Form
Scroll down to find the Enter Test Results form. It is only visible after a valid JSON file is loaded
Enter the Test Results
Each row in the Test Results Form includes:
  • A. Issue Number
  • B. Test Name
  • C. Test ID
  • D. Test Condition
  • E. Test Result - Use the dropdown to select
    • No Selection
    • Pass
    • Fail
    • Does Not Apply
  • F. Browser - If the browser used for this test result is different it can be noted here. When applicable, select the check box to change the browser. Use the dropdown to select the version of the browser used for the test.
  • G. Tester Comments - The form field has a character limit and is used for any comments about the test.
  • H. Location/Screen - The form field has a character limit and is used to provide details needed to locate the defect on the web page.
  • I. Screenshot - After a test result is added, a ‘Choose File’ button will appear to add images to the corresponding test result. To add a screenshot, select the ‘Choose File’ button, select the image file (PNG, JPEG, or GIF), and select Open.
  • J. Global Issue - Use the dropdown to select
    • None
    • Yes
    • No
  • K. Go to Parent/Add Child Issue - The Child Issue is a separate issue added that is associated to the same Test ID, the parent.
Additional Option: Remediation Details.
These columns are only available if ‘Show Remediation Detail’ is checked.
  • Remediation Details
  • Remediation Screenshot
  • Remediation Date
Save The file will be saved to the system’s Downloads folder by default.

Any accessibility issues that are not addressed before production release should be tracked within the test results generated using ACRT to be prioritized in the product backlog. Trusted Testers should coordinate with their IT Project Manager regarding remediation details.

Load JSON file
Select the Checkbox for Show Remediation Detail Columns
Two columns are added to the report next to Global Issues.
Remediation Details
Include the steps taken to remediate the accessibility issues identified. This field has a character limit.
Remediation Screenshot
At this time we are not requiring images to be added.
Remediation Date
This is only requirted if you are making remediations to the site.
Provide the date the accessibility issues were remediated and finalized.
Enter the Remediation Details
If a test fails add suggested remediation resolution for client's dev team to resolve the issue.
If you are making the remediations as you go then mark the criteria as passed and this will not be required.
Save
The file will be saved to the system’s Downloads folder by default.