Simplify accessibility with AI: Webinar for Developers & Product teams

Welcome and Introductions

Sapir: Hi everyone. Thank you so much for joining us today. We’re excited to introduce you to this webinar from accessiBe: from backlog to release, simplify accessibility with AI. We’re going to jump into a lot of topics today. And this is really dedicated to dev team leaders and product leaders and anyone really who’s touching accessibility at their organization and hoping to bring accessibility closer to their digital products. So our agenda for today is to briefly introduce ourselves, then talk about accessibility briefly before we get into the developer’s dilemma.

What’s holding accessibility back for developers and product teams? Why is this being stalled? What can we do about it? Then my colleague will share accessFlow, our accessibility management platform, in real time, along with the MCP, which is very exciting. Feel free to add your questions in the chat at any time. We’ll be here to answer them. We’ll dedicate time at the end. And we’re really looking forward to this session and bringing more of this information closer to you. So, without further ado, I’ll introduce myself. My name is Sapir Yarden. I am part of accessiBe’s marketing team.

I’ve been with the company for over four years. I have been in a few different roles here, but I’m really excited to be part of this organization and the work that we do. Especially in my role with the community, I focus on partnerships and ensuring that the products we build are actually impacting end users and that we get feedback from them to continuously improve. And I’m really excited for my colleague here to introduce himself, so I’ll hand it over to him.

Jason: Hey, everyone. My name is Jason. Before I actually worked at accessiBe, I was a teacher for children with special needs. So this kind of actually molded how I actually decided to work with the community, and that kind of is what brought me here. So in that process, I started at the ground level, working with the support teams and actually understanding how our customers really felt about accessibility and actually trying to help them along through their journey.

And nowadays, I’m an automation engineer, directly working with the accessFlow product, interacting with it daily, and starting to build something truly great here.

Sapir: Thanks, Jason. And we’ve been at the company for some time now, and we’ve had the opportunity to work across departments but also together, delivering accessFlow to different types of customers.

And what’s been really interesting about our collaboration and how we work as a company is also the ability to get customer feedback so that we can add new features and make sure that the product is really working for any sort of use case, and you’ll see that as we go on with the webinar. So we’ll talk briefly about why we’re here today: digital accessibility and bringing accessibility closer to your organizations. So, when we’re talking about what web accessibility is, it really is about making your digital assets accessible for everyone, including and maybe also especially for the disability community.

In the image here, you can see my colleague Josh Basile. He’s a C4-5 quadriplegic. He was voted onto the Forbes 100 list for accessibility, which was the first time the list went live, as one of the biggest advocates of accessibility in the US in the past year. And really, this is his setup at home. I took this picture of all of the different screens and technologies that he’s using to navigate the web. So that could be the click stick that he’s using with his mouth to navigate different elements.

It could be the onscreen keyboard, or it could be the screen reader he’s using, just to hear all the different elements. And the way that he navigates is truly amazing. And that’s really what this all is about, making sure that anyone has the ability to reach every single element on the page to navigate freely through the content that your organization is trying to share.

So, that’s a little bit about the background to what we do as an organization, but where this stems from and maybe where you’re coming from in this conversation, where your business is coming from, is the compliance angle and making sure that you’re up to standards with the latest regulations. So there are global regulations. In the US, that might be the Americans with Disabilities Act, which went into effect in 1990 but didn’t mention websites at the time. So we’re just catching up to that now. There are regulations in Canada and, most recently, in Europe, where the European Accessibility Act came into effect in June of 2025.

And all of these different regulations adhere to the WCAG, the web content accessibility guidelines, which is essentially a guidebook for how websites can be perceivable, operable, understandable, and robust for people with disabilities to navigate your websites. So these are the standards also that our accessibility engine and all of our solutions are adapted to to make sure that the websites that you’re building are going to be accessible to that standard. and compliant with the relevant laws, which is why we’ve built the platform Accessibe has today.

So we have several different solutions, and what we’ve become famous for, or known for, is accessWidget, which is the AI-powered on-demand solution that you’ll see on a lot of websites when you see that little widget on the website, and you can make those adjustments in real time. But what we’re here to talk about today is the dev tools that can help you make sure that you’re delivering real-time, accessible experiences.

And we also have a services team that provides professional services if you have downloadable files that need remediation, videos that need captions, or any audits or VPATs of the sort. If anyone here is interested in more of those compliance elements, feel free to add that in the chat as well, and we’ll get back to you.

But all of these different platforms help you on your accessibility journey, making sure that everything that you’re doing at your organization is going to be at the level that you want to be at, at the highest level that you want to be at. And that’s why we’re excited to talk about access flow today, because this is really going to be core to your needs. As I mentioned before, feel free to add your questions to the chat as they come up, and we’ll make sure to answer them during the Q&A.

The Developer Dilemma

But in my time at accessiBe, and Jason, I’d love for you to jump in in a moment, but in my time at AccessBity, I’ve had a lot of different conversations with developers and product teams and people who touch websites. And they might be experts in this, and they might not, but what has come to my attention is that accessibility is really difficult to prioritize. It’s still sort of niche in the world of building websites. Even though we’ve been talking about it, at least at our organization, for quite some time. So it usually happens at the end of the product cycle. And then that’s when issues surface.

So it could be too late. You have to go back and do rework. If you have multiple products or if there are different teams working on different websites or elements or digital assets, then testing can also be disconnected and happen at different times. And ultimately, there are not many organizations, at least in the growing market segment. So maybe in the biggest companies they do have accessibility teams, but not every single company has an accessibility person on demand who has specialized knowledge to make sure that elements are accessible, and I wanted to hear what your thoughts are, Jason, on this particular dilemma.

Jasson: You’re very right about this, actually.

So, like, the common thread about all this is, like, friction, because in each aspect, actually, as we’re working with devs as QA, devs, product, and design, we actually realize that the hardest point is that we’re trying to push things quickly. But the thing is, everything related to accessibility ends up in the backlog because it’s actually super hard to prioritize. It requires a lot of diligence and has actionable items, but it’s really hard to manage.

So what we’re trying to fix here is actually to make this actual flow a lot smoother and actually give us a way to actually test things in advance, catch issues early, and be very proactive about our approach to dealing with this particular dilemma.

Sapir: So, having heard all of these different elements of the developer dilemma or the challenges that developers might face when building products and then reaching accessibility, ultimately, accessFlow is here to provide value, right? It’s here to help with some immediate needs.

Why do you think things get stuck with accessibility? because because it’s super hard to prioritize like like as we said before like it’s it’s something that like kind of like it’s so niche that we don’t really know how to manage it and it’s like something that’s not part of the common workflow but like if we can make it something that’s actually in our existing workflow then it’s a way to kind of actually help us move it forward you know so that’s that’s our goal you know yeah

Introducing accessFlow

Sapir: Exactly, well, you lined that up perfectly for my next slide, which is let’s take control with accessFlow and I’d love for you to maybe tell us a little bit more about the product and your experience, because you’ve really been at the company since the onset of this product development and where it’s at now. So, can you tell us a little bit about how accessFlow works? Yeah.

Jason: So, it’s been some time since I’ve been here, but like definitely I saw this product actually grow from like something that was actually like pretty small workable, but then seeing how our our customers, the people that we worked with actually they actually gave their input and actually figured out what what actually like worked for them and we actually also added our input and pretty much it helped us build a wonderful product. So, right now, like, the way the product works is that we audit your website.

You actually input your website, and then we actually scan all the pages that you actually like are allowed in your quota. Once we do that, you actually have all your data immediately, like everything is actually there.

And then, pretty much, we actually offer quick solutions for all the information, like for each issue. You see actual data that is actionable and allows us to fix the issues, specifically whenever we want. It provides instant value whenever you need it. And then, aside from that, actually, it allows us to actually so once we actually allow you to actually fix everything- then you’re able to actually maintain, like, all the issues with periodic scanning, and actually you have, like, all the monitoring that you need, and it also integrates with, like, a lot of your external tools.

So allows us to kind of like make sure that it’s part of your existing workflow. So this is actually the thing, like, you maintain this project as you move forward, you know. I like that, and it’ll become a lot more tangible once we jump into the demo as well, because I’m already visualizing a lot of the elements for myself. But what I think is really cool is that you input the website into the platform.

It scans the platform. It tells you what you need to fix, and then you’re pretty much smooth sailing there, and you’re in control of when you scan, how frequently you scan, when you make the changes, and how many changes you make at a single point in time. And it’s just a really cool product to see in real time. So, without further ado, Jason, your turn to share the screen.

Jason: Yeah, I’m going to share now. Okay.

accessFlow Platform Demonstration

All right. So now we have this as the platform. Okay. So this is actually the dashboard view. So right here we have a view of unique issues. Okay. So this is actually your complete website overview. So here you can see the website URL in the top corner, and then here you can see details about the existing unique issues. Okay. So, in general, we categorize issues as unique one-offs. Things that happen actually on a single page across time, and then we have recurring issues that happen across your entire website. You also have your audited pages.

So these are the pages on your website based on the scan quota. Here you could also see your audit cycle and actually like all the actual data, like actually like when your last audit happened, and then also when your upcoming audit is happening, which is also like you could actually get it changeable like based on your plan. Then you also have website assets. Assets are the products that are pretty much any external file that you could remediate or anything like that that happens to be asked for, but I’ll get on that a bit later. Here you have a view of

Sapir: Can I ask a quick question? Yeah. What are the different audit cycles? It says weekly.

Jason: Yeah. So, what are the different options? Yeah. So the options are actually weekly. We have a monthly cycle, a bi-weekly cycle, and an API you can trigger on demand for your entire site, which is part of a separate plan. And just for clarification, the website assets you mentioned are downloadable files.

So those would be like the PDFs or video files that you might need remediated separately, because, yeah, so PDF, audio, anything that actually is an external asset that actually requires a download and may not be accessible, we actually put these into this section, and then you could actually work with our manual services team to actually get them remediated. Cool. Thank you. Also, this view shows you anything that happened on your website throughout the scan. So, like, if there were any loading issues throughout, like specific pages, so you could see any issues that were there.

Also, we provide all the analytics you need to track your accessibility journey. So, for example, actually, you could track your score over time. Here you have filters to actually track, like, over the last 12 months, and then you can also see it, like, historically through here as well. So this actually is a way to actually make sure that you’re making the progress that you need and actually also so you can show it to shareholders to actually make sure that they actually are getting the true picture of what you’re really looking for.

Sapir: At our company All Hands last week, we had a customer who uses accessFlow demonstrate how they use the score to report to leadership about all of the changes that they’re making on their end and the effectiveness of accessFlow in helping to add value for those conversations. So they’re saying, “Hey, here’s the progress we’ve made on accessibility over this amount of time.” Yeah. Exa Exactly. So this is actually a view to get the breakdown of your entire website’s journey. Now, moving to the explore page, like how we actually work with the platform. Okay. So this is our explore view.

This actually gives you your workflow here. So this actually gives you details on all the issues occurring across your entire website. So here you can actually look at a specific issue.

Jason: So like for example I’ll go into this issue field label and here we show a issue description which actually gives you the the actual title of the issue a way that you could track it if you actually decide to export it into a external ticketing system which I’ll go over later and also you get the descriptions here you get actually any information that you need to actually understand why this issue is happening how you made this actual this accessibility error and then also So it it provides you your source code and also your your suggested fix here. not to forget we also like actually give you a link to the WCAG criteria so you could actually follow it and actually understand even deeper why this issue happened and ways to prevent it in the future.

So, like, our platform is really meant to actually inform you how to actually, like, kind of work with accessibility in an ongoing way. That’s really cool from the perspective that not everyone has an accessibility expert on their team or on demand, but you get the code issue, the fix, and the explanation of why that needs to happen. Yeah. Yeah. It’s powerful stuff when you actually work with it in tandem with everything. So this also gives you an issue selector and the web page on which it appeared.

So you can actually track it to understand exactly where it occurred and how to resolve it. This is actually the view of a unique issue. I’ll go into one of the recurring issues here. So, like, a recurring issue is also, as I explained before, an issue that appears on multiple web pages. So it gives you the same view here, but you could also track any page that it appeared on throughout your website. So this is also a way to make sure you keep it resolved within the entire application. So

Sapir: I was just about to ask you about that, and then I saw another thing I wanted to ask you about, which is the team comments at the top.

Jason: Yeah, we have a team comment section that lets you interact with your team members. So you could actually

Team Collaboration and Issue Management

Okay. So, we have a full suite of actual team collaboration tools that allow you to actually assign issues to your teammates. So, you could actually get them to work on specific issues. It appears in the remuneration table here, and then you could also mark them. Yeah. So, like, it sends them a notification so they understand that they have to work on it. You could also comment on them. You could also mention them; make sure that they’re aware of what they actually have to do.

And you could split the tasks across your entire dev team to make sure everyone’s working on specific things and knows what they’re working on. We also have filters for this, so you can actually now filter your entire table. So, for example, the assigned issue, like appearance, is actually here for the specific user. So each user who actually logs in to the platform can manage their work. Okay. Users can have access. So we have, like, unlimited users, but it also depends on the plan.

So, like, the enterprise plan is unlimited users, but, like, actually, lower tiers- like, we actually have, for like, three users, we have 10 users- like, yeah. So you could, like, be tailored to your needs, kind of in a sense. So if you need more users, like, it’s always something that we’re willing to actually help you out with. So, like our table here, you could actually filter by issue type, filter by assignee.

You have all the filters and sorting capabilities you would need for a table like this. And yeah, it helps you kind of move forward with your accessibility project and streamline your workflow. Here we have another view of the actual issues, but by the rule. So you could actually view each issue type, but only at a more granular level. If you want to work on a specific issue that’s happening across your website, you could actually do it. We have the definitions of everything.

You could also export your issues here, like the entire list of that specific issue, to a JSON, and then get it, and then actually import it into your ticketing system. And yeah, it’s another way to work with your actual website and the accessibility issues that come up along the way. Here we also have web pages. So the web page view is actually pretty much like this; it’s also another way that allows us to kind of navigate how we want to work with our accessibility issues.

So, if you want to track a specific page, you can track it and follow all the issues that occur on it. You have all the occurrences. It’s a different view to actually navigate and actually manage our issues. We also have a visualization tool that lets you see the website pretty much as it happens, as issues arise. So it’s a way to work with our accessibility platform, with a visual indication of what’s happening. It’s super powerful, actually, here, and you also have all the capabilities that I mentioned before.

That’s cool as well. Here, like, I also want to go into the exporting function. So we also have, like, the ability to export issues in the information panel. Okay. So you could actually export to any ticketing system we’ve set up here. So I’ll show you this list here. We have these, and you can export an accessibility issue there, then track it through your own ticketing systems and manage it within your existing workflow. So you could actually make this a project that you could actually manage, and pretty much everyone who touches it has full visibility into it. Okay.

Testing User Journeys

I also want to go into the journeys tool. The journey tool is actually a tool that allows us to record a user journey. So, like, let’s say our common user journeys are adding something to a cart, inputting something into a form field. Actually, this is a tool to track accessibility issues throughout these projects. So, for example, I could actually show you here. Hold on, give me one second. I could actually show you how this looks. So we have a tool that lets you record your user journey. So this actually records your actions.

We actually have it here in our step timeline, and then we could actually now follow any issue that is happening. So, for example, I clicked this page, and I went into this view. I want to go to this link for failure examples. And now I want to end the recording because I actually did this journey. So we actually gather all the recorded steps, and you could actually tailor this. So, what this is actually showing you is the accessibility issues occurring in the specific user journey.

So it allows you to actually track all these workflows that the user has that may actually become an issue.

Sapir: That is such a powerful tool because I’m thinking about a webinar that we recently did about e-commerce and we found I I’m not sure if our guests here today are from the e-commerce space but we found that 40% of people that we surveyed about e-commerce trends did not complete a checkout audit or an audit of their checkout journey on the website within the last year and they had the of the survey respondents there was a 72% confidence rate that their checkout was working well. And on top of that, we know there’s about $260 billion in losses from cart abandonment worldwide.

So if you’re thinking about $260 billion being lost, and 72% of people feel confident about their checkout journey, but only 40% have audited it. If they had access to this tool, where you can just record very simply, I’m thinking anyone could record a journey on the website and then share it with the dev team, so they automatically get those issues.

Am I correct in assuming that, like any, yeah, it provides instant value, like you actually are able to, like, validate an entire checkout flow and then understand exactly what issues may have arisen in this checkout flow? Like, yeah, it’s super powerful when we actually work with it this way, actually. So yeah, these are the issues that arise from this journey here. So, they just add on to the previous issues. It’s actually separated. So, you actually have a separate list of issues for a specific journey. So, like, this journey triggered this many issues.

So, like, it’s actually a way to kind of like make sure that you can actually really lock down your checkout flows or lock down your search inputs. So this was actually going through a search field, checking the search input data, and then moving through those tabs to get to the solution. So yeah, it’s a really powerful tool if you want to actually lock down your specific user flows. It’s great. It’s great.

Prioritizing and Auto-Resolving Issues

Sapir: One last question, because we didn’t touch on it, and it’s probably my favorite feature: the severity.

Jason: Ah, yes, yes. So, like, issues are also filtered by severity. You could actually know what issue to work on specifically. So if you want to handle your most extreme issues, you could now filter your tables by severity and tailor your workflow to, say, let’s deal with all the extreme issues, and then, pretty much from there, we’ll move on to medium and high issues.

Like, it’s a great way for us to work through this whole accessibility project because it’s a little daunting when you get a bunch of issues. But if you start to separate them by severity, it makes it a lot more actionable. Well, I’m just thinking I’m not very technical. I don’t work on the R&D side of the company at all, and seeing that list of issues was making me stressed out. Yeah.

So if there’s a way to prioritize and see how I can consolidate some of the work, and then also knowing that I can integrate it into my own systems or assign other teammates to work on specific projects, so it’s not just sitting with one person, but rather it’s a team effort to make that website or that asset accessible. Yeah. Yeah. It’s such an amazing way to actually work with the platform. Here we also have the WCAG filters, actually.

So you can filter by any WCAG level we have here, which also lets you work with the platform that way. If you want to make sure you reach this level of compliance, this is a way to address it as well. I’m also going to move on.

Sapir: Last question. Sorry. no. Oh, what’s that? Yeah. Okay. So, I was going to get to that in a few, but maybe I’ll touch on that now. I’ll stop interfering. I just- I’m It’s an exciting product. Oh, it really is here, actually. So, okay. So, maybe I’ll touch on that now. Autoresolvable. Okay. So, you see the issues here with this indication. These are issues that are eligible for Auto-Resolve.

So these are actual; auto-resolve is a feature on the side panel that allows us to pretty much resolve issues automatically. You could actually install a script that actually, so, like, for example, this is actually the view, but I could show you how it would look actually with the actual view. So, pretty much, Auto-Resolve is a feature that lets us resolve issues immediately in your page session using a script. So it’s kind of like you could target a specific issue and then just resolve it instantly.

So, like, I’ll kind of give you a show on that. okay. So first, we verify whether the script is installed on your website. We actually first want to make sure that your website has these installed. And then you could follow this link to track the eligible issues for Auto-Resolve. And this shows you a list of the issues, the same list from our explore page, but just filtered by the autoresolvable issues.

So like, now we could actually pretty much just manage this like cuz if we want to actually not have to resolve like issues at a specific time like like mainly like if we want to actually deal with the accessibility issues later we we could actually just get our instant coverage and and make sure that we’re actually covered while we actually work on like other issues. So this is a way to kind of like deal with this flow. So you could also kind of like go ahead.

I also did mention that we actually have batch actions you could do here, but, like, here you could go ahead and just Auto-Resolve these issues. It’ll actually apply the actual fix on the page for that session. Okay. So it’s like a real time saver. Yeah. Yeah. It’s a real time saver, like the way this works actually. Like, it’s pretty impressive, actually. Pretty impressive. yeah.

Using the accessFlow MCP

Sapir: Are you ready to jump into the MCP, or is there anything else you want to share?

Jason: Oh, I actually- maybe I just touched on the integrations, just kind of a quick view of the assets page. This is actually a page that I mentioned before, just so you get a view of it. Like all the files, you could actually send it to our services team and actually manage it there. And then also, yeah, now we can just jump into the MCP. So the MCP is actually a tool that allows us to work. Okay. So, like, our goal is to make sure you can deal with accessibility issues before you push it to production. Okay.

So the way we manage that is by using a token system that lets you create a token for our MCP and work directly in your IDE. So you actually could use either a cursor or a co-pilot. Any agentic workflow, including those that are MCP-compatible, allows you to work with our tool here. So you just need to make a minor configuration here, and you’ll have access to a few tools we offer. So it gets the most urgent issues.

So, for example, I could kind of show you how that works here. Let’s fetch the most urgent accessibility issues, so, for example, I can actually fetch the list of the most urgent accessibility issues. This is actually now working with our platform in your IDE. So you’re able to actually gather the issues, though it takes a little while because things sometimes take a while to load, and you have a lot of accessibility issues. Yeah, exactly. This is absolutely true. So, it’s now fetching the urgent issues. Oh, I think it stopped. Okay, it’s gone. Still moving. It’s still moving.

Let me zoom in here so you guys can kind of get a view there. Yes, it’s working with the server. Oh, yeah. It’s working really slowly today. It happens. You know, only on a video demonstration do these things happen. Well, this is a good opportunity to say that if anyone has questions, they can add them in the chat. So, when we’re done with the demo, we’ll be able to answer their questions and make sure you get value from this webinar as well. Okay.

So, instead of waiting for it, maybe I’ll just show you the output, actually, because this is taking a while. So, like, the output of this is actually that it gathers the issues that happen across your website, the most urgent, and then you can actually navigate to the issue. So it gives you the issue, the severity, and actually pretty much everything you see on the platform, but with the context of your code. So what you could actually do here- yeah, this is actually working super slow. So what you could do here is actually, like, for example, let me see something.

For example, you could select a specific issue. So I’m going to choose this one, the button rolls, and I’ll just say here, hey, so let me just do this fetch issue using so I’m going to fetch the issue using the access MCP- yeah, so I’m fetching this specific issue that actually was actually like in the list using the accessible MCP. okay. Great, great, great. It’s using the tool. Hey, there you go. There you go. Hey. All right, great. Okay, so it’s actually now fetching the specific issue. It’s actually giving us all the details.

So, I could actually also move this to the side so you can kind of see. So it actually gives you all the details of the specific issue. And then now I want to actually, so like, you could also locate the issue inside of your browser here. So, for example, if I wanted to open this issue for one second, if I wanted to open the issue just for visibility. Yeah, that’s it right there. I can actually identify the specific issue on my website and then work on it in my IDE. So, like, let’s say, pretty much, we could actually apply the fix now.

Okay. So when I apply this, I want to apply the suggested fix. So it uses another one of the tools that’s actually to get the specific issue, and then it applies the specific fix to the issue we had going on here. Like, it also tracks the issue because it may not have said it; as the occurrences happen, it tells you the page the issue occurred on.

So you could actually now so like any any instance of this within your code it’s going to apply a fix to. So yeah, it’s actually now computing on what it should do. It’s actually seeing where it should apply it. So this is actually good because it’s actually tracking the exact issue. it was with a success component and trying to add the roll button here. Okay. Okay. Yeah, because there are a couple of elements it needs to apply to. So, it takes a little while, and I think my computer’s just particularly slow at this moment. But, yeah. So, now, okay. Yeah.

So, this is kind of for demo purposes; I could show you how the fix works. So yeah. So, like, pretty much this is an example that I actually did a fix for a specific issue. I applied the fixes, and then it actually created a to-do list of the issues and then actually applied the relevant fix to the code. So it’s a way we could actually work with this tool seamlessly inside the code editor.

I wish it would show you seamlessly now, but hey, this is how it is. But yeah, this is the MCP tool. And now you could also use another tool to resolve the issue in AccessFlow. So you could communicate back to accessFlow to let our platform know you resolved this issue. Okay. So what would be the difference between using this MCP versus another co-pilot? Oh, great question. So, pretty much, the thing about this MCP is that it lets you interact with our entire ex accessibility back end, and it has a lot of accessibility context.

So it allows you to pretty much make more informed decisions now using our own accessibility library and everything we’ve sourced over the years. So it’s like super powerful in that sense, actually, like the patented research of the widget and the engine. Cool. Awesome. Yeah. Yeah. It’s super powerful, actually. And before we move on, just one last chance for people to add questions to the chat while we share some final thoughts about the webinar. Okay, Jason, I’m going to take over the screen share if that’s okay with you. 

So, just closing out the webinar today, what I understood, and hopefully this is what we were both trying to communicate- so hold me accountable here- is that you don’t need to be an accessibility expert. So that’s a question of technical debt, meaning maybe not everyone at your organization could be using it because it does seem to be pretty technical, but for developers and product leaders, it could be a very helpful tool in terms of streamlining processes, reducing the amount of time for workarounds, or coming back to projects because you’re really integrating it into the workflow.

And then you can also automatically, or with the click of a few buttons, make some code suggestions to the source code. Is that accurate? Yeah, it’s very accurate. It’s no, it’s from an engineering perspective, it’s actually like about actually being in control of your accessibility project and actually managing this with your team, actually, because you don’t actually have to context switch, actually, and it’s actually just kind of making this a cohesive workflow for accessibility teams. Well, for just development teams without having to specialize in accessibility, you know.

Sapir: Okay. So, some of the use cases I’ve seen with customers who have used accessFlow include a website rebrand or starting a new business, and they want to make sure everything is accessible from the ground up. But what are some other use cases for accessFlow? When would someone want to use this solution?

Jason: So, like, it’s actually perfect to use in your existing accessibility projects- like, I mean your existing projects- like, so like you want to actually make sure that your website is actually compliant. For example, let’s say you have a new promotion on your e-commerce website; you want to make sure everything tailored to this promotion is accessible. So you could use this to ensure your flows are compliant and pretty much navigate the way a screen reader user or keyboard-only user would on your website.

So it’s like, yeah, there are many ways that you can kind of like really tailor these flows, actually. Yeah. And how soon would someone be able to see the value of that? Oh, immediately. Like you, you really actually get the value from the first scan. So as soon as you scan the website, you get instant value by seeing all your pages. You can also use the Auto-Resolve tool to address a certain number of issues immediately, then start working from there.

Audience Q&A

Sapir: We also got our first question from the audience. Thanks, Ruben. So could you clarify what the data source is being used to identify, prioritize, and remediate the issues?

Jason: Yeah. So, so we actually pretty much organized the issues by severity like actually using the WCAG standards and actually just all and also using actually like if I’m actually hearing the issue correctly like we’re actually pretty much sourcing all of our data from pretty much our backend which is actually based off of accessibility best practices and standards and we actually use these as ways to resolve issues and also identify what’s the most what’s the most severe and the most like what actually is the breaking changes on your website pretty much that’s the way that we kind of like

Sapir: So a combination of WCAG guidelines, accessibility best practices from the company’s own accessibility engine, industry standards, and then what I really love- and this is my little marketing sticktick here- but what I really love about the way that we work is also really much tying back to the community. So we’ve had a few different experiences of working with disability focused nonprofits, and we also have a team that works closely with our product department called Access Labs, and it’s a group of blind usability testers who go in and make sure that our products are working effectively and that we’re aligned with those WCAG standards.

So it really ties back to that and it’s super important that we’re not working in silos but rather both Jason and I have had have had conversations with the community have heard feedback and as Jason said at the beginning of the call many of our customers have given feedback about the pro about accessFlow over the past couple years that we’ve been developing this and some of the features that we’ve built have been as a result of feedback that we’ve received. I think there are a couple that you’ve mentioned to me before that were direct feedback. Do you recall which ones those were?

Jason: For some of the ticketing system integrations, we actually made sure we got specific platforms; aside from the most common, we started supporting more of those, and some of the batch actions and things like that actually make a workflow a lot smoother. These are actual tools that we actually generated because of our users. So, we’re really open to that.

Sapir: Cool. Thank you for all of that. I’ll give it one more, you know, like a few more seconds to see if anyone has any questions, but as a last question from me to you, what do you want people who join today’s session to walk away with from accessFlow? What do you think is like the number one thing that they need to know if they’re taking this information back to their teams?

Jason: Good question. Honestly, that accessibility doesn’t have to be a long-winded journey. It’s something that you could actually build into your daily workflow, and it’s something that, like, we’re all trying to get better at, you know; we’re all working at it. And I think that work is the most important thing. And with a platform that actually lets you prioritize everything and, like, kind of make accessibility a natural progression of your project. It’s something that is powerful. So yeah, it’s worth trying out, you know. That’s awesome. And people can get started today with a free trial.

Absolutely. Just remember that, like you, you can go ahead and actually sign up, like it’s actually completely, like, free, and you get to try the platform yourself just to actually get the insight.

Closing Remarks

Sapir: Awesome. Well, thank you so much for your time, Jason, for joining this. Thank you to everyone who is part of this conversation. We hope you got some value from it and that you’re energized to take accessibility best practices back to your team. And we’ll catch you at the next webinar, or feel free to reach out, and we’d be happy to do a live demo for you and answer additional questions. Thank you all. Have a good one. Bye.