1.1 Website Discovery

• ☐ Identified all primary agency websites
• ☐ Catalogued all subdomains (e.g., subdomain.agency.texas.gov)
• ☐ Documented all departmental microsites
• ☐ Listed all online service portals
• ☐ Identified third-party hosted sites (.com domains, vendor platforms)
• ☐ Discovered “shadow IT” websites (unauthorized or forgotten sites)
• ☐ Documented mobile apps with web components
• ☐ Created master inventory spreadsheet with URLs, owners, and purposes

Total websites/portals identified: ___________

2.1 WCAG 2.1 Level AA Testing

Perceivable: Information and user interface components must be presentable to users in ways they can perceive.

• ☐ All images have appropriate alt text
• ☐ All non-text content has text alternatives
• ☐ Video content includes captions
• ☐ Audio content has transcripts or captions
• ☐ Color is not the only method of conveying information
• ☐ Sufficient color contrast ratios (4.5:1 for normal text, 3:1 for large text)
• ☐ Text can be resized up to 200% without loss of functionality
• ☐ Content is readable in both portrait and landscape orientation

Operable: User interface components and navigation must be operable.

• ☐ All functionality available via keyboard
• ☐ No keyboard traps exist
• ☐ Users can control time limits on content
• ☐ Content does not flash more than 3 times per second
• ☐ Users can skip repetitive content (skip navigation links)
• ☐ Page titles are descriptive and unique
• ☐ Focus order is logical and intuitive
• ☐ Link purpose is clear from link text or context
• ☐ Multiple ways to navigate to pages (menus, search, sitemap)
• ☐ Headings and labels are clear and descriptive
• ☐ Keyboard focus is visible

Understandable: Information and user interface operation must be understandable.

• ☐ Language of page is programmatically identified
• ☐ Language changes within content are identified
• ☐ Pages behave in predictable ways
• ☐ Navigation is consistent across pages
• ☐ Form fields have clear labels
• ☐ Error messages are clear and helpful
• ☐ Error prevention for legal/financial transactions

Robust: Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.

• ☐ HTML validates with no major errors
• ☐ Elements have complete start and end tags
• ☐ ARIA attributes used correctly
• ☐ Status messages can be programmatically determined

3.1 Navigation & Findability

• ☐ Primary navigation is clear and intuitive
• ☐ Maximum 3-click rule to key content/services
• ☐ Search functionality is prominent and works effectively
• ☐ Breadcrumb navigation implemented
• ☐ Site map available
• ☐ 404 error pages are helpful and provide navigation options
• ☐ Mega menus (if used) are organized logically
• ☐ Footer navigation includes key links

4.1 Forms & Applications

• ☐ All forms accessible online
• ☐ Forms can be filled out digitally (not just downloaded)
• ☐ Form fields have clear labels and instructions
• ☐ Required fields clearly marked
• ☐ Error validation provides helpful messages
• ☐ Confirmation messages displayed after submission
• ☐ Users can save progress on long forms
• ☐ Form data can be submitted electronically
• ☐ Mobile-friendly form design

5.1 Visual Consistency

• ☐ Reviewed DIR web page templates and guidelines
• ☐ Agency logo used consistently across all sites
• ☐ Color scheme consistent with state branding
• ☐ Typography follows DIR recommendations
• ☐ Header/footer design consistent across sites
• ☐ Visual hierarchy clear and professional
• ☐ Design is modern and not outdated

6.1 Content Audit

• ☐ Identified all outdated content (>2 years old)
• ☐ Identified duplicate or conflicting content
• ☐ Identified broken links and orphaned pages
• ☐ Reviewed all downloadable documents
• ☐ Identified content that should be archived vs. deleted
• ☐ Created content inventory spreadsheet

7.1 Security Standards

• ☐ HTTPS/SSL certificate active and valid
• ☐ Security headers configured properly
• ☐ Forms use CAPTCHA or similar spam protection
• ☐ Regular security updates applied
• ☐ Vulnerability scans performed regularly
• ☐ Data encryption for sensitive information
• ☐ Backup and recovery procedures in place

8.1 Consolidation Opportunities

• ☐ Identified similar or overlapping websites
• ☐ Identified low-traffic sites that could be merged
• ☐ Evaluated cost savings from consolidation
• ☐ Assessed technical feasibility of merging sites
• ☐ Considered user impact of consolidation
• ☐ Developed consolidation strategy and timeline

9.1 Assessment Documentation

• ☐ Completed comprehensive digital property inventory
• ☐ Documented all accessibility issues and remediation plans
• ☐ Recorded mobile responsiveness test results
• ☐ Documented performance benchmarks and improvements
• ☐ Created content audit documentation
• ☐ Documented consolidation decisions and rationale
• ☐ Compiled cost-efficiency analysis
• ☐ Created implementation timeline with milestones