How to ensure accessible University websites & applications

    Ensuring accessible University websites

    EID-protected websites:

    • Site owners should run currently available accessibility tools (e.g., FireEyes, Wave, NVDA) during website development to check for U.S. Section 508 compliance.
    • Site owners should contact the ITS Accessibility Administrator by sending a request to accessibility-assessments@utlists.utexas.edu to initiate one-time website scanning runs using the WorldSpace tool.
    • Site owners will be required to make temporary arrangements to disable the current site authentication to allow a WorldSpace scan to execute.

    Public websites:

    • Site owners should run currently available accessibility tools (e.g., FireEyes, Wave, NVDA) during website development to check for U.S Section 508 compliance.
    • Site owners should contact the ITS Accessibility Administrator by sending a request to accessibility-assessments@utlists.utexas.edu to complete the set up to have the new site scanned on a monthly basis in WorldSpace.
    • Once sites have been set up by the ITS Accessibility Administrator; the sites are scanned every month and, upon scan completion, site owners will receive an email with a link to the scan results and a web site score (0 to 100) with a goal of 90%.
    • Site owners should study the scan results and contact the ITS Accessibility Administrator with questions to address noncompliance issues. Additional scans may be requested to improve compliance adherence and increase the web site score.
    • WorldSpace scan results are sent to the EIR Accessibility Coordinator every other month for disbursement to deans and vice presidents.

    Ensuring accessible University applications

    Externally Acquired or Purchased Applications

    1. The EIR Accessibility Coordinator will request a VPAT (Voluntary Product Accessibility Template) review by ITS Accessibility Administrator.
      • The VPAT is completed and provided by the application vendor.
    2. The EIR Accessibility Coordinator then uses a set of guidelines and criteria (product audience, scope of use, cost of software, etc…) to determine if accessibility testing on the application is needed.
      • This testing and evaluation will be done by the ITS Accessibility Administrator.

    University-developed Applications

    • Software developers should run the currently available accessibility tools (e.g., FireEyes, Wave, NVDA) during application development to check for U.S. Section 508 compliance.
    • Guidance and review from the ITS Accessibility Administrator is available by sending a request to accessibility-assessments@utlists.utexas.edu.