All Posts

The article is a companion to the Now Learning course From the Experts: User Experience (UX) Leading Practices: Organizing Content   If you want to learn the practices that help you organize content effectively, enroll in the course.   Tree testing is a usability technique that can help you evaluate how easy or difficult it is for employees to find topics on the portal. It can be used to assess the findability, labeling, and information architecture. With tree testing, you can identify navigation issues early on and make improvements to ensure your users can quickly find the information they need.   This is a sample tree test where you get to experience what your users would see as they go through the exercise. You will be shown a series of tasks. Beneath the task, there will be a menu of categories and subcategories that you can access by clicking on the category. For each task, select which sub-category you would expect to go to in order to complete the displayed task. Link to the tree test: https://sky.mu-iq.com/run-task-survey?pbid=2367184   Let's get started!

Method Overview Through this method, you create a timeline of touchpoints between the user, the application(s), and any people/organizations they interact with. This method is used to see the process or service from the users’ perspective. You can map out the current state of a process or envision an idealized future state via journey mapping.   When to Use Digitizing a manual, paper-based process. Replatforming a process onto ServiceNow. Reviewing an existing process that has a negative NPS.   Outcomes Alignment among internal teams of overall opportunities and gaps. List of unmet user needs and pain points. Identified process gaps and opportunities to streamline. No assumptions about how the process occurs. Visualization of the end-to-end customer experience. Prerequisites Scope and clear objectives of the project Primary user persona(s) and their goals identified. Insights from user observations and conversations.     Participants Process owner, product manager, business analyst, design strategist, developer, and stakeholders   Materials Needed Conference room, whiteboard, markers, roll of paper. Or real-time collaboration whiteboarding tools such as Miro, or Mural Agenda Duration Activity 5 minutes Welcome & agenda 10 minutes Icebreaker / energizer 90 minutes Create journey map 5 minutes Wrap up & next steps   What do you do after? Synthesize findings into final map. Capability Cards workshop Alignment Jam   Related Plays Building Empathy   Learn More Journey Mapping 101 The 5 Steps of Successful Customer Journey Mapping Journey Mapping Course How to Run a Journey-Mapping Workshop: A Step-by-Step Case Study

Observe users interacting with your solution prototype or solution to identify issues affecting their ability to complete tasks. Method Overview Usability testing is critical to including users in the process of building a solution on ServiceNow. Testing provides you with real evidence of the effectiveness of your team’s solution. By asking real users to complete actual tasks and observing their behavior you’ll identify issues with the solution and learn about their behavior.   A usability test requires a facilitator to meet 1 on 1 with each participant and ask them to complete a series of tasks in the actual application, or a prototype. Ideally, a second observer is watching the interactions and taking notes of issues and behaviors. After all sessions are completed, the observations are synthesized for review and planning.   There is plenty of research on the right number of participants to include in your study but a general rule of thumb is to: Once the rate of discovering new issues slows, you’ve tested with enough users.   Outcomes Better understanding of users’ behavior when completing the assigned tasks Improved user experience if the observed issues are addressed   Prerequisites List of 3-5 common tasks users come to the site to perform. An interactive prototype (can be paper, design mockups) or the actual application (ideally in a non-production environment).   Participants Test participants should represent potential users of the site and have limited experience with the solution they will be interacting with.   Materials Needed Teleconferencing – if participants are remote or to allow observer to take notes from another room Interactive prototype or application   Process See the attached Usability Study Script for a sample facilitator's guide.   Prepare for the test by drafting a Facilitator’s Guide that helps the facilitator introduce the study and present the tasks Pilot the test with at least 1 person to ensure the tasks are clear and the prototype does not have any functional bugs. Work with stakeholders to recruit at least 5 participants for the initial round of testing. When the test begins, remind the participant that this is a test of the system, not the user so there are no wrong answers. Your goal is to get them talking aloud, describing what they are doing. During each session, the observer documents issues, behaviors, and any other insights that may help improve the overall experience. After all sessions are complete, aggregate the notes to see what issues were most common across the participants Prioritize the issues based on frequency of occurrence and impact to task success.   Synthesis Review the issues with the project team and identify remediation plans to improve the overall user experience. Once you make changes to the mockup or solution, rerun the usability study with new participants.   Learn More Usability Testing 101 (Nielsen Norman Group) Checklist for Moderating a Usability Test (Nielsen Norman Group) 10 Golden Rules of Facilitation (MeasuringU)  

ServiceNow's technology is powerful. This isn't news to anyone reading this blog post. We all know ServiceNow can be the engine to power your company's digital transformation dreams. But if you're not considering User Experience, you're not getting the most out of your ServiceNow investment. Why? Because building great workflows requires more than just great technology. It requires an understanding of the people those workflows serve; their needs, pain points, and goals. In our Knowledge23 Lab session, Patrick Healy and I outlined a 5 step plan to encorporate UX methods and tools into your next business process transformation project. It might seem like a lot to learn at first, but the great news is this plan works for any business process. Whether you are reimagining employee onboarding, finding new efficiencies in supply chain management, or something else entirely, you can use these steps time and time again to build business processes that work for people.    

Method overview When your team sets off on a journey to deliver a project, it is critical that everyone is aligned on 1-2 long term goals. These shared goals will help drive decision making as you balance scope and timeline.   Outcomes Some of the outcomes you will achieve by doing this is Alignment on desired project outcomes Framework for making decisions during the project lifecycle   Prerequisites Identify the project champion. This person is the lead stakeholder with the most influence or responsibility. They will have a unique role during the activity. In the voting activity, they will vote after everyone else.   Participants 3-6 stakeholders that are responsible for the outcomes of the project.This should include the project champion.   Materials needed 3” x 5” (76mm x 127mm) sticky notes Permanent markers Voting dots [if virtual] Online collaboration tool like Miro or large conference room   Method steps Hand out a pad of stickies and markers to each participant Present the prompt “In two years time…” by writing in on a whiteboard or large sheet of paper. You can make the timeline shorter or longer based on your project scope. Give participants 5 minutes to find at 2 least two different ways to finish that prompt as it relates to the project. Consider how you might talk about this project with your colleagues, friends, or family when it is successful. Have everyone present their statements and place the sticky notes on the wall. Reserving 1 color for the project champion, give everyone else 3 voting dots and ask them to vote on their favorite statement(s). They can use all their votes on 1 statement or distribute as they wish. Ask the project champion to review all the voting dots and then decide where to place their 3 voting dots Tally the votes. If there are 2 statements that end up in a tie, work as a team to rewrite the one ideal statement as your long-term goal. You can choose to keep both goals, but recommend no more than 2 long term goals. If your project team is located together, create posters with the goal(s) on them and put them up in your space, to remind your team of why they are there.

Hello User Experience Community!   We've created this document to answer Frequently Asked Questions (FAQs) that you might have. Please feel free to comment; we'll update this post as a living doc.   What is the purpose of the User Experience Special Interest Group (UX SIG)? What are the goals? The goal of this group is to discuss, educate, share, and learn. We want to help people deliver great user experiences on the ServiceNow Platform. We are focusing on: Helping user experience professionals learn about the specifics of UX on ServiceNow Helping non-UX professionals learn how to deliver great experiences with ServiceNow Creating a space/community to share knowledge Supporting each other   Who is this for? This is for everyone!  It doesn't matter if you're a user experience professional or not. That said, we will focus on two key personas: UX Pros who want to learn more about UX on ServiceNow Non-UX Pros: ie ServiceNow admins and developer, business analysts, IT folks and leaders that want to ensure that their ServiceNow applications have great experiences  Anyone else in your company who might be interested in delivering great user experiences on the Now Platform    Why should I spend time here? What do I get out of it? Learning, support, community.  This is a place where folks hang out to help others and share their expertise.   What kinds of things can I post? All kinds of things, but please keep in mind that this is a public forum, so no confidential or secret information, please: Questions & Answers  Best practices Tips and tricks Discussions about features and functionality UX-specific topics (ie processes, methods, tools, etc)   Can I invite others to join this community? Absolutely.  The more the merrier, and everyone is welcome.  If you happen to know UX pros who are not a part of the community, please encourage them to join and share their expertise.

ServiceNow's technology is powerful. This isn't news to anyone reading this blog post. We all know ServiceNow can be the engine to power your company's digital transformation dreams. But if you're not considering User Experience, you're not getting the most out of your ServiceNow investment. Why? Because building great workflows requires more than just great technology. It requires an understanding of the people those workflows serve; their needs, pain points, and goals. In our Knowledge23 Lab session, Patrick Healy and I outlined a 5 step plan to encorporate UX methods and tools into your next business process transformation project. It might seem like a lot to learn at first, but the great news is this plan works for any business process. Whether you are reimagining employee onboarding, finding new efficiencies in supply chain management, or something else entirely, you can use these steps time and time again to build business processes that work for people.  

Observe users interacting with your solution prototype or solution to identify issues affecting their ability to complete tasks. Method Overview Usability testing is critical to including users in the process of building a solution on ServiceNow. Testing provides you with real evidence of the effectiveness of your team’s solution. By asking real users to complete actual tasks and observing their behavior you’ll identify issues with the solution and learn about their behavior.   A usability test requires a facilitator to meet 1 on 1 with each participant and ask them to complete a series of tasks in the actual application, or a prototype. Ideally, a second observer is watching the interactions and taking notes of issues and behaviors. After all sessions are completed, the observations are synthesized for review and planning.   There is plenty of research on the right number of participants to include in your study but a general rule of thumb is to: Once the rate of discovering new issues slows, you’ve tested with enough users.   Outcomes Better understanding of users’ behavior when completing the assigned tasks Improved user experience if the observed issues are addressed   Prerequisites List of 3-5 common tasks users come to the site to perform. An interactive prototype (can be paper, design mockups) or the actual application (ideally in a non-production environment).   Participants Test participants should represent potential users of the site and have limited experience with the solution they will be interacting with.   Materials Needed Teleconferencing – if participants are remote or to allow observer to take notes from another room Interactive prototype or application   Process See the attached Usability Study Script for a sample facilitator's guide.   Prepare for the test by drafting a Facilitator’s Guide that helps the facilitator introduce the study and present the tasks Pilot the test with at least 1 person to ensure the tasks are clear and the prototype does not have any functional bugs. Work with stakeholders to recruit at least 5 participants for the initial round of testing. When the test begins, remind the participant that this is a test of the system, not the user so there are no wrong answers. Your goal is to get them talking aloud, describing what they are doing. During each session, the observer documents issues, behaviors, and any other insights that may help improve the overall experience. After all sessions are complete, aggregate the notes to see what issues were most common across the participants Prioritize the issues based on frequency of occurrence and impact to task success.   Synthesis Review the issues with the project team and identify remediation plans to improve the overall user experience. Once you make changes to the mockup or solution, rerun the usability study with new participants.   Learn More Usability Testing 101 (Nielsen Norman Group) Checklist for Moderating a Usability Test (Nielsen Norman Group) 10 Golden Rules of Facilitation (MeasuringU)

Method Overview Through this method, you create a timeline of touchpoints between the user, the application(s), and any people/organizations they interact with. This method is used to see the process or service from the users’ perspective. You can map out the current state of a process or envision an idealized future state via journey mapping.   When to Use Digitizing a manual, paper-based process. Replatforming a process onto ServiceNow. Reviewing an existing process that has a negative NPS.   Outcomes Alignment among internal teams of overall opportunities and gaps. List of unmet user needs and pain points. Identified process gaps and opportunities to streamline. No assumptions about how the process occurs. Visualization of the end-to-end customer experience. Prerequisites Scope and clear objectives of the project Primary user persona(s) and their goals identified. Insights from user observations and conversations.     Participants Process owner, product manager, business analyst, design strategist, developer, and stakeholders   Materials Needed Conference room, whiteboard, markers, roll of paper. Or real-time collaboration whiteboarding tools such as Miro, or Mural Agenda Duration Activity 5 minutes Welcome & agenda 10 minutes Icebreaker / energizer 90 minutes Create journey map 5 minutes Wrap up & next steps   What do you do after? Synthesize findings into final map. Capability Cards workshop Alignment Jam   Related Plays Building Empathy   Learn More Journey Mapping 101 The 5 Steps of Successful Customer Journey Mapping Journey Mapping Course How to Run a Journey-Mapping Workshop: A Step-by-Step Case Study

The article is a companion to the Now Learning course From the Experts: User Experience (UX) Leading Practices: Organizing Content   If you want to learn the practices that help you organize content effectively, enroll in the course.   Tree testing is a usability technique that can help you evaluate how easy or difficult it is for employees to find topics on the portal. It can be used to assess the findability, labeling, and information architecture. With tree testing, you can identify navigation issues early on and make improvements to ensure your users can quickly find the information they need.   This is a sample tree test where you get to experience what your users would see as they go through the exercise. You will be shown a series of tasks. Beneath the task, there will be a menu of categories and subcategories that you can access by clicking on the category. For each task, select which sub-category you would expect to go to in order to complete the displayed task. Link to the tree test: https://sky.mu-iq.com/run-task-survey?pbid=2367184   Let's get started!

Introduction Most requestor experiences on ServiceNow are built on top of the Service Portal framework. This framework brings together AngularJS and Bootstrap to provide an extensible, responsive user experience. Many customers of ServiceNow choose to theme their experience to match their company’s brand. This guide will walk you through your theming options from the simple to complex.   How to approach theming If your company has established branding guidelines for web applications, there usually is a team that owns that specification. Try to partner with them to adapt the guidelines to the options the platform allows you to manipulate. Absent branding guidelines, you may be able to reference your company’s public web site or other well regarded applications and inspect the style used there.   There a few things to focus on to effectively apply your brand Primary and secondary colors - these are often used for calls to action, buttons and navigation items throughout your reference site. Spacing - does your reference site have an airy, spaced-out design or a condensed, focused layout? This may affect how you apply margins. Fonts - By default, the Employee Center portal uses the Lato font, and the stock Service Portal demo uses Source San Pro. You may choose to override this with your brand’s font. Depending on the complexity of the changes you want to make, your familiarity with CSS and SASS, and your plans to scale your use of ServiceNow, there are multiple paths to take when it comes to theming.   Branding Editor The simplest way to theme a portal is via the Branding Editor; which provides a real time preview of the impacts of your changes. You do not need any knowledge of CSS or SASS. Depending on the portal you select, a limited set of color overrides are provided. Changing these variables will only apply to the specific portal selected in the interface.   Changes made in Branding Editor appear in the “CSS variables” field on portal record in  sp_portal .   Variable Overrides The Service Portal framework uses the Bootstrap (v3.3.6) frontend toolkit as the foundational stylesheet. If you understand the basics of SASS variables, you can easily override the out of the box themes. The platform exposes the SASS variables as if you were building you are bootstrap CSS file from source. That means you can set variables overrides in the portal record. To get to the portal record. Open the Application Navigator Search for  Portals Click on the Portals menu item underneath Service Portal Open the record that correspond to the portal you are working on Create or modify the variables in the CSS Variables field   Variable Reference - This uses the LESS prefix of an  @  symbol while SASS expects a  $ Theme Records Creating a theme record and then applying it to the portal is the recommended approach for creating scaleable branding across your instance. One theme record can be applied to multiple portals, giving you a central place to make changes once and impact many experiences.   Docs: Create a Portal Theme   In the theme record you can set the SASS variables or use the CSS Includes related list to write your own CSS for the elements within the portal. For example, in a CSS include you can create a CSS selector that overrides the style for  .text-muted  with any properties you want, you are not just limited to Bootstrap’s variables.   Bootstrap CSS Helper Class Reference   More Specific Options The framework allows you to override styles at the page level, in a widget definition or an instance of a widget.     For a full breakdown of styling options reference the Docs article Service Portal styles   Fonts in Service Portal There is no one-size fits all guidance for overriding a portal’s default fonts. A lot depends on your IT infrastructure security and ability to access hosted fonts. A few options that are out there Use a CSS Include with the Source set to  URL  and paste in the link to the hosted font. Encode the font as Base64 and paste it directly into a CSS Include Attach the font files to a CSS include record and reference via  sys_attachment.do?<SYS_ID> Work with your platform owner and admin team to figure out what works for your environment.  

Method overview When your team sets off on a journey to deliver a project, it is critical that everyone is aligned on 1-2 long term goals. These shared goals will help drive decision making as you balance scope and timeline.   Outcomes Some of the outcomes you will achieve by doing this is Alignment on desired project outcomes Framework for making decisions during the project lifecycle   Prerequisites Identify the project champion. This person is the lead stakeholder with the most influence or responsibility. They will have a unique role during the activity. In the voting activity, they will vote after everyone else.   Participants 3-6 stakeholders that are responsible for the outcomes of the project.This should include the project champion.   Materials needed 3” x 5” (76mm x 127mm) sticky notes Permanent markers Voting dots [if virtual] Online collaboration tool like Miro or large conference room   Method steps Hand out a pad of stickies and markers to each participant Present the prompt “In two years time…” by writing in on a whiteboard or large sheet of paper. You can make the timeline shorter or longer based on your project scope. Give participants 5 minutes to find at 2 least two different ways to finish that prompt as it relates to the project. Consider how you might talk about this project with your colleagues, friends, or family when it is successful. Have everyone present their statements and place the sticky notes on the wall. Reserving 1 color for the project champion, give everyone else 3 voting dots and ask them to vote on their favorite statement(s). They can use all their votes on 1 statement or distribute as they wish. Ask the project champion to review all the voting dots and then decide where to place their 3 voting dots Tally the votes. If there are 2 statements that end up in a tie, work as a team to rewrite the one ideal statement as your long-term goal. You can choose to keep both goals, but recommend no more than 2 long term goals. If your project team is located together, create posters with the goal(s) on them and put them up in your space, to remind your team of why they are there. Learn more Design Thinking Toolkit - Long term goal Design Sprint 2.0 Monday - Long Term Goal & Sprint Questions (external)

  Background ServiceNow's product design organization – known as the Experience Team (EX) – uses Figma as the primary design tool to create wireframes and prototypes of the screens that become our products with each release. To support the 500+ designers creating product-specific prototypes, the DesignOps and Design Systems teams curate libraries of components and styles that reflect our core design systems.   These libraries represent the widgets (Employee Center / Service Portal), components (UI Builder, Next Experience, Workspaces, and Classic Environment) and elements (Mobile) that make our UIs come to life.   For you, our customers and partners configuring our customizing solutions on ServiceNow, these libraries can serve as building blocks to explore ideas for your unique needs.   Within each kit are instructions on how to setup the libraries on your Figma Team or Organization plans so that colleagues across your organization can collaborate   To download the kit, visit our Figma Community profile   Our libraries provide components, styles, and templates for: Classic Environment Configurable Workspaces Employee Center Mobile Next Experience   Getting Help If you run into any issues please post a question to the UX SIG and the team will respond within 5 business days.   Legal Disclaimer Please review the attached legal disclaimer before working with the files

In any project, it is important to gain an understanding of the users' expectations, experiences, and needs to deliver a positive outcome. We want to thank you for coming to the Continue building better workflows by understanding your users lab. Below you will find a recap of the lab, a list of resources that will help you research journey and opportunities to participant in ServiceNow research. Its worth mentioning that this framework is not limited to building a product and is applicable to many strategic initiatives, and especially relevant to those responsible for implementing and managing ServiceNow workflows in their organizations.  Why understanding your users is important Understanding your users ensures you deliver a solution rather than an invention. A solution implies the product takes into account user's thoughts, feelings, and behaviors. Additionally, understanding your users allows you to learn about their needs. User needs are key to product success as building for user needs increases the probability of success. To identify needs effectively, it requires a systematic and continuous process of understanding your users, thus, following the research process will guide you on your journey. Overview of the research process     At a high level, these are the milestones for a research project. All are important in their own way, but identifying research objectives deserves a special call out. Clear research objectives are important because they establish direction. Research with unclear direction will not be conducted effectively because if you have vague direction you will get vague results. Research objectives also have implications for your study's methodology and general logistics because you make these decisions based on what puts you in the best position to answer your questions. Qualities of great research objectives Generally you want to have 3 - 5 objectives per study. The concern with having more is that you spread yourself to thin and reduce the quality of your findings. Open ended and consider cause and effect This refers to focusing on a topic with substance and sets you up to explore the interconnectedness of users. Provide a path for more follow research Compelling objectives often lead to more questions, which requires more research.  Pass the so what test Meaning they are of relevant and interest to others, usually tied to a business goal or something relevant going on at your organization. UX Research Methods       There is no best method or type of research. There are many factors that go into selecting which one you should employ, but the choice is primarily driven by your research objectives. Other factors you should consider: General logistics Time Access to end users Level of confidence in findings How much data to collect? What's more important than how many users you collect data from is that you are collecting data from people who are most representative of your end user. Generally, when conducting qualitative research the sample size is smaller whereas in quantitative research the sample size is larger.   It is important to remember that they are people and not just test subjects that provide data. You must keep ethics in mind regarding the types of questions you ask, obtaining consent to collect data, and how you handle and protect the collected data.   Writing your discussion guide A discussion guide is a written roadmap of your interview conversation and the questions you want to ask.     Tips for structuring the questions in your discussion guide Group related questions together Start broad and then get more specific Be mindful of question order Tips for writing good interview questions Open ended (What.., how..., why..., tell me about...) Avoid leading questions Moderating an interview Tips to moderate like a pro Involve your stakeholders Have an observer/notetaker Remember to stay neutral Resist the urge to explain Analysis Tips for analyzing data Check hypothesis and identify themes Categorize or tag your data in a tool (ex., Excel, Miro)         Suggested reading: Want to learn more about UX research methods and strategy? Here are some places to get started: NN/g Nielsen Norman Group MeasuringU dscout User Interviews UserTesting   Sign up to participate in ServiceNow research studies! We want to ensure we are providing the best possible experience for all customers. To achieve this, we need your help to understand your ServiceNow experiences and needs. Research studies can range from 2 to 90 minutes, with compensation (if eligible). Learn more here or sign up now.

Accessibility is an important part of all digital experiences — and at ServiceNow, we believe that everyone should have the opportunity to use our Platform and Products. What this means, is that we design with all backgrounds, abilities, disabilities, and various needs in mind to ensure that we can offer the most inclusive experience possible.   Thank you for coming to the Accessibility Leading Practices presentation and Designing for Accessibility pod at Knowledge 2023. Here is a list of resources and tools we know that you will enjoy, learn from, and use to improve the accessibility of your ServiceNow instances and implementations.       ❗Important quick links Accessibility Leading Practices presentation This presentation (PDF is also located at the bottom of this article) covers how ServiceNow makes products accessible as a collective team, along with 6 leading practices and tools to help you be successful today.   Sign up to participate in ServiceNow accessibility research studies! We want to ensure we are providing the best possible experience for all customers and ensure our products are accessible for everyone. To achieve this, we need your help to understand your ServiceNow experiences and needs. Research studies can range from 2 to 90 minutes, with compensation (if eligible). Learn more here or sign up now.     Design & Research Tools Order your Accessibility cards For the first time, ServiceNow is releasing our accessibility cards! These cards are to be used side-by-side with your organization’s personas (target users) and highlights major differences and solutions people with disabilities may encounter when interacting with digital experiences, along with listed solutions. This was created and driven by primary and secondary research, and can be used by anyone in your organization. Order here now to get your free cards shipped to your home (please enter your work email and use access code: a11y).   Design annotation templates Our Figma accessibility design annotation template  (located in the ServiceNow Figma community profile) includes annotation options for labeling many common needs for accessibility. This includes color contrast, keyboard usage, alternative text, and even forced colors or Windows High Contrast Mode. This template can be used by designers, engineers, and quality teams to ensure everyone is on the same page for accessibility.   Color contrast automated checking tools Ensuring appropriate contrast for your text and informational graphics is a fundamental requirement for accessible design. There are many online tools and plug-ins for testing and finding accessible color combinations. Here are some of our favorites: aremycolorsaccessible.com colorsafe.co WebAIM Contrast Checker Contrast plugin for Figma   Development Tools Accessibility automated evaluative tools Test automation tools can help identify potential accessibility issues in your content and to give you quick insight as to what changes you might need to make. These tools typically can find some of your accessibility defects (but not all). Here are some of our favorites: Axe DevTools Chrome extension WAVE browser extension Accessibility Insights Evinced ANDI   Base components via Next Experience Components The ServiceNow Next Experience Component Reference is an amazing resource to learn about our components, their UI Builder configurations, Accessibility API properties, and usage guidelines. You can also configure our components live in the Component Playground. For highly customized components outside of this, you can use W3C’s ARIA authoring practices guide to help assist you.     Learning Resources Community articles Read more about some best practices and guidance for targeted ServiceNow products Service Portal: design guidelines Service Portal: best practices Knowledge: guide for writing accessible articles   Product Accessibility Conformance Reports  Learn about how ServiceNow products are meeting accessibility standards, such as the Web Content Accessibility Guidelines (WCAG). These reports are available for the currently supported ServiceNow releases. View the accessibility conformance reports here.   ServiceNow’s Accessibility statement Learn more about ServiceNow and its accessibility commitment.     More opportunities Join the Accessibility Product Advisory Council (PAC) This PAC is an annual program for a group of customer representatives selected to participate in a product-specific advisory board based on extensive accessibility knowledge. This is a unique opportunity to advice and influence accessibility of ServiceNow products through quarterly collaborative events. To join, please contact Tony Morales (tony.morales@servicenow.com)     Have accessibility questions? Contact accessibility_support@servicenow.com