BrandMEE is now Avad Shamar Creative: same founder, same standard, a deeper build. Read the story

Accessibility statement.

What this site is built to, how we test it, what we know isn't finished, and how to tell us when something blocks you.

Effective date: September 6, 2026

The short version

  • This site targets WCAG 2.2 Level AA, the current standard, not the older 2.1.
  • Every template is checked by automated tooling and by a person using a keyboard and a screen reader before it ships.
  • We name what isn't done yet rather than claiming full conformance.
  • If something on this site blocks you, tell us and a person will answer, and fix it.

Our commitment

Avad Shamar Creative builds to Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That commitment applies to this website and to the websites and digital experiences we build for clients. We don't hold our own site to a lower standard than the work we sell.

Accessibility here is a build requirement, not a post-launch audit item. It is scoped into every engagement from the start, because retrofitting access into a finished site costs more and produces worse results than designing for it from the first wireframe.

What that means in practice

The specific commitments this site is built and tested against:

  • Contrast. Text meets or exceeds AA contrast on every surface, with body text verified at AAA on both our light and dark fields. Interactive non-text elements meet at least 3:1.
  • Keyboard. Every interaction is operable without a mouse, in a logical tab order, with a skip link to main content and no focus traps. The mobile menu and accordions return focus where you'd expect.
  • Focus. A visible focus indicator on every interactive element, at 2px with 2px of offset. It is never suppressed for visual tidiness.
  • Structure. One H1 per page, no skipped heading levels, and proper landmarks (header, nav, main, and footer) so screen-reader navigation by region and heading works.
  • Forms. Visible labels that stay visible (never a placeholder standing in for a label), programmatic label association, plain-language inline errors conveyed by text as well as color, and touch targets of at least 44px.
  • Images and media. Descriptive alternative text on informative images, empty alt on decorative ones, no autoplaying media, and captions and transcripts on any video we publish.
  • Motion. Full support for the reduced-motion preference: transform-based animation is removed, not merely shortened. Nothing on this site flashes.
  • Small screens and zoom. Readable at 320px wide with no horizontal scrolling, and pinch-zoom is never disabled.

How we test

Two passes, both required before a template ships:

  • Automated. Accessibility checks run against every page as part of the build, so regressions are caught at the point they're introduced rather than at the next audit.
  • Manual. A person navigates each template by keyboard alone and again with a screen reader. Automated tools catch perhaps a third of real barriers; the rest need someone to actually try to use the page.

What isn't finished

An accessibility statement that claims everything is perfect isn't credible. Here is the honest state of this site:

Two we know about. The Lagniappe checkout hands off to Stripe’s hosted payment pages, which we do not control (Stripe publishes its own accessibility commitments). And case-study imagery is decorative: the copy beside each image carries the meaning, so nothing is lost if images are off. If you find a third, tell us.

Items we already know to revisit: third-party components we don't control (including the scheduler and, once wired, the form backend) are assessed before launch, and where a vendor's component falls short of 2.2 AA we say so here and give you a way to reach us that doesn't require it.

Content published over time (articles, case studies, and any documents we post) is held to the same standard, but new content is where accessibility most often slips. If you find a page that falls short, that's a defect, and we'd like to know about it.

Tell us about a barrier

If any part of this site prevents you from doing what you came to do, contact us and describe what happened. You don't need to identify the guideline or use technical language: "the booking form wouldn't let me past the date field with my keyboard" is exactly the right amount of detail.

We aim to acknowledge accessibility reports within two business days and to tell you what we're doing about it, including a timeline when the fix isn't immediate. If the barrier keeps you from reaching us through this site at all, the contact page, or ask for a phone call in your message and we will set one up.

If you need this content another way

Anything on this site can be provided in an alternative format on request: plain text, large print, or read aloud in conversation. Ask, and we'll arrange it. There's no process to navigate and no form to justify the request.

Formal specifics

  • Conformance target: WCAG 2.2 Level AA.
  • Conformance status: partially conformant with WCAG 2.2 Level AA. Some parts of the content may not yet fully conform.
  • Assessment approach: internal automated testing plus manual keyboard and screen-reader review. No third-party audit has been commissioned yet; one is planned for the first year.
  • Applies to: avadshamarcreative.com, including the scheduler. Third-party tools embedded or linked from this site are noted above.

This statement is reviewed at least annually and whenever a template changes materially. Last reviewed: September 6, 2026. Related: our privacy policy and terms.