Accessibility Statement

Wildcore Studio is committed to making wildcore.studioand every website we build usable for as many people as possible — including people who use assistive technology like screen readers, keyboard navigation, voice control, or switch devices. Accessibility isn't a checkbox for us. It's part of what “a website that actually works” means.

Our commitment

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible to people with disabilities and easier to use for everyone. We also align with the accessibility requirements of Section 508 of the U.S. Rehabilitation Act.

Level AA is the standard most public-facing sites target and is the conformance level referenced by the U.S. Department of Justice's ADA web accessibility guidance.

What we've built in

Some of what we do to meet WCAG 2.2 AA on wildcore.studio:

• Semantic HTML structure — headings, lists, landmarks, and form labels are used as intended so screen readers can navigate the page logically.
• Full keyboard navigation — every interactive element (links, buttons, form inputs, menus) is reachable and operable without a mouse. Visible focus indicators appear wherever focus lands.
• Alt text on meaningful images — every image that carries information has descriptive alt text. Decorative images are marked as such so screen readers skip them.
• Color contrast — body text meets the WCAG AA 4.5:1 contrast ratio on normal text and 3:1 on large text, in both light and dark sections.
• Reduced-motion support — animations respect the prefers-reduced-motionsystem setting. If you've asked your OS to reduce motion, decorative animations are disabled.
• Resizable text — layouts remain usable when text is zoomed up to 200% without horizontal scrolling on mobile.
• Descriptive link text— we avoid “click here” and name the destination in the link itself, which matters when a screen-reader user scans a list of links out of context.
• Form labels and error messages — every form field has a visible label and programmatic association. Error states are announced, not just colored.
• Accessible names for icon-only buttons — things like the chat widget toggle and mobile menu button carry an explicit aria-label.

How we test

We test accessibility with a mix of automated and manual techniques:

• Automated audits with Google Lighthouse and axe-core run against the site regularly
• Keyboard-only navigation testing on every major layout change
• Screen reader spot-checks with VoiceOver (macOS/iOS) and occasional NVDA (Windows)
• Color contrast checks against the WCAG AA ratio using browser devtools

Where we still have work to do

We don't claim to be perfect. Accessibility is an ongoing commitment, not a one-time fix. A few honest caveats:

• Third-party embeds— the chat widget, analytics scripts, and scheduling embeds are provided by external vendors. We evaluate each one for accessibility before adding it, but we don't control their internal implementation.
• Older content — we continuously review and update older blog posts for heading structure, alt text, and link clarity. Some may not yet match our current standards.
• Video content — not all video on the site has captions yet. Video with spoken content is a priority for our next round of accessibility work.

Found an accessibility barrier?

If you hit a barrier using wildcore.studio — something that didn't work with your screen reader, a color you couldn't read, a button you couldn't reach with the keyboard, anything — we want to know. We take every accessibility report seriously and try to respond within two business days.

Please include:

• The page URL where you ran into the problem
• What you were trying to do
• What went wrong (error message, unexpected behavior, etc.)
• The assistive technology you were using, if applicable (screen reader, browser, OS)

Email us at accessibility@wildcore.studio. If you'd rather go direct, Corey reads everything sent to corey@wildcore.studio.

Technical specifications

wildcore.studio relies on the following web technologies for conformance with the accessibility standards used:

• HTML5
• WAI-ARIA (where native semantics aren't sufficient)
• CSS3
• JavaScript (progressively enhanced)

These technologies are used in reliance on accessibility standards and browser / assistive-technology compatibility. The site is tested with recent versions of Chrome, Safari, Firefox, and Edge paired with VoiceOver and NVDA.

Formal approach

This statement was prepared on April 12, 2026 and is based on a combination of internal evaluation and automated accessibility audits. We review the statement at least annually, and update it whenever we make a substantial change to the site.