Release Notes

This release includes updates to comment code 400/401 tasks, the Verification forms, and accessibility enhancements.


  • [SV-2984] - Update Comment Code 400/401 Tasks to Reflect Allow Tax Return Setting
    • Back in February, StudentForms was updated to have the optional settings to allow the collection of a Signed Federal IRS Form 1040 in the Verification process. This setting has been updated to also allow students to upload a Signed Federal IRS Form 1040 when tax information is requested for Comment Codes 400 and 401. Previously it was forcing the student to provide the Federal IRS Tax Return Transcript in any circumstance; it now correctly generates the document task based on the setting.
  • [SV-2975] - Verification Form Update - Reporting an Unborn Child
    • The age calculation found on the Verification form household section has been updated to display an expected birth date under the Age column if the reported date of birth is a future date at the time of completing the form. This helps schools differentiate whether a child has already been born and is under the age of 1 or is an unborn child. A born child under the age of 1 will continue to have the Age display as 0, while unborn children/siblings will now display the expected date of birth.
  • [SV-2957] - Ensure Keyboard Focus is Indicated Visually
    • An accessibility enhancement to ensuring visual focus is seen on all items a keyboard only users may tab into. This assists keyboard users know where the current execution focus is located to enter correct information, submit forms, and reduce extra time trying to determine where the keyboard input focus is.
  • [SV-2960] - Provide a Descriptive Dialog Title
    • ¬†An accessibility enhancement to ensure titles are provided through an accessible manner so that the purpose of the page's current state (with the modal dialog) is understood and makes it easier for assistive technology such as screen readers to locate.
  • [SV-2959] - Ensure Form Field Constraints and Errors are Associated with Their Corresponding Field
    • An accessibility enhancement to ensure form fields that have specific constraints, such as required state, formatting requirements, or unit requirements are clearly communicated both visually and programmatically, so that they are displayed easier to users with cognitive disabilities so that they know what the minimum fields to complete are. Examples of form field constraints include:
      • Date Masks (i.e. MM/DD/YYYY)
      • Required field indicators
      • Text representing a minimum and maximum range of numbers