This guide outlines recommended practices for creating accessible web content at the University of Washington. It is intended for anyone involved in building or maintaining websites — developers, content creators, project managers, and others. These practical topics align with guidance from the UW ADA Coordinator’s Office, Accessible Technology Services, and the UMAC Web Strategy team. Note, this page will eventually link to a forthcoming accessibility standard and policy.
Sign Up for Deque University
What to do
Enroll in Deque University to begin your accessibility learning journey.
Why it matters
Deque University provides free, high-quality accessibility training for UW staff. It covers essential topics such as screen reader testing, semantic HTML, ARIA roles, and accessible design principles. This foundational knowledge is critical for anyone creating or editing web content.
How to get started
Visit go.uw.edu/deque and follow the instructions to request access.
Start your project using UW’s accessible templates and themes
What to do
Use the accessible templates and themes provided by the UMAC Web Strategy team to begin your web project.
Why it matters
These templates are built with accessibility in mind and align with UW branding standards. Starting with these resources ensures your site has a strong foundation for both usability and compliance.
How to get started
Browse the available templates and themes at go.uw.edu/templates and choose one that fits your project needs.
Follow best practices from Accessible Technology Services (ATS)
What to do
Review the best practices for websites from ATS and incorporate them into your workflow.
Why it matters
ATS provides detailed recommendations on accessible navigation, color contrast, keyboard usability, semantic structure, and more. Following these practices helps ensure your site is usable by everyone, including people with disabilities.
How to get started
Visit go.uw.edu/accessible-websites and explore the sections on design, development, and testing.
Code to WCAG 2.1 AA Standards
What to do
Ensure your code meets the WCAG 2.1 AA accessibility standards.
Why it matters
WCAG 2.1 AA is the benchmark for accessible web content. It includes guidelines for text alternatives, adaptable layouts, distinguishable elements, and more. Meeting these standards is essential for legal compliance and inclusive design.
How to get started
ATS’s pages on creating accessible websites, available at go.uw.edu/accessible-websites, provide practical guidance for implementing WCAG principles.
Sign up for DubBot and check your work often
What to do
Use DubBot to scan your site for accessibility issues.
Why it matters
DubBot is an automated accessibility checker that helps identify issues like missing alt text, improper heading structure, and broken links. Regular scans ensure your site remains accessible as content evolves.
How to get started
Visit go.uw.edu/dubbot to request access and learn how to use the tool effectively.
Use the UW Web Checklist before publishing
What to do
Review the UW Web Checklist before launching or updating your site.
Why it matters
This checklist covers accessibility, usability, branding, and technical standards. It’s a final quality assurance step to ensure your site meets UW expectations.
How to get started
Go to go.uw.edu/webchecklist and walk through each item before publishing.
Review and remove outdated content
What to do
Before investing time in remediating accessibility issues, review your site’s content to identify outdated or irrelevant material. If content is no longer needed, delete it. If it must remain available for historical or compliance reasons, consider archiving it.
Why it matters
Outdated content can clutter your site, confuse users, and create unnecessary accessibility remediation work. However, not all content can be deleted. In such cases, marking it as archived helps users understand its status and reduces accessibility obligations.
How to get started
Review the guidance from the ADA Coordinator’s Office on archiving web content and use the archive banner to clearly label archived content.
Join the community and learn with your colleagues
What to do
Engage with the vibrant accessibility and web communities at UW. Attend events, join mailing lists, and participate in conversations with others who are passionate about creating inclusive digital experiences.
Why it matters
You’re not alone in this work. There is a strong network of developers, designers, strategists, and accessibility advocates across campus who are ready to share knowledge, offer support, and collaborate. Being part of the community helps you stay informed, inspired, and connected.
How to get started
- Attend ATS Events: Accessible Technology Services hosts regular events focused on accessibility and inclusive design. Learn more at: go.uw.edu/accesstech-events
- Join the Monthly UW Web Accessibility and Usability Meetup: This is a great space to ask questions, share ideas, and learn from peers. Sign up via the AccessibleWeb mailing list: go.uw.edu/accessibleweb
- Participate in Web Council: Hosted by the UMAC Web Strategy Team, Web Council meets on the first Thursday of every month to discuss strategy, tools, and best practices. Details at: go.uw.edu/webcouncil
Get help when you need it
What to do
Reach out to the appropriate teams for support.
Why it matters
Collaboration ensures your site meets both accessibility and branding standards. The UMAC Web Strategy Team and ATS are here to help.
How to get started
How to get help:
- For branding, style, and use of themes, templates, and/or plugins, contact the UMAC Web Strategy team at go.uw.edu/help.
- For accessibility and coding support, contact Accessible Technology Services at go.uw.edu/accesstech-help.
Maintenance and updates to this content
This page is maintained by the UMAC Web Strategy Team. For questions, updates, or suggestions, please email uweb@uw.edu.