Hi, Drupalites!
Thank you for your recent support on meeting SB1 mandates as it relates to web content.
Our next big hurdle, for which we need your ongoing collaboration, is to bring all of our digital content into compliance per the Department of Justice’s (DOJ) accessibility mandates by April 24, 2026.
As we continue our accessibility compliance efforts, we have two important updates about file management on the СƬƵ website.
Review and Remediate Your Files Before Accessibility Compliance Deadline
Now is the time to review and organize your files so you beat the April deadline for meeting accessibility compliance.
Please determine which webmaster or individuals in your department will be the project lead and/or contributors and notify Lin Danes.
Our Drupalites are hearing this first so you can begin preparing. We’ll notify university leadership about the requirement in the next few weeks.
How to get started? Take advantage of the guide on our website, which outlines these steps:
- Request a content export by submitting a ticket.
- Evaluate all PDFs and other files on your site.
- When doing so, ask yourself: Do I need this file?
No → Delete it and any links leading to it - but follow proper deletion steps (below)!
Yes → Determine which category:
- Historical internal document → Move to your department's shared server.
- Public historical document → Flag it to be moved to archive.
- The DOJ rule recognizes that not all older content needs full remediation. Documents that are no longer actively maintained but have genuine historical value can be preserved through the upcoming University PDF Archive. This option will be available in January but will require an extra step.
- Note: Content created after April will not meet historical archive criteria.
- You can . The rule includes specific exceptions for certain types of content, including archived web content.
- Important: When in doubt, delete rather than archive. Only preserve content with genuine historical value.
- The DOJ rule recognizes that not all older content needs full remediation. Documents that are no longer actively maintained but have genuine historical value can be preserved through the upcoming University PDF Archive. This option will be available in January but will require an extra step.
- Active, current document → Make current files accessible now via remediation in Word and/or Adobe and/or convert it to a true web page.
- This will be a requirement for all content after April 2026.
Need help with PDF accessibility? Stay tuned for upcoming workshops on PDF evaluation, remediation and accessibility best practices - more details coming soon.
New Process for Deleting Files
As you review your files for accessibility compliance, please follow the updated deletion process.
These steps will ensure files are removed properly from your site while maintaining site integrity. Bypassing these steps could allow for your file to still be findable through a Google, Bing or other search engine.
File Upload Changes Coming Soon
If you typically upload documents directly through the WYSIWYG editor, please note that this option is being retired. Going forward, files should be uploaded using the standard method outlined below.
What’s Changing
Editors will no longer be able to upload files directly using the Insert Media button in the WYSIWYG editor ribbon.
Adjusted Standard File Upload Process
To upload files to your site, create a new “File” content item and upload your document there. This has always been the standard process in Drupal—we’re simply removing the alternative WYSIWYG upload option to promote consistency and support accessibility compliance.
Remember: All files uploaded to the website should meet accessibility standards.
If you have questions about file management or need assistance with the triage process, please submit a ticket via our support and training webpage.
Happy editing!
Web Team
Jared Boehm, Senior Manager, Digital Enterprise Solutions
Lin Danes, Executive Director of Digital Communications (Web Services)
Laura Duarte Schneider, Student Web Support Specialist
Olivia Moye-Isaly, Student Web Support Specialist
Eddie Lampert, Web Designer
Paul McKinney, Web Designer
James Parsons, Web Content Coordinator
Tim Priester, Web Designer & Services Lead
Todd Randolph, Senior Applications Developer