S/legal, Accessibility

Accessibility

Last updated: July 12, 2026

SearchLocalPro is built to be usable by everyone, including people who rely on assistive technology. This statement explains the accessibility standard we work toward, the steps we take to meet it, and how to reach us if something gets in your way.

Report an accessibility issue

Our commitment

We treat accessibility as part of how we build, not an afterthought. Our goal is for anyone to be able to find a contractor, post a project, and manage their work on SearchLocalPro, regardless of ability or the tools they use to get online.

The standard we work toward

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard our design system and interactive components are measured against.

New work is reviewed against these guidelines as part of our release process, and accessibility checks run automatically on every change to the site.

What we do to support accessibility

Use semantic HTML and ARIA where it helps assistive technology understand the page.

Make interactive elements operable with a keyboard, with visible focus.

Meet AA color-contrast levels for text and controls, using our shared design tokens rather than one-off colors.

Provide text alternatives for images that carry meaning.

Support browser zoom and honor the reduced-motion preference for animations.

Offer the full experience in both English and Spanish.

Ongoing work

Accessibility is never finished. As we add features, we keep auditing the site and fixing what we find.

Some areas may not yet fully meet our target. When we identify a barrier, we prioritize the fix based on how much it affects people trying to get things done.

Tell us about a barrier

If any part of SearchLocalPro is hard to use, read, or navigate, we want to know. Email us with the page or screen, the device or assistive technology you were using, and what happened. We will look into it and work to fix it.

Third-party content

Some tools or content from outside providers may not fully meet our accessibility standard. Where we rely on them, we push for accessible alternatives and account for them in our own testing.