Design without compromise: Stunning design that is built for everyone

Welcome and Introductions

Josh: Welcome, everyone. My name is Josh Basile, and I’m the Community Relations Manager at accessiBe. Today, we’re going to bust the myth that accessible design can’t also be stunning design because it absolutely can. Accessibility and creativity aren’t at odds. They’re actually partners. We’re here to reframe how you think about accessible design. It’s not about perfection. It’s about being intentional, inclusive, and just starting. We’ll get things going. It’s all about being simple, practical, and doable. The big takeaway really is accessibility isn’t just the right thing to do. It’s about smart business.

It opens your digital doors to more people, strengthens your brand, and ultimately improves your product for everyone. So, let’s jump into it. I’ll ask Haim to introduce himself, and then I’ll share my own journey, and let’s make this happen.

Haim: Hey, thank you very much, Josh. Indeed. Let’s make this happen. It’s great to see everyone, and it’s wonderful to have so many people joining us. Hi, everyone. I’m Haim, the VP of Design here at accessiBe. I’ve been with the company for the past five and a half years. My mission as well as our mission is to help you guys create stunning designs while keeping them available and accessible to everyone. Thank you.

Josh: So my journey started about 20 years ago. I was in waist high water as a teenager. This was back in 2004. I was in the ocean. A wave picked me up, threw me over my boogie board, and slammed me head first against the ocean floor. And that day I heard a loud crack. I was immediately paralyzed below my shoulders, unable to move, unable to turn myself or scream for help. Thankfully, my friends saw me floating. They pulled me to shore. I had to hit a big reset button on life.

When I did, I ended up coming home. Always had a goal of being employed someday. So, I went to community college and then completed my undergraduate degree at the University of Maryland and then graduated magna cum laude from law school. I did that through helpful hands, through incredible technology and just a focus. But you know, for the last decade, I’ve been a trial attorney, a consultant, run a nonprofit, and do everything I can just to break down barriers to access and inclusion for people with disabilities. About four years ago, I joined accessiBe as the Community Relations Manager.

I’ve been enjoying being on this journey, meeting incredible people and working with incredible organizations like you. The fact that you’re here today means that you care, that you want to be a part of this. From the bottom of my heart, thank you. We have a lot to cover today. One of the important ideas behind the agenda is that you do not know what you do not know. There is always more to learn, more to do, and more to give. When you approach life that way, that is where meaningful change happens.

So, with the agenda, we’re going to have three different stages. I’m going to be breaking down kind of the accessibility planning, providing the groundwork for building with inclusion from the start. Haim will then lead stage two, showing what accessible design looks like in practice and sharing real tips and tools. In stage three, we’ll have a Q&A and go through questions, thoughts, and ideas. Throughout, we’ll use interactive polls to get your input. We want to hear what you’re thinking, what your thought processes are, and really we’re here to learn together.

Please be as interactive as possible, answer the questions, and let’s do this together. We also want to hear from you. Here’s a question for the chat: what do you think accessibility means to you? Share your answer in the chat, and we’ll look at a few responses. I’m curious to see what people will write. It can mean a lot of different things. Whatever comes to mind is welcome. What does accessibility mean to you? For someone who’s blind, it might mean a screen reader to access the world or the internet. For someone who has ADHD, it might mean distraction-free, clean environments and layouts.

For someone like me, who has ADHD and is paralyzed below the shoulders, accessibility means assistive technology that helps me navigate a page. So for me, you’ll see my quad stick right in front of me. I use this to operate a mouth-controlled cursor on the screen. I use voice-dictation software that types what I say. I also use a screen reader to move through pages. I use several forms of assistive technology, which makes me a good example of how accessibility benefits everyone. Think about using a site on your phone in bright sunlight or with a slow internet connection.

Features such as high contrast and fast load times help everyone. Planning for these different needs improves the experience for all users.

Why Accessibility Matters

Josh: More than 1.3 billion people globally live with a disability, including more than one in four adults in the U.S. These are significant numbers. Disability does not discriminate. It can happen at any moment in youth, old age, or anywhere in between. You know, most of us either know somebody with a disability or have a colleague or have a loved one. What struck me when I joined accessiBe four years ago was how inaccessible the internet remains: fewer than 4% of websites are accessible. We can do better.

We must do better. The fact that you’re here means we’re going to do better with you. Thank you. Thank you. That gap shows that accessibility is not a niche issue. It’s really mainstream. It is necessary for advancing equality and opportunity, and making digital spaces more usable for all. So, let’s face it, accessibility lawsuits are becoming more common, and no one enjoys dealing with them. Prioritizing accessibility helps you stay compliant and avoid those legal risks. But beyond compliance, it’s a smart business move. The fact is, you know, accessible content reaches more people, boosts engagement, improves ROI, builds lasting trust with your users, and it shows that your brand values inclusion in a real, tangible way.

The Business Case

Josh: From a business perspective, accessibility is not only about doing the right thing. It’s about avoiding risk that impacts time, profit, and your reputation. Digital accessibility lawsuits are on the rise, and we can’t afford to ignore it. It is also a powerful business decision: it expands your audience, strengthens trust, and improves ROI. So most importantly, it shows inclusion matters in your organization and not just in theory but in action. Now let’s look at the ethical case.

The Ethical Case

Josh: As I said, accessibility is a smart business decision, but let’s be real, it is also the right thing to do. Honestly, who does not want to help break down barriers? I love heroes, superhero stories, and good people who are willing to go above and beyond. Being able to make your digital assets accessible, in my opinion, you’re a hero and you’re doing incredible work. Accessibility is about people – real people with different needs, using your content in ways that you might not expect. So it’s about progress and not perfection.

A lot of people think that if they are going to address accessibility, they have to get everything 100% right immediately. It is about starting, learning, and being a part of the journey. So next time you ask the question, could my grandma use this? Could someone with a screen reader use it? Could someone who uses assistive technology like me use it? These are the important questions that need to be asked to make sure that it is part of every user’s journey. All right.

Understanding WCAG

Josh: You might be thinking, all right, I like this. I’m on board. Where do I start? For websites and digital content, we follow established standards. This comes from what’s known as WCAG. So, what is WCAG? WCAG stands for Web Content Accessibility Guidelines. It’s the international standard for making web content accessible to all regardless of ability. So these detailed guidelines help ensure your digital content works for a wide range of users. We’ll drop some links in the chat if you want to dive deeper and learn even more. But now that we’ve kind of covered that foundational element of WCAG and understand what it is and where it comes from, I’m going to hand it over to Haim to talk about creating accessible designs that are also visually stunning.

So take it away, Haim.

Designing for Accessibility

Haim: Thank you very much, Josh. I’m happy to take it away from here. I agree, of course, with everything you said. It is an important mission, and we should make sure we get it right. I want to talk about designing for accessibility. From the initial idea through practical design decisions. Design is where accessibility is born or broken. The way you design determines who can and cannot use your product. That is where accessibility starts. Most accessibility barriers are introduced before coding even begins. That means that when you address accessibility in the design phase, you can avoid repeated development work later.

We all know how difficult rework can be during the development cycle. Addressing accessibility at the start can prevent costly fixes later. So we studied this, you know, and we found that focusing on six pillars of accessible design can prevent many common accessibility issues. The framework is easy to understand, and I’m going to go through all six pillars right now and explain each one.

The six pillars are content, interaction, visuals, navigation, feedback and errors, and compatibility. Together, these pillars help us create visually strong designs that remain accessible to people with disabilities. We’re going to start with the first one. The first pillar is content. Is your information understandable to everyone? Okay. Can everyone understand exactly what we’re communicating? The next is interaction. Can everyone operate and use the interface? For visuals, is the content responsive and visible to everyone? For navigation, can users move through the experience and find exactly what they need? For feedback and errors, can everyone notice and understand the system’s response?

For compatibility, will it work with screen readers, keyboards, different browsers, and different screen sizes? Keeping these questions in mind gives us a useful framework. Let’s begin with content. Content should be clear and structured because users with cognitive disabilities may struggle with complex or unstructured information. You want people to use as little cognitive effort as possible when they interact with your products, digital assets, and websites. If the content is confusing, users may give up, make mistakes, or take actions you did not intend, which is something we obviously want to avoid. Keep every instruction and request clear.

Josh, could you share a few tips for making content clear for everyone?

Content: Keep It Clear and Structured

Josh: Clarity starts with plain, simple language that gets straight to the point. If people need a dictionary to understand the content, it is too complicated. Make sure it is simple enough for anyone to understand. The simpler it is, the easier it will be for everyone. Make your calls to action clear so users know exactly what to do next without having to stop and interpret the interface. A clear call to action is essential, but structure your content in a logical and user-friendly order.

Make sure the journey is clear from start to finish to get everybody to the finish line. If only 70% of users reach the finish line, you are losing too many people along the way. No business wants to lose people who were willing to complete that journey. So, structure the content logically and present it in a user-friendly order, but really be mindful of motion. Avoid anything that moves excessively and can’t be paused or stopped, as it can be really distracting. It can overwhelm users and, for people with epilepsy, certain movement can trigger a seizure.

Think about both the content and the journey. Ask friends, family members, and people with disabilities in your community to test it. Watch how they move through the experience and use their technology. There are also companies that can connect you with user testers who have different disabilities. There are many ways to be proactive. The important thing is to choose a starting point and act. Let’s put this into practice with a quick poll, and we’re going to have you pick the different version of content that you think is better.

Haim: Awesome. Let’s put that into practice. Take a moment to read the two examples on the screen. We’ll give you a few seconds to compare them. Which of the two frames is stronger? The one on the left is frame one. The one on the right is frame two. Which one’s better? Okay. All right. 100%. I love it. You guys are brilliant, and that is 100% the correct answer. Thank you.

Josh: Haim, can you explain why the version on the right is stronger?

Haim: Yeah. Well, that was pretty obvious. Everyone was right. As we said earlier, we want to keep it clear. We want the headlines to be as short as possible to give clear directions about what needs to be done. We want to avoid jargon. We do not want jargon to prevent people from understanding what we are saying. We want to keep the language as simple as possible. Bullets and short points also give the content a clear reading direction and make it easier to process.

This is what studies show. You can see that the second version is faster and easier to read. That is why everyone picked this option as well.

Josh: It’s a clearer, more digestible journey. There are probably many places on your site where you could replace a dense version like frame one with something closer to frame two. We can keep improving these touchpoints to strengthen the site. Launching a site is often an exciting and overwhelming process, and teams naturally focus on getting the story and content online. But as time goes on, there’s nothing against the rules that says you can’t go back as you learn new best practices or think about different ways to make it easier and better for people.

It is a journey. Accessibility is a journey. Design is a journey. The work is about continuing to improve those touchpoints while keeping inclusion in mind.

Interaction: Support More Than a Mouse

Josh: Not everyone uses a mouse. People navigate websites in different ways because they have different abilities and needs. Some people use keyboards. I personally use an on-screen keyboard and voice dictation software like Dragon Naturally Speaking. It does amazing things for me. It has allowed me to work as a trial attorney and as the Community Relations Manager at accessiBe. It’s given me access to the digital world. But often, if the website doesn’t support these inputs, I get stuck at checkout, or I can’t fill out a form. I may not even be able to enter my name or credit-card information.

Every business wants to make sure their clients can check out or sign up for an appointment, or can navigate the filters properly to buy the product that’s right for that person. So, when this happens to me, I first get a little sad. I get a little frustrated, and then I leave the site. Sometimes a friend or family member can help, but I do not always have someone beside me. That independence is essential, and many users do not have anyone available to help. People who encounter those barriers often go to a competitor that gets it right, and they may not return.

But one of my favorite statistics of the disability community is that people with disabilities are the most brand loyal customers that you will ever face. When they are treated well, they return again and again as repeat customers. That loyalty is especially important when fewer than 4% of websites are accessible. You know, if you find a website that does it right, you’re going to come back because you want to have that same experience again and again and again. Yes, let’s make that happen.

Josh: All right, so now we’re going to talk about how we fix the interaction experience. And that’s why it’s so important that we make sure your site works with all those input methods. So every user should be able to interact, take action, engage, and stay engaged on your website. Test your site with an on-screen keyboard, standard keyboard navigation, voice dictation, and screen readers. Many free tools let you test these experiences yourself, and community members can also help. Do not limit testing to a mouse or touchscreen.

Try the assistive technologies people use today, and make every interaction cue clear. Enable full keyboard navigation. Use visible focus indicators and don’t rely on a color alone to signal interactivity. Some users cannot distinguish certain colors or contrast differences, so color alone is not a sufficient signal. accessWidget can also improve usability by offering customization options and remediating common accessibility barriers. I have accessWidget on every single one of my sites, nonprofits, and platforms. I love it, and people today want options. Whether or not someone has a disability, options create choice.

It gives us the power to experience a website the way we want. Let’s try another poll and see what you think about this interaction example.

Josh: All right. So, we had 89% choosing frame one and 11% choosing frame two. Haim, can you describe what works and what does not?

Haim: Yeah. Well, that’s interesting. When we talk about interaction, we want to make sure everyone has a way to control and use the interface. Not every user can operate a mouse. Adding controls such as plus and minus buttons, along with keyboard shortcuts, helps more people use the component. So yes, this is why frame one is a better choice than frame two. Adding more control options makes the website more accessible. The keyboard navigation shown in frame one gives users another reliable way to operate the control.

Exactly. By the way, the common use for that is using the arrow keys according to common conventions. For example, when a carousel is coded correctly, users can operate it with the left and right arrow keys instead of a mouse. This is also important. So I’m going to throw it back over to you.

Visuals: Design for Different Levels of Vision

Haim: Let’s move on to visuals. Visuals are central to design. Designing for different levels of vision means creating something visually distinctive that can still be viewed and read by people with different disabilities. This matters because users have different visual needs. Users with low vision or color blindness may need additional support, and many of you likely know someone affected by one of these conditions. They may need stronger contrast and more readable design. If we overlook this, people may miss critical information in the design.

Fortunately, this is relatively easy to address. Maintain a contrast ratio of at least 3:1 for large text and 4.5:1 for regular text. You can do this easily with Figma. Its built-in accessibility option displays the contrast ratio when you select the control next to the color picker. We’ll demonstrate this shortly. Allow text to be resized up to 200% for people who have difficulty reading small fonts. This benefits more than only people with disabilities.

For example, it can also help older users. Making the design easier to see and use benefits everyone. You want to use large, clear touch targets, and that means that if you’re using mobile phones or if you’re using your screen, you want all the touch targets to be large enough for people to tap comfortably, like you know Android and iOS as they have their own rules of 44 and 45 pixels so people will have enough space with their fingers to touch the screen. You do not want people struggling to tap the correct target.

This is also very important to make sure your design will be usable for more people. Let’s put this into practice with another poll. This one may look straightforward, but take a close look. Let’s try this one. Choose the version with the stronger visual design. Frame one or frame two.

Haim: Great job. Yes. Yes. Very good job. The button treatment may make the comparison slightly confusing, but most of you identified it correctly. The stronger contrast makes the content easier to read. You can still use a varied color palette, as this example does with blue, light blue, and an accent color. The key is maintaining sufficient contrast. Yeah, we talked about Figma. Let me show you how this works in Figma.

Use Figma’s built-in tools to validate color choices as you design. It’s very easy. You don’t need to perform a long QA session afterward. When you consider contrast during the design phase, the later QA process becomes much easier. It helps prevent critical information from becoming invisible to users. This is what we all want, obviously. Here is the control in Figma. As you can see, selecting the button in the top-right corner opens Figma’s built-in contrast checker.

Figma compares the selected component with its background, displays the exact contrast ratio, and shows the applicable WCAG conformance level. You have AA or AAA. So you have everything in one place. You don’t have to install different types of plugins. Just use this one and get a better understanding. If you don’t want to use this one, of course, we have accessWidget that can do this for you. It also lets users adjust contrast for themselves. Or you can use other online checkers.

There are many available; simply search for a contrast checker and review the options.

Navigation: Create a Predictable Journey

Haim: Moving on to navigation, users expect a predictable journey. You do not need to reinvent the wheel for digital experiences because accessibility is also about consistency and clear structure. We do not want anyone to get lost or frustrated by the user flow. If the structure is unclear, users get lost and frustrated, which can damage your reputation and cause them to abandon the site. The solution is straightforward: use consistent page layouts and reusable templates. This helps users understand how to navigate your website. Use ARIA landmarks and skip links.

You can talk with developers about that. This is more technical, but teams working with developers should align around consistent page layouts. This is easier when you use a consistent CMS template instead of building every page from scratch. This will also help you maintain the navigation. Use the correct semantic structure, including ARIA landmarks and skip links where appropriate. If you do not have a development team that will do it, you can use accessWidget, which will do it for you. This also helps maintain a logical focus order of your website.

Again, let’s put this into a poll. Another one. This one is trickier, but I’ll explain the difference in a moment. Go ahead. Great – most of you selected the correct answer.

Haim: Here’s why. For the developers among us, when you code a page, you can use semantic tags for different sections in your web page. Rather than using a generic div for every section, use semantic HTML elements where appropriate. Why is it important? Because screen readers can identify each region of the page. People can navigate more easily when they know exactly what kind of content they are consuming and what type of section it is. Whether it is a header, footer, or navigation bar, any kind of semantic tagging is very important here.

This makes the website easier to navigate. Keyboard and on-screen-keyboard shortcuts let users jump quickly between page regions, which can save a great deal of time. I love the one on the left very much. That is exactly right. As we said earlier, not everyone uses a mouse. Some people use assistive technology to navigate your website and your product, and you want them to be able to go through all of these areas. Yes, that is a very important one. So

Communicating Accessibility to Developers

Haim: Let’s talk about the final step in the design process. After applying these pillars, the next step is communicating the requirements to developers. When you finish the design phase, the next question is how to communicate the requirements clearly to developers. One of the best ways to do that is to annotate your design files for developers. Okay, Figma includes annotation features, but they aren’t specifically focused on accessibility. That is why I recommend using an accessibility-focused annotation toolkit. We especially like the CVS Health Accessibility Annotation Toolkit, but you can choose whichever toolkit fits your workflow.

Basically, it lets you mark up design files with clear implementation guidance for developers. This helps designers and developers communicate clearly about how the design should be implemented. If you are not using an automated tool such as accessWidget, you can annotate your designs with one of these toolkits. They already include accessibility guidance, so you do not have to determine every requirement from scratch. Follow the toolkit guidance and apply it directly to your design.

Deliver the annotated designs to your developers so accessibility remains part of the implementation process.

Feedback and Error Messages

Haim: Moving on to feedback, the fifth pillar is feedback and error handling. Feedback tells users exactly what is happening and why. If you do not provide real-time feedback, the user can get stuck, which creates a poor experience and may cause them to leave the website. Think about the times you clicked something, and nothing happened. How frustrating is that? So what can we do about it? Okay. First, we want to add clear, visible messages that also announce this to assistive tech. For example, screen readers.

For example, it is not enough to indicate that a password is invalid without explaining why. The message must also be announced to assistive technology so users who are blind or have visual impairments can understand it. Let’s look at another example. What do you guys think: frame one or frame two? You can also tell us why you chose it. We also have a question from Sylvia about ARIA landmarks.

ARIA landmarks and states communicate the purpose and current state of interface components to assistive technology. For example, a user who is blind cannot visually see that a dropdown is open. We add an ARIA state that communicates that the menu is open. That way, a user who is blind can know that the dropdown is open right now. This is one example of how ARIA markup communicates information.

But you can look it up more. Here are the results. Ninety-six percent of you selected the correct answer.

Haim: You guys were right. Why? Let’s talk about it. Color alone is not enough feedback. As you can see on frame one, even though the password was wrong, the field is red and the button is disabled, but the interface has not provided enough feedback. What about visual impairment? What about users with color blindness? So, we want to give them enough feedback. Okay? We also need to explain what is wrong – for example, that the password has seven characters but lacks both uppercase and lowercase letters. Provide clear, specific feedback so users understand what they need to correct.

That is why frame two is the stronger option. The final pillar is compatibility.

How do we make sure the experience works across devices and interfaces? Again, and this is a bit more technical, and if you do not have a development team or a developer working with you, you can use accessWidget to help you do that because it uses AI to support this work automatically. But it’s really important to test, even if you have different browsers, different computers, and mobile devices, so you can identify hidden differences. Again, we’re talking about ARIA where necessary. I just explained to Sylvia why ARIA markup and semantic HTML matter.

Different browsers can interpret and display your website more reliably when you use semantic HTML, and screen readers benefit as well. Test your design with common screen readers. Today, this is easy to do. On a Mac, you can use VoiceOver, the built-in screen reader found in the Accessibility settings. Other common screen readers include NVDA and JAWS. Explore the available tools and test your design.

It is important.

Compatibility and Assistive Technology

Haim: Let’s put compatibility to the test with one final poll. Again, we have two examples. The Accessible Canada Act graphic is an image. This example is more technical: frame one shows the image in HTML without alternative text, while frame two includes an alt attribute. The answer should be fairly straightforward. Yes – 98% of you were right. Alternative text allows screen readers to communicate the meaning of an image to users who are blind.

Users who are blind cannot see the images on your website, so you need another way to communicate their meaning. That is why you use alt text. Today, many AI tools can help automate this work, and AI is very advanced and can provide accurate information about what is shown in images for users who are blind. AccessWidget can also automate this process for images across your website. You can also write the description that will be most useful to your users.

Haim: Josh, you wanted to add something.

Josh: I was just going to add that AI is getting very good at creating the descriptions, but at the end of the day, the person who took and published the photo is still the best storyteller. And it also helps with the context and flow of the site. When you have the ability, take the time to write thoughtful alt text yourself. But you know, having accessWidget as an additional layer as well is also an option.

Haim: Yes, that is completely true. With that, I’ll hand the conversation back to Josh. First of all, thank you, everyone. It was an honor to accompany you on this journey toward accessible design. Of course you can reach out to me on LinkedIn if you have more questions. I’m here to help. Thank you very much, Josh.

Audience Q&A

Josh: Thanks for sharing your design expertise and your perspective on the accessibility journey. Let’s see what questions we have. We have a few minutes, and again, thanks, Haim. My colleague Sapir is here to present some of your questions.

Sapir: Thanks, Josh. We had some very good questions throughout. Feel free to leave more in the chat. The first question is for you, Josh: Why would I still need to install accessWidget?

Josh: Accessibility is a journey. First, accessWidget scans the site every 24 hours. Websites change constantly, and new content can introduce accessibility issues. Ongoing scanning and remediation are therefore important.

What I value most about accessWidget is the usability it adds for people with different abilities and assistive-technology needs. As I mentioned, I have ADHD, I have a reading disability, and I also have paralysis below my shoulders. accessWidget offers different profiles and extensive customization tools. I use it differently on different websites because each experience may call for different settings. Having those options gives all of your customers the ability to navigate and experience the site on their own terms. It gives them a kind of superpower on the internet and especially on your website.

Yes, the accessWidget is one of my favorite things in the world.

Sapir: That’s awesome. Thanks, Josh, for sharing. We have a question from Rihanna Campbell. She asks, and this is actually for social media, which I’m sure there are plenty of designers here who deal with social media. Is it better to add an image description in the caption or an alt text to the image itself?

Josh: I would put it in the alt-text field. It does not hurt to include a visible description as well, but alt text is specifically intended for people using screen readers. Including a visible image description can also help people with other disabilities understand the image’s meaning. So, it could help other people in that respect as well. Sapir, what do you think?

Sapir: I absolutely love this question because, one, we created a resource for this which I’ll share in a moment, but also alt text, or alternative text, was created to help screen-reader users understand what is shown in the image, including any meaningful text. It can also help with SEO. If the image does not load, the alt text may appear in its place and help the user understand the context, whether or not they are blind. An image description can provide additional context about why the image was chosen, and that’s more related to people with cognitive disabilities or anyone who wants more context about why the image was chosen.

So, I always use both. I recommend using both because they offer accessibility to different communities and generally make your photo more accessible, but it’s for everyone. And in a moment, I’ll share a link to a free alt-text guide we have on our website so you can learn how to add alt text to your different social media platforms, as well as for your websites. Okay, next question is from Jeff. They use accessWidget on their website, but they’re planning to do a complete redo. How should they approach the redesign and create a genuinely accessible website?

They are based in Canada and may also be working with an online portal or app.

Josh: When I started at accessiBe, accessWidget was our flagship product for organizations that needed accessibility support. We now offer a full suite of services, including accessFlow, a developer-focused tool that supports accessibility from the beginning of the build and suggests improvements during development. Building accessibility into the foundation of the website is a best practice, but because accessibility is a journey, we have to meet people where they are.

accessWidget can help at different stages. I’m a strong believer in using accessFlow from the beginning to build accessibility correctly at the code level, while using accessWidget as an ongoing layer as the site changes. Its usability profiles and customization options can take the experience to another level.

Sapir: That was great. Thanks, Josh. The next question is: Does accessWidget send alerts when issues turn up, or do the designers and developers need to check online reports?

Do you want me to take that one?

Josh: You got it.

Sapir: Sure. Okay, cool. So, accessWidget is an AI-powered solution that automatically remediates code issues on the website to make them accessible. But if you want to check your reports, we send a monthly report to your account that includes an overview of all the adjustments made that month. Of course, we do offer more in-depth remediation reports as well as manual audits. So, if you haven’t talked to your account manager in a while, or you want to learn more about the different ways you can test the code level for accessibility, definitely reach out to us, and we’ll follow up with you to provide more answers and solutions.

I think we’re approaching the very end of this, and there are a few more questions. So, to be fair, I will consolidate them and make sure our team addresses each one. This has been a fantastic session. Josh, do you want to share any final words before we close?

Closing Remarks

Josh: Thank you, Sapir. Thank you. Thank you so much, everybody, for being on this journey with us. The fact that you’re here means you care and are willing to act. We’re here to be on this journey with you as well. I always want to say this to people, especially businesses and design professionals. Accessibility is not just a checklist. It’s a commitment to people. It’s a commitment to your customers because every digital choice we make either includes people or excludes someone. Let’s choose to include. Let’s build with empathy. Let’s design with intention.

Let’s create digital spaces with everyone in mind – spaces that work for everybody. I recently watched a Steve Jobs movie, and I’m a big fan of his approach to design. He had a quote: “Design is not just what it looks like and feels like. Design is how it works.” In my opinion, let’s make it work for everyone. Thank you, everybody. On this final slide, GAAD (Global Accessibility Awareness Day) took place on May 15. It is an important day for building awareness and advocacy, having the right conversations, and teaching the world that accessibility matters, and we have a useful resource package.

If you go to accessiBe.com/GAAD, you’ll find a package of content and social posts you can use to share with your community, repost, and adapt to your own brand. It is a useful conversation starter, and you should be proud to be an organization that cares. The more openly we show that accessibility matters, the more other businesses will join the movement. Together, that helps create a more accessible internet and more inclusive digital products. Thank you, everyone, and yeah, please visit the link.

Sapir: Thanks, Josh, and thank you, everyone, for attending. We’ll send the recording and answers to any questions that we missed today. Have a good one. Thank you, everyone.