All Georgetown websites must be AA-compliant upon launch.

Launching a new non-UIS-themed website

This is the process for launching a non-UIS-themed website with a georgetown.edu domain.

  1. Take the accessibility training courses. (optional but recommended)
  2. You can start by checking the accessibility of individual pages using the Siteimprove chrome plugin, or if you'd like to use Siteimprove to do site-wide automated accessibility checks, email webaccessibility@georgetown.edu to ask to get your website added. The website cannot be password protected.
  3. Your website must pass automated testing and manual testing. You can use tools like Siteimprove to perform automated testing, and you can use the manual testing checklist to catch the errors that automated testing misses.
  4. If you're not sure how to test your site for issues, you should contract with Siteimprove or another reputable accessibility tester to perform testing for you and produce a report (note that there will be a cost for this).
  5. If the report is positive (i.e. no A or AA issues found), send webaccessibility@georgetown.edu the report at least 1 week before your intended launch date.
  6. If the report finds issues, you'll need to fix them yourself or hire someone to make the fixes for you. You can provide a justification for why it's impossible to fix certain issues. If the final report includes justifications, send webaccessibility@georgetown.edu the report at least 3 weeks before your intended launch date to give us enough time to review your justifications, and give you enough time to make additional fixes if need be.
  7. Web Services will review your report and do cursory testing. If Web Services finds errors, you'll be required to fix outstanding errors.
  8. When the AA requirement is satisfied, your website can launch.

Getting Started with Accessibility

  1. Take the accessibility training courses
  2. Start with the 5 essential fixes
  3. Use Siteimprove to easily see what issues need to be addressed (sign up for the training to get access to Siteimprove)
  4. Prioritize A-level errors and warnings, then AA-level errors and warnings, then Review items
  5. Install the Siteimprove extension for Chrome to check individual pages right inside your browser window.

Every time you publish a page