Thank you for joining SF State in its effort to make all websites, software and mobile apps accessible to people with disabilities. One of the steps for “going live” with your Drupal website is to receive accessibility approval from the ATI team. The information below will help you better understand what is involved with this process.
Once you have submitted your request, allow 5-10 business days for the review and approval process. Please consider this timeframe when you a planning for the launch of your website. If you have an especially complex website, it will take longer.
Note: The following procedure applies to websites that are using the SF State Drupal template. We highly recommend that you use the Drupal template since it has been approved for both accessibility and branding. However, if you are not using the Drupal template we can still assist you in making your website accessible. Be aware that it will take significantly more effort on your part. Contact us at firstname.lastname@example.org if this is the case.
1. Create accessible content
After you receive a Drupal website in the development (“dev”) environment, you should begin to add content to your website with accessibility in mind. While the Drupal templates are accessible, the content that you add to your website might not be. This includes images, tables, multimedia, forms, documents, etc. While creating and editing your content, please follow guidelines on creating accessible web content. This will save you time and effort when you begin validating your content for accessibility later.
2. Validate accessibility of your content
2a. Automated accessibility assessment
Once you have finished creating website content in the Drupal staging environment and have a near-final version of your website, you will need to validate the accessibility of this content to ensure no accessibility issues were introduced. SF State provides access to an automated assessment tool called Compliance Sheriff that will crawl through pages on your website and provide you with a report on the accessibility of your content. You may either request an automated report or request an account so you may re-run your own reports as you correct issues.
2b. Manual accessibility assessment (optional)
Once your website has passed the automated checks, the last step is to perform a manual verification of your website. The automated tool cannot test for all accessibility checkpoints, so human verification is needed. This is an optional step for you since the ATI team will conduct manual testing when you submit your website for review. However, if you would like to perform it yourself, you may review the manual testing process. You may also download the Manual Assessment Summary.
3. Submit your website for ATI approval
The ATI team will use the same process as steps 2a & 2b above, so please ensure you have fixed the automated assessment errors before submitting your website for review.
Requests for exemptions to the SF State web accessibility standards are rarely granted. Exemptions are considered on a case-by-case basis and limited to mission critical university activities. If granted, exemptions are only valid for a specific, fixed and reasonable period of time, not to exceed one year.
Website exemption request procedure
- Complete assessment and remediation plan first and consult with the SF State ATI Team
- Prepare justification for exemption and fill out the Web Product Exemption Form.
- Obtain approval from the university Vice President you report to
- Submit request to SF State ATI
- Await response from SF State ATI before proceeding
- If an exemption is granted, include the interim accessibility language in your website
Document Exemption Procedures
If our assessment report indicates major accessibility issues within the documents on your website that will be difficult to fix within a short time frame, you will need to create a Document Exemption plan, submit it to the SF State ATI Team at email@example.com and place the Interim Accessibility Statement on your website.
Interim Accessibility Statements
SF State's Web Accessibility Guidelines require that all web and document content be accessible. In a situation where accessibility barriers are identified and cannot be immediately remedied, the content owner is required to supply an interim message to the web user.
In line with this goal, the SF State Web Accessibility Group has drafted the following Interim Accessibility Statement:
This website/The documents on this website has/have been identified as having barriers to accessibility. The [site owner] is working to remedy these access barriers by [date]. If you experience problems using this website/ the documents, contact [CONTACT PERSON / INFO].