Accessibility

Breauti Studio treats accessibility as part of design, engineering, content, and verification—not a decorative statement added after launch.

Effective
July 24, 2026
Reference target
WCAG 2.2 Level AA
Status
Ongoing development
  • Semantic structureHeadings, landmarks, labels, and controls
  • Keyboard operationVisible focus and non-pointer access
  • Theme-aware contrastReadable light, dark, and forced-color states
  • Feedback mattersBarriers can be reported for review
A practical commitment

Breauti aims to make the public Studio experience perceivable, operable, understandable, and robust. Accessibility is reviewed as the site changes, and meaningful barriers take priority over a claim of perfect conformance.

Commitment and scope

Breauti Studio wants people with disabilities to be able to understand the offer, review work, read policies, prepare a project request, and use any future client or payment experience. The goal applies across desktop, tablet, and mobile devices and includes keyboard, screen-reader, magnification, contrast, reduced-motion, and touch use.

This statement covers the public Breauti Studio website. Accessibility requirements for a client project are defined in that project's scope, users, content, platforms, and legal context. Studio will not claim that building to a reference standard automatically satisfies every law or every person's needs.

Measures in the current site

  • Semantic headings, navigation, main content, sections, lists, tables, labels, and buttons are used where appropriate.
  • Interactive controls are designed for keyboard use with visible focus and meaningful accessible names.
  • Layouts reflow across common viewport sizes and avoid requiring horizontal page scrolling in ordinary use.
  • Light and dark themes preserve readable contrast; text selection is theme-inverted; forced-color behavior is considered.
  • Reduced-motion preferences shorten or remove non-essential transitions and animations.
  • Policy pages include a browser print and Save as PDF path with a simplified print layout.

Reference standard and verification

Breauti uses the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, as the public site's reference target. WCAG provides testable criteria across perceivable, operable, understandable, and robust content. It does not cover every disability, situation, device, or legal requirement.

Verification should combine automated checks with keyboard use, zoom and reflow review, contrast review, reduced-motion and forced-color checks, screen-reader inspection of key flows, and human review of content and interaction. A passing automated scan by itself is not treated as proof of accessibility.

Breauti has not obtained an independent accessibility certification for this development-stage site. This statement describes the intended standard and current practices rather than promising flawless conformance.

Known and possible limitations

The site is actively being developed. Complex visual project previews, large interface screenshots, interactive carousels, dialogs, locally prepared request content, and long policy tables can create barriers that require continued testing. Images are intended to have meaningful text alternatives when they communicate content; decorative imagery should be hidden from assistive technology.

External sites, portfolios, repositories, future Stripe-hosted checkout, Firebase interfaces, browsers, operating systems, and other third-party technology are not fully controlled by Breauti. Breauti will choose and configure providers with accessibility in mind and provide an alternative route where reasonably possible, but cannot certify every external experience.

The current project intake is local-only and does not submit a request. This is a product-readiness limitation as well as a communication limitation; it will be clearly updated before a live intake is enabled.

Feedback and accessible assistance

If a part of the Studio site is difficult to use, support@breauti.com is the designated launch contact. The inbox must be activated and tested before the development notice is removed. Once active, helpful details include the page or feature, what you were trying to do, the barrier, browser and device, assistive technology if relevant, and the format or accommodation that would help. Do not include passwords, full payment details, or sensitive identity documents.

Breauti will review accessibility reports in proportion to their impact, make reasonable efforts to provide the information or service in an accessible way, and prioritize high-impact barriers. No fixed response-time service level applies unless separately agreed, but reports should receive a meaningful follow-up through the verified support channel.

Alternative formats or communication methods may be arranged where reasonably possible. This statement will be updated as the site, client workspace, checkout, and support processes change.