The web Browser you are currently using is unsupported, and some features of this site may not work as intended. Please update to a modern browser such as Chrome, Firefox or Edge to experience all features Michigan.gov has to offer.
SOM Applications and Site Standards
SOM Applications and Site Standards
When citizens interact with the State of Michigan (SOM), our goal is to make their transition from one platform to another, and from one agency to another, as seamless and easy as possible. Consistent content design and branding across websites, mobile applications, social media, and other digital communications helps build a unified user experience and establishes trust with citizens.
When designing, procuring, or proposing digital solutions for the SOM, please be aware of these policies and the below standards and guidelines to ensure they are integrated into your products and digital services.
SOM Web Applications Standards
The SOM Web Application Standards were documented to ensure that visitors have a similar experience throughout all state applications, portals, and agency sites.
All SOM applications must adhere to:
1. Applications developed after May 31, 2018, must follow:
Applications in development before May 31, 2018, may follow the:
- State of Michigan (SOM) Look and Feel Standards
- Center for Shared Solutions (CSS) Application Templates
2. Meet conformance level AA of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines 2.0
3. Complete a SOM Digital Standards Review to ensure standards are met
- In a move to ensure internal and external applications adhere to SOM Digital standards and guidelines, and simplify the accessibility review process, the Michigan Department of Technology, Management and Budget (DTMB) eMichigan team has updated the SOM Digital Standards Review (DTMB-3533) form. To initiate an application review, submit the DTMB 3533 form to the DTMB eMichigan team at firstname.lastname@example.org
- Reviews can be initiated in the design or development phase to find and fix issues as early as possible.
- After the DTMB eMichigan team completes the review, results with any identified issues will be returned to the requestor. Identified issues must be corrected and returned to the eMichigan team for re-review. This is an iterative process until all issues have been resolved and verified by eMichigan.
4. Accessibility issues identified during the SOM Web Application Review(s) must be resolved prior to production release.
5. Adhere to related SOM Native Mobile Application Guidelines, SOM Website Guidelines, SOM Social Media Standard and Guidelines and follow all SOM Accessibility Standards and Guidelines.
SOM Native Mobile Application Guidelines
The Native Mobile Application Guidelines communicates important design and development standards for native mobile applications produced and maintained for the purpose of conducting official state business with the SOM.
SOM Website Guidelines
- State of Michigan Browser Requirements
- SOM Digital Standards
- Digital Guidelines
- Internet Domain Management Standard, currently on SharePoint.
- Internet Domain Name Standard for Michigan.gov Portal, also currently on SharePoint.
- Michigan.gov Marketing URL Guidelines
Questions can be sent to eMichigan@michigan.gov.
SOM Social Media Guidelines
The SOM encourages the use of social media, social networking sites and emerging web tools to enhance transparency, communication, customer service, collaboration and information exchange among the SOM and the public. To view current social media standards and guidelines visit our social media standard page.
Questions can be sent to email@example.com.
SOM Digital Accessibility Guidelines
The SOM is committed to providing access to public information for all citizens, including those with disabilities, who use state websites, applications, and digital services. In keeping with the Americans with Disabilities Act of 1990 (ADA) and the spirit of effective citizen-centric communication, the SOM has adopted:
- 1650.00 Accessibility and Reasonable Accommodations & Modifications Policy
- 1650.01 Reasonable Accommodations, ADA Title I
- 1650.02 Accessibility and Reasonable Modifications, ADA Title II
Effective October 23, 2019, policy updates cover all Executive Branch Departments, Agencies, and Sub-units.
Vendor Proposed IT Solution Reviews
The SOM has adopted a formal policy regarding accessibility requirements. The SOM evaluates the accessibility of vendor’s proposed IT solutions through the use of documents called Voluntary Product Accessibility Templates (VPAT) and Government Product Accessibility Templates (GPAT). Vendors use these document to self-assess their products accessibility. To learn more about our standards review process visit the page below:
Michigan Voluntary Product Accessibility Template (VPAT) Standards Review Process
Accessibility - Testing Tools
- Color Contrast Checker
- Chrome Accessibility Developer Tools
- Chrome WAVE
- JAWS Screen Reader
- NVDA Screen Reader – (Available in SOM Software Center)
Accessibility - Resources
- SOM ADA Electronic Resource Guide, currently on SharePoint.
- Easy Checks – A First Review of Web Accessibility
- WebAIM’s WCAG 2.0 Checklist
- Mobile Accessibility Guidelines 2.0
- Introduction to Web Accessibility
- 10 Easy Accessibility Tips Anyone Can Use
- 18F Accessibility Guide
- Alternative Text
- Captions, Transcripts, and Audio Descriptions
- Keyboard Accessibility
- "Skip Navigation" Links
- Color Contrast Checker
- Creating Accessible Forms
- Creating Accessible Tables
- Seizure Disorders
- Accessibility of Rich Internet Applications
- Michigan Voluntary Product Accessibility Template (VPAT)
Accessibility for Multimedia
- WCAG 2.0 Standards for Video and Audio
- Multimedia Accessibility FAQ
- How to Add YouTube Video Captions
Accessibility for PDF and Word documents
- PDF Accessibility
- Make PDFs accessible
- How to specify the language for a passage or phrase in PDF documents
- How to Test a Document Using JAWS (video)
- Make Word docs accessible
Questions on digital accessibility can be sent to firstname.lastname@example.org.