Equalize Digital Web Accessibility

A lot has changed in Accessibility Checker Pro over the past year. We’ve spent that time rebuilding the plugin around one goal:
Helping you find and fix accessibility issues faster, without pulling you out of WordPress.

The redesigned Accessibility Checker helps you spot problems, prioritize your next steps, and track your progress faster, while making issues easier to understand and action.

Join us for a deep dive into what’s changed and how Accessibility Checker Pro 2.0 can make your accessibility work easier. This is a great webinar to drop into, whether you’re considering using Accessibility Checker for the first time, are a long-time customer, or you’ve been away for awhile and are curious to see how the software has improved.

We’ll explore how to:

• Find what needs your attention most with Pro 2.0’s Issues Explorer, including powerful filters, grouping, and bulk actions.
• Review issues while you edit with the new Block Editor sidebar.
• See exactly where problems appear when using a front-end builder, using the redesigned Front-End Highlighter and its built-in explanations and supported fixes.
• Track your progress with weekly accessibility email reports, and get instant feedback on fixes as you deploy them with our new issue-specific re-scan feature.
• Save time across websites by importing and exporting settings and fix configurations in Pro, great for large institutions or agencies.

Come see what changed over the last year, and leave with practical ways to make accessibility part of your publishing and maintenance routine using Accessibility Checker Pro.

Automated accessibility scanners like Accessibility Checker, WAVE, axe, and SiteImprove flag issues that require human review or judgment. When you see these issues, you need to assess if they are an accessibility failure and, if so, how to fix them. These “Needs Review” issues are among the most common issues we get asked about.

In this presentation, Amber will provide real-world examples of elements that flag in automated accessibility reports and discuss how to assess if they’re truly problems. Attendees will learn how to think critically about and act on reports delivered by Accessibility Checker and similar accessibility browser extensions.

Thank you to our sponsors:

Accessibility work doesn’t just involve detecting and resolving issues in your content or code. You’ll also be deciding what to do with years of outdated content, or figuring out the best way to surface large quantities public meeting information.

Join us for a practical look at the products in Equalize Digital’s growing Remediation Suite: ArchiveWP, and BoardScribe. We’ll explore where each tool fits into your WordPress accessibility work and the systemic problems each can help you solve going forward.

In this session, we’ll cover:

• Using ArchiveWP to organize and clearly label outdated content while keeping it available for reference, to help meet archived content exception rules under some accessibility regulations.
• Using BoardScribe to improve how you present meeting agendas and minutes, addressing issues such as ambiguous links, missing table headers, and poorly structured meeting listings.

Adopting better standardized practices, alongside the right tools and systems, helps you make accessibility the “default state” for everything you do. That’s what working smarter (not harder!) means to us, and in this session we’ll show you how to do that.

Building a custom Gutenberg block that looks polished is easy. Building one that actually works for keyboard and screen reader users in the editor, on the frontend, and in any interactive behavior it adds is where most blocks are overlooked.

This session walks through building an accessible custom block from the ground up across all three of those layers: keyboard and screen-reader support inside the block editor, semantic markup in the rendered frontend output, and correct ARIA Authoring Practices patterns for common interactive block widgets like tabs, accordions, and modals. Plus diving into what the Interactivity API does and doesn’t handle for you automatically.

Thank you to our sponsors: