ES EN
ES EN

Accessibility

Last updated: 14 January 2026

Oliver BAM is built to be usable by as many people as possible — including people who use screen readers, keyboard navigation, voice input, or need bigger text / higher zoom.

If something on this site isn’t working for you, tell us. We’ll fix what we can.

Our commitment

We’re working towards meeting WCAG 2.2, Level AA (the widely used standard for accessible websites).

What we’ve done so far

Here are some accessibility basics already in place (and we’ll keep improving):

  • Skip to content is available on pages, so keyboard and screen reader users can jump past navigation.

  • Clear page structure and consistent navigation across the site.

  • A simple, low-clutter layout designed for readability (less chaos, more clarity).

Where things can still be tricky

We haven’t completed a full independent accessibility audit yet, so the site is partially compliant with WCAG 2.2 AA while we continue improvements.

Some areas that may need extra attention:

  • Images and icons: some decorative visuals may not have perfect text alternatives yet.

  • Sliders / carousels: rotating content can be awkward with keyboards and some assistive tech.

  • Third-party widgets: embedded tools can behave differently depending on device and assistive technology.

If any of this blocks you, email us and we’ll help directly.

Forms and reCAPTCHA

We use Google reCAPTCHA to protect our forms from spam. reCAPTCHA is designed to work with major screen readers and announces status changes (like when verification is complete).

That said, CAPTCHAs can still be a barrier for some users. If reCAPTCHA gets in your way, email hello@businessawaremarketing.com and we’ll make sure you can contact us another way.

(You may also see Google’s required disclosure text in the form flow: Google Privacy Policy and Terms apply.)

How to report an accessibility issue

Email: hello@businessawaremarketing.com

Helpful details (if you can):

  • the page URL

  • what you were trying to do

  • what happened instead

  • your device/browser (and screen reader, if you use one)

Links