Hello everyone and welcome to the DQM Product Office Hour for November 2024. I'm Beata, Product Manager for DQM and I'll be guiding you through today's session. It's great to have you all here. Whether it's your first Office Hour or you've joined us before, thank you for taking the time to connect with Crownpeak. Let me give you a quick overview of what's on today's agenda. We'll start with a recap of 2024, highlighting the features we introduced this year and the value they bring to you. Then I will share our strategy for 2025, including our roadmap and the thinking behind it. After that, I will demo some of our key updates, showcasing how they work and why they matter. And finally, I will share with you how you can shape the future of DQM by sharing your feedback and ideas. One more thing before we dive in. If you are enjoying these Office Hours and want to stay up to date, mark your calendars with the following dates. We've got quarterly sessions planned for February, May and September next year. These sessions are a great way to stay ahead of new developments and get answers to your questions. We'll always aim to share with you the latest news on what's been going on in the DQM world and bring you exciting experts and answer all your questions. I hope to see you there. At your answers from the poll in the last product Office Hour session, I have asked you what kind of topics you would like to cover in the upcoming product Office Hours. And definitely, we've got very, very interesting answers. Most of you would like to find out more about our strategy for 2025, about our roadmap and rationale for upcoming initiatives. You would also like to learn more about benchmarking scores, DQM best practice and the recap of 2024. And this is what we will be looking at today to make sure that you get maximum value from the time you spend with us. All right, let's start by reflecting on 2024. It's been an exciting year for DQM. And we definitely focused on making your work faster, simpler and more efficient. And let me walk you through some of the insights. The first big addition this year was the DQM Jira integration. It's especially key for teams managing their issues in Jira. And obviously, this feature is for them a game changer. It will let you create Jira tickets directly from DQM checkpoints. That means no more manual copying over and pasting key details or losing some information along the way. In the ticket creation dialogue, you will be also able to choose the relevant project and ticket type that you need. And yeah, just ensuring that this is all tailored to your workflow. And in the next segment, the Jira creation dialogue is available in the analyzer view in DQM. But we are working on having this available in other screens. And definitely, this is where your feedback will be extremely valuable to us. The setup is quick and secure. The information that you will need to provide to us is a link to your Jira cloud instance, the API token, which you can get from your internal admins, and of course, details on the projects and ticket types that you would like to have available. The best way to get that setup is to contact our Crown Peak support team. This is the moment when you can take your phone out and scan the QR code. So under the QR code, there is a great user guide available, which explains in detail how you can make the most of the Jira integration. It will also direct you to a link on the Jira onboarding guide, where you have all the details that you need to set up the Jira integration. Now, let's talk about broken link reporting. So that was definitely a feature that was really anticipated and valuable in the beginning of 2024. We know that broken links can be very challenging to troubleshoot. So we've improved the data that we are providing to make sure that you have more agency and more ability to self-serve when it comes to troubleshooting the broken links within your organization. So what we have included in the DQM interface is the direct link to the page, which is no longer accessible. We have also included the date when the link was checked last time, so that it's much more simpler for you to contact your internal teams and find out why this link is no longer accessible. And additionally, within the export, so in the CSV export, we have included a problem code. So this is the code that can direct your teams to why this link has failed when it was checked. We've also made the data more precise by including in this view only true 404 errors. So these are the errors where the page was not found. So we are no longer including issues related to server timeouts or other false alarms. This will make it easier for you to prioritize and fix the links that truly matter. We've also improved checkpoint descriptions. And why does that matter? It's because customizing descriptions of the checkpoints helps you align DQM with your specific needs. You can add your brand standards, accessibility guidelines, or any other critical details. And this turns your DQM data, DQM information, into a single source of truth for your organization. It ensures that your teams are on the same page and working towards the same goals. And this is especially helpful since our new Jira integration actually copies over this information from the checkpoint description to the Jira tickets. So once this information has been included here, this will be also copied over to any tickets that you create within DQM, of course, if you are a Dura user. Now, I'm going to very quickly share a quick demo of the key items which we have released this year. So this is a very familiar to you screen of DQM website overview. And I'm going to start by navigating to the page I want to find out more about. And I'm going to scroll down to navigate the issues page. So this is the very familiar view where you typically go to find out which checkpoints have been affected in the latest scan, which checkpoints have broken, have issues. So to show you the new additions to broken links reporting, I'm going to expand checkpoint 2.2. And we can see that one broken link was discovered. So when you expand the section, you can see which specific link was broken. You can click on the link to view the page. And of course, this one is a 404 error. The page was not found. You can also see when this link was last checked. So this is the exact time when this link was checked during the scan cycle. So that can really help you troubleshoot what happened with this link. And in the export, under the export button, you will be also able to access the specific error code. In this case, that would be the 404 link. Now, let's have a look at the new exciting Jira integration. So I'm going to navigate to issue. Let me expand all of the affected checkpoints. I'm going to navigate to number one. And I'm going to have a look at page 12, which has 15 issues. I'm going to have a look at this page. And you can see that the error has been highlighted here. And we have a new button, which is probably something new to most of you, to create a Jira ticket. And a ticket and the issue type. I can add any information that I think relevant. Just for the sake of the demo, I'll add a few details. And you can see that the information from the checkpoint has been copied over. I will now create a Jira ticket. The ticket has been successfully created. I can click on the link to navigate to my Jira instance, see the information that has been copied over from the ticket. And for example, assign it to the member of my team who will be tasked with resolution. I can also add any necessary labels or team information, depending what's the next step in your workflow. And you can see that the ticket number is now listed on the left-hand side of the analyzer view. That makes it very clear to us which issues the ticket has been created for. Since this integration is only one directional for now, we are not able to pull the status of the ticket from your Jira instance. However, if this ticket has been solved, instead of waiting for the scan to clear this issue, I can just close the ticket by un-linking it from the DQM issue. And thanks to that, the ticket no longer persists in the view. In the future, we'll be looking to create a bi-directional integration that would make this process even more streamlined. Now, coming back to my issues view. I also wanted to show you the checkpoint management improvements. So this view might not be available to all users because it's specifically designed for the administrators. So definitely there is someone in your organization who has access to this view. And what I wanted to share with you is the ability to edit checkpoint summary and description to make it even more tailored to your organization. So the administrator is able to edit the checkpoint to include relevant information and then save. And same for editing this information. I will just add, make sure it's capitalized. And I will save. The data has been updated. And will be reflected for all users in your organization. Now, I will move over back to our presentation. That concludes our demo of Key 2024 releases. Not only the development team has been busy in this last year. The team of our accessibility experts and solution engineers have been working hard behind the scenes to bring even more knowledge and even more expertise to our customers. And there are two amazing webinars that I would really encourage you to catch up on if you haven't had a chance to attend them. The first one is related to navigating international accessibility regulations and standards. It's a great material for all of you who want to understand more about the global digital accessibility landscape. And again, you can take out your phone and scan the QR code to get a direct link to the webinar recording. The second webinar, which I think is great for all of our customers, is the webinar explaining why accessibility is a competitive advantage. How it boosts SEO and conversions. So I think for many of us, accessibility is often associated with inclusion. However, there are direct bottom line benefits of having accessible sites and tools. So I would really encourage you to learn from our experts and review this webinar as well. So I will give you a moment to access the links if this is of interest to you. Great. Let's move on. Now, let's shift gears and look ahead to 2025. This is where the things get really exciting. Our strategy for next year is built around two main key ideas. Making all of the DTM insights more actionable and making sure that we give you a variety of ways to accelerate issue resolution and improve tasks prioritization. A few features which will greatly contribute to this goal is scanning behind JavaScript logins, something that our customers have been really looking forward to. Improving benchmarking scores so that you better understand where you're at with accessibility and quality. Upcoming new AI-driven features. So AI-driven insights, which I will talk a bit more about on coming slides. And AI-driven fixed suggestions, which will allow you to harness the power of AI to solve your issues faster. So looking at the snapshot of what's coming in the first half of next year, we are working hard behind the scenes to bring you AI executive summary. This will allow you to understand at a quick glance what's happening on your dashboards and in your groups without diving deep into the numbers of issues. We are also looking at updating the benchmarking scores to make them more transparent. And at enabling scanning behind logins, which I will also talk more about in a second. Moving on to the second half of 2025, let's look at how AI-generated insights, including the executive summary, would help you solve issues faster and be more effective. We're looking at potentially providing a summary of issues, which will highlight key categories in which our site needs improvement. We are definitely seeing great value in providing an executive summary. We're also looking at the ability to use the AI-driven insights, which will allow you to understand the changes that you can use within your organization, and understand at a quick glance what's happening on your sites, and what's driving the changes. And additionally, we believe that understanding more critical actions will help you improve your templates to prevent introducing accessibility issues to your sites. So the third step that we're looking at, as we're discussing the AI-generated insights, is scanning behind logins. So what we'll provide is the ability to scan behind JavaScript logins, which includes handling simple form authentication, dismiss cookie banners, and handle edge verification gates. So that will enable our customers to add even more dashboards and even more sites to their DQM instances, and in turn make their sites even more high quality and accessible. And this feature is scheduled for launch in second quarter of 2025. And when it comes to the second half of next year, we are looking at additional AI-driven features, which could include AI suggestions. There is definitely a value of providing AI-generated suggestions, and giving your team's ability to utilize those for a quicker issue resolution. We've also heard you all, all of you who were asking for new exports, and this is definitely something which will be coming in second half of next year. And just to make sure that you're aware that we are always listening to the feedback which our customers are providing. That's why we always keep some capacity within our teams for any features that are being requested via our portal. So for those of you who are not yet aware, early last year, we have launched our portal. So this is how we call our external roadmap, where our customers can view details of any features which are under considerations, which can be scanned and launched. On this page, you have ability to vote on those specific cards and provide your feedback. And I would really, really encourage you to do so. This is just an example of the cards which I have added to the roadmap regarding our Jira integration. Because for the future, we are considering allowing for creation of a Jira ticket for multiple checkpoints on a single page. That's one of the possibilities in the direction that the DQM Jira integration can go, or maybe updating Jira tickets based on the two-way communication. So definitely please take the opportunity to have your say and vote on the features which would add most value to you and your team. Now, I will enable a survey where you can share very quick thoughts on what features are you looking forward to the most in 2025. Thank you. All right. Thank you for your answers. And let's move on to the next slide. I heard that everyone is very curious and wants to know more about the benchmarking scores. So let's have a look at some of the information that all of you will find very valuable. So our benchmarking scores, as probably you know, range from 0 to 10 and are based on the number of issues in relevant benchmarking checkpoints. The scores reflect the overall quality and compliance of pages in specific categories. Some of the checkpoints carry more weight, are weighted more heavily than others. So the calculation is not linear. But by fixing all of the issues of a benchmarking checkpoint for a page, your score will increase. It is also very important to note that if a page contains one or multiple occurrence of a checkpoint issue on a page, for example, if you have more than one image on a page that is missing alternative text, it will count as one issue, which means that this page fails this checkpoint. The issue will only be resolved once all of the issues for this checkpoint are solved. And the issues that you find on this page are fixed. This helps to drive action to fix all the issues on the page and to ultimately be more, be fully accessible and have higher quality of the pages. Our product team is currently in the process of reassessing our benchmarking checkpoints and formula. So as I mentioned, there will be changes to the benchmarking scores in the future. And additionally, any benchmarking checkpoints and formulas are subject to routine review. So they are regularly reassessed by our experts to align with industry standards in terms of accessibility, SEO and usability. And of course, we want to make sure that we bring for you clear guidance for how specific issues affect benchmarking scores. And the changes are coming in the first half of next year, as I mentioned. I will now move back to DQM to show you a quick demo of some additional features that you might not necessarily be aware of. Right. So you are probably used to reviewing the benchmarking scores on the group overview page. And this is correct because this information is not currently available on the website overview page. However, there is a way to view the benchmarking scores for specific websites. So here you can see that I'm viewing the benchmarking score for all websites. However, I can have a look at a specific group of websites. So the benchmarking scores will be adjusted to only take those specific websites in this group into consideration. If I navigate back to the website overview, you can see that there is no benchmarking score here, which might change in the future. However, to view the benchmarking score for your specific page, you can navigate to the website leaderboard and view the benchmarking score in the specific column, depending on which benchmarking score you want to use. So you can see that the benchmarking score is of interest to you. As you are probably aware, any score above eight is highlighted as green. This is something that obviously we are all striving for. Anything between five and eight will be marked as amber, which indicates that there is still some work to be done in this area on this page. And anything below five will be marked as red, which indicates that there is probably a lot of work to be done. If you are quite surprised to see the number zero and no rank for your page, it probably means that the scan has failed. Likely the starting URL of the scan was no longer working or no longer accessible. So this is definitely a prompt for you to reach out to your internal teams or Crown Peak support to understand why this specific page was not scanned. I will also mention that this score includes both public and restricted checkpoints. So if the term restricted checkpoint doesn't seem familiar to you, I would definitely encourage you to have a look at our Crown Peak community. So this can be accessed under community.crownpeak.com. And here you can find very relevant information, very valuable information if there are some features of the QM that you are not sure about. And if restricted checkpoint is something that you're not aware of, then I would strongly encourage you to have a look at the information here. This is the type of checkpoint that could be very useful to your organization. So if you want to introduce different levels of priority, we all know about priority checkpoints. However, if there are checkpoints which don't seem very relevant to your organization right now, they can be classed as restricted. So they will not be shown to the majority of users, but they can focus on the key checkpoints. However, both public and restricted checkpoints will be considered in the benchmarking. So yeah, if the term of restricted checkpoints is something that you're not familiar with, it's worth speaking to your DQM admin or contact our Crown Peak support. And of course, we have three types of scores available. Accessibility, SEO, and usability. Majority of our customers are indeed interested in accessibility. However, SEO and usability are also key priorities for them. That's why keeping track of the scores is very, very helpful. For a spotlight on accessibility score, I would encourage you to go to the accessibility page under Website Insights or under Group Performance, where you can dive deeper into your accessibility score. And how you are performing when it comes to the regulations. In terms of SEO, there's also a dedicated page for SEO checkpoints. And what's extremely useful here is the very simple sign benchmark, which means that this checkpoint is contributing to your benchmarking score. So we are aiming to introduce a similar type of indication for the rest of the checkpoints, scores, flexibility, and usability as well. So that all our customers are clear which checkpoints contribute to the benchmark and how. Now, we also had your feedback that you want to find out more about the best practice in DQM. And something very interesting that the team has been working on is giving you more advice on how to start solving more issues. So if this is the question that you are asking yourself, then I would encourage you to navigate to this page. The page that's available under this QR code is a page in our community, which highlights more information and tips on how you can start solving issues in DQM if you are a new user or if you haven't been using DQM for a long time and it's not very clear to you where you should start. So this is just a snapshot. Snapshot from the guide, which we have launched this month. And I would encourage all of you to review the information so that you can make the most of your DQM tool. And before we conclude the session, I would love to ask you a few more questions around how did you enjoy the session and what would be most useful in the upcoming sessions. You should now be able to see a poll with feedback for this session. Thank you. As we wrap up the session, I just wanted to say thank you to all of you. Your partnership and feedback are what drive us to keep improving. And together we are building a platform that makes digital quality and accessibility management easier, faster, and more effective. If you have any questions about what we have covered today or want to dive deeper into a specific topic, do not hesitate to reach out. And me and the team are here to help. I look forward to seeing you in the next office hour. This session will be recorded and distributed to all of the participants and those who signed up. So you're definitely welcome to catch up or any bits and information which you will find useful in the future. Yeah, I look forward to seeing you in the next office hour. Thank you so much.