Web Building at UMW
  • Returning Users:
  • Sites@UMW Sign-In
  • |
  • Domain of One’s Own Sign-In
  • |
  • Get Support
  • Menu Menu

Website Building at UMW

Getting Started

  • Domain of One’s Own Overview
  • Before You Sign Up
  • Best Practices for Choosing a Domain Name
  • Getting to Know Your Web Space
  • I Set Up My Account, Now What?
  • Introduction to cPanel
  • Accounts & Passwords

Control Panel

  • Introduction to cPanel
  • Creating a Subdomain
  • Subdomains vs Subdirectories
  • Cleaning up Storage Space
  • Adding a Redirect
  • Adding a New Domain Name

Web Applications

  • Sitejet Builder: Getting Started
  • What is a Web Application?
  • Installing Applications with Installatron

Wordpress

  • Introduction to WordPress Overview
  • Installing WordPress
  • WordPress Editor
  • WordPress Settings
  • Posts and Pages
  • Categories, Tags, and Menus
  • Themes and Customizing Your Site
  • Classic vs Block Themes
  • Basic Privacy
  • Changing Your Display Name
  • Themes and Plugins – Recommendations
  • Uninstalling WordPress
  • Best Practices for Handling Media
  • Cloning a WordPress Installation
  • Creating Footnotes in WordPress
  • Adding a New User to a WordPress Site
  • Resetting your WordPress Password
  • Migrating Sites@UMW to DoOO
  • Feeds (RSS)

Additional Resources

  • Achieving Digital Accessibility on Domain of One’s Own and Sites@UMW 
  • Technical Details: What is the server set-up like?
  • Sites@UMW or Domain of One’s Own?
  • Troubleshooting
  • Accessible Web Design

Web Security

  • Accounts & Passwords
  • Securing Your Site with SSL

Leaving UMW Domains

  • Leaving Domain of One’s Own: Overview
  • Leaving Domain of One’s Own: The Practical Steps

Omeka

  • Omeka Guide
  • Troubleshooting Omeka
View Categories

Achieving Digital Accessibility on Domain of One’s Own and Sites@UMW 

If your website is used to share information related to UMW’s services, programs, teaching, or public activities, it must comply with the Web Content Accessibility Guidelines (WCAG) 2.1 AA by April 24, 2026. This page provides a framework to help you reach compliance. 

Step 1: Clear Out What You Don’t Need  #

Go through your site and remove pages and files that are outdated or no longer accurate. 

Why this helps: Fewer pages mean less work. By removing unused content, you cut down the number of items that need to be checked and fixed. 

Domain of One’s Own  #

  • If an entire site isn’t needed, you can uninstall it from your Domain of One’s Own dashboard. 
  • To fully close your Domain of One’s Own account, reach out to us. 

Sites@UMW  #

  • If an entire site isn’t needed, you can delete the site or you can contact us if you need assistance with this step.

Step 2: Decide What’s Important  #

Make a list of: 

  • Sites you still use for teaching, research, or department activities. 
    • On identified sites make a list of pages and files still needed. 
  • Content you regularly share with students, colleagues, or the public. 

Start with your highest-use content like syllabi, program information, or student-facing resources. Making those pages accessible first has the biggest impact. 

Step 3: Check for Accessibility Problems  #

Use an accessibility tool to scan your site for common issues. These might include: 

  • Missing alt text for images. 
  • Text and background colors that don’t have enough contrast. 
  • Headings that are out of order or skipped. 

If you are new to digital accessibility concepts we recommend reading our Accessible Web Design guide, which explains the basics and shows how they apply in WordPress. 

Domain of One’s Own  #

Tools and resources we recommend: 

  • Accessibility Checkers : We have a list of WordPress accessibility plugins as well as external website checkers that can help you identify issues in need of remediation on your site. 
  • Documents (Word, PowerPoint, PDFs): Use Microsoft Office’s built-in accessibility checkers.  
  • “Accessibility Ready” themes in WordPress. WordPress makes it possible to find themes they deem “accessibility ready”. These themes do not necessarily meet WCAG standards but have healthy defaults.

Sites@UMW  #

  • Accessibility Checkers: By default sites on Sites@UMW should have Editoria11y accessibility checker activated.  
  • Documents (Word, PowerPoint, PDFs): Use Microsoft Office’s built-in accessibility checkers. 

Step 4: Get Support  #

We’re here to support you in using Domain of One’s Own and Sites@UMW. Support options include: 

  • Web accessibility consultations to help you review and remediate your site. 
  • Accessibility question support by submitting questions to the Title II Accessibility e-mail, t2access@umw.edu. 
  • Accessible Web Design guide for guidance on how to remediate your website to meet compliance.

Created by Shannon Hauser 10/14/25

Powered by BetterDocs

Table of Contents
  • Step 1: Clear Out What You Don’t Need 
    • Domain of One’s Own 
    • Sites@UMW 
  • Step 2: Decide What’s Important 
  • Step 3: Check for Accessibility Problems 
    • Domain of One’s Own 
    • Sites@UMW 
  • Step 4: Get Support 
University of Mary Washington logo

Web Building at UMW

About

Terms of Service

Sitejet Builder: Getting Started Introduction to WordPress Overview
Scroll to top