1. Home
  3. Accessibility Statement
Digital access and usability

Access Is PartOf The Experience.

Pro Boost Local aims to make its consumer and partner websites usable by people with varied abilities, technologies, devices, and access needs. Accessibility is an ongoing design, content, testing, and maintenance responsibility.

Last updated: July 15, 2026
Clear role separationPublishable operating templateReview when practices change
Pro Boost Local framework

Important Information In A Usable Format.

WCAG2.2 AA target
KEYBOARDOperable controls
TEXTReadable content
FEEDBACKIssue reporting
Open the website directory

A goal—not an unverified certification

Pro Boost Local aims to align owned content with WCAG 2.2 Level AA where reasonably practicable. Do not claim full conformance until the complete live site and third-party integrations are tested.

Accessibility efforts

The Design System Includes Practical Access Features.

Final performance depends on the theme, plugins, content, forms, images, and scripts.

Keyboard access

Links, buttons, forms, disclosures, and navigation should remain usable without a mouse.

Visible focus

Interactive elements use a visible focus indicator.

Readable typography

Responsive text, spacing, contrast, line length, and hierarchy support reading.

Text alternatives

Meaningful images need useful alt text; decorative images should be hidden.

Media alternatives

Recorded media should include captions, transcripts, or equivalent information.

Reduced motion

The design system respects reduced-motion preferences.

WCAG principles

Content Should Be Perceivable, Operable, Understandable, And Robust.

These principles should guide pages, forms, images, video, and plugins.

PerceivableUse text alternatives, contrast, adaptable content, captions, and more than color alone.
OperableSupport keyboard navigation, focus, target sizes, timing, and safe motion.
UnderstandableUse clear language, consistent navigation, labels, and helpful errors.
RobustUse semantic HTML, accessible names, and compatibility with assistive technology.
Content and form standards

Accessibility Can Be Lost During Routine Editing.

Editors should preserve structure.

Heading hierarchy

Use logical heading levels rather than choosing headings only for visual size.

Descriptive links

Use link text that explains the destination.

Semantic lists and tables

Use real structural markup for relationships.

Form labels and errors

Associate labels, identify required fields, and explain errors.

Contrast and color

Maintain contrast and do not rely only on color.

Plain language

Explain service, insurance, partner, and legal concepts clearly.

Testing and maintenance

Automated Testing Alone Is Not Enough.

Combine tools, human review, and assistive technology.

Automated scans

Identify common contrast, label, structure, and code issues.

Keyboard testing

Review order, focus, menus, forms, and controls.

Screen-reader review

Test representative pages, navigation, forms, errors, and dynamic content.

Responsive testing

Review zoom, reflow, orientation, mobile layouts, and touch targets.

Human review

Include people with disabilities and varied access needs when practical.

Regression testing

Retest after theme, plugin, content, tracking, or design changes.

Known limitations

Third-Party Tools May Create Barriers.

Call widgets, maps, forms, videos, CAPTCHA, documents, and provider sites may not be fully controlled.

Plugins and embedsChoose accessible vendors and provide alternatives when barriers remain.
Provider websitesIndependent-provider websites follow their own accessibility practices.
DocumentsPDFs or legacy files may require remediation or an accessible alternative.
Alternative assistanceOffer another method to obtain information or submit a request.
Feedback process

Accessibility Reports Need A Useful Response Path.

Specific information helps reproduce the problem.

Submit the barrier

Use Contact, select Accessibility Issue, and provide the page URL and task.

Include details

Share device, browser, assistive technology, error, and preferred contact method.

Review and reproduce

Evaluate the page, component, plugin, form, or vendor tool.

Respond and assist

Communicate status and provide another accessible method where possible.

Contact and updates

Accessibility Feedback Is Welcome.

Report issues through Contact or accessibility@proboostlocal.com. Replace the email with the final monitored contact.

Review this statement when the design system, theme, forms, call widgets, third-party tools, or target changes.

Common questions

Important Answers Before You Continue.

Does the site claim full WCAG conformance?

No. It targets WCAG 2.2 Level AA, but conformance should be claimed only after testing and remediation.

How do I report a problem?

Use Contact and provide the page, task, device, browser, and assistive technology if possible.

Can I request another format?

Yes. Describe the information and format or assistance needed.

Are provider sites covered?

No. Third-party provider sites are controlled by those providers.

Does the design support reduced motion?

The supplied design system does, but the final site and plugins must be tested.

Will an alternative be offered?

The goal is to provide another reasonable method when a barrier is identified.

Pro Boost Local

Accessible Design Requires Ongoing Attention—Not A One-Time Badge.

Review the related consumer, partner, privacy, recording, accessibility, and website terms that apply to the interaction.

Company contact

General business inquiries

Call Pro Boost Local with questions about this page, accessibility, privacy, or other company matters.

Call (504) 417-7767