Digital Service Standards (DSS)
The Digital Service Standards set the baseline requirements for all government digital services to be usable, accessible, and citizen-centric, ensuring consistent, high-quality digital experiences across agencies.
Last updated on 26 September 2025
Shaping a positive, consistent digital experience through the Digital Service Standards
The Digital Service Standards (DSS) (opens in new tab) outline the requirements and recommended practices that guide how government digital services are designed, built, and delivered. Grounded in user-centricity and accessibility, the DSS ensures that every digital interaction with the Government is simple, seamless, and inclusive, helping agencies and their partners create consistent, high-quality digital experiences that serve citizens better.
Organised into key categories, the framework ensures that services remain consistent, accessible, and citizen-centric, while upholding high standards of quality and trust.
Below is a summary of each category, with links to the full standards for detailed guidance.
Baseline Design Practices
Services must adopt consistent layouts, intuitive navigation, and clear language to ensure usability across services.
Examples of recommendations:
Implement Responsive Web Design techniques to ensure web-based digital services are optimised for various devices and screen sizes.
Use a design system such as the Singapore Government Design System (SGDS) (opens in new tab).
Implement contact channels such as phone numbers, email, contact forms, live chat.
Read full details for Baseline Design Practices (opens in new tab)→
Performance and Reliability
Digital services must be fast, stable, and resilient, with processes in place to monitor, review, and recover quickly when issues occur.
Examples of recommendations:
Clearly communicate scheduled downtime using methods like maintenance banners and in-app notifications.
Registration of all public facing digital services and implementation of WOGAA tracking code.
Regularly test your service on the latest two major versions of popular browsers such as Chrome, Firefox, Safari, and Edge.
Read full details for Performance and Reliability (opens in new tab) →
Trust and Legitimacy
Government services must demonstrate transparency and authenticity through secure domains, official branding, and consistent government identifiers to reassure users they are engaging with legitimate sources.
Examples of recommendations:
The service's logo should render clearly without distortion or pixellation to maintain trust and reinforce brand reputation.
The Official Government Banner (opens in new tab) must be the topmost component of the web service.
The footer (opens in new tab) must contain key links such as Contact Us, Feedback, Report Vulnerability, Privacy Statement, and Terms of Use.
Read full details for Trust and Legitimacy (opens in new tab)→
Transactions and Payments
Where payments are required, services must provide seamless, secure, and user-friendly transaction flows that minimise friction and give users confidence in their interactions.
Examples of recommendations:
Provide clear instructions and confirmation prompts to guide end users through the process to minimise errors.
Pre-fill forms with known data where applicable via Singpass/MyInfo integration.
Send acknowledgement via channels like SMS, email, push notification, or in-app notifications.
Read full details for Transactions and Payments (opens in new tab)→
Understanding Users
Government digital services should be designed with empathy and inclusivity, taking into account diverse user needs and contexts.
Examples of recommendations:
Take steps to understand end user context, needs, and problems before deciding on a solution via methods such as user research or data analytics.
Conduct usability testing at key milestones such as prior to public release.
Document findings in a structured report, prioritising issues based on severity.
Read full details for Understanding Users (opens in new tab)→
Accessibility (WCAG Principles)
Aligned with international Web Content Accessibility Guidelines (WCAG) (opens in new tab), government services must be operable, perceivable, robust, and understandable. The WCAG help increase accessibility of web content for persons with disabilities, seniors who experience changing abilities due to ageing, and everyday users who would also benefit from an improved user experience.
Examples of recommendations:
[Operable] Provide keyboard operation for all the functionality of the page unless the function requires path-dependent input such as handwriting.
[Perceivable] Provide accurate, concise alt text or a relevant textual description for non-text content (images, charts, media).
[Robust] Inform users of status changes, such as when an incorrect text in an input field is entered and a status message appears above.
[Understandable] Provide expanded forms of abbreviations the first time they appear on a page or provide contextual help such as inline explanations, tooltips, and glossaries.
Read full details for: