Skip to content
Accessibility

Accessibility Statement

What this site does to be usable by everyone, and — more usefully — the specific place where it currently does not.

Effective September 30, 2026 · Daybreak Growth Systems, LLC

01Our commitment

Daybreak Growth Systems, LLC is committed to making this website usable by as many people as possible, including people who browse with a screen reader, navigate by keyboard, rely on magnification, or need reduced motion.

We build to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our target standard. That is the benchmark the Department of Justice and the courts have consistently applied when assessing whether a business’s website is accessible under Title III of the Americans with Disabilities Act.

We say “target” deliberately. This site has not been through a formal third-party audit, so we are not claiming full conformance. Section 3 records what we know is wrong with it today.

02What is in place

Each of these is built into the site rather than added by an overlay:

  • A skip link as the first focusable element on every page, so keyboard users can jump past the navigation straight to the content.
  • A visible focus indicator on every interactive element, using :focus-visible so it appears for keyboard users without cluttering the page for mouse users.
  • Semantic landmarks — header, nav, main and footer — and a heading structure that follows the document rather than the visual design.
  • Descriptive alternative text on photographs and on the concept artwork, written to convey what the image shows rather than to repeat the caption.
  • Form fields with real, associated labels. Errors are announced with aria-invalid and linked to the field with aria-describedby, so a screen reader reads the problem rather than just the field name.
  • Full support for prefers-reduced-motion: the scroll-reveal animations, smooth scrolling and the counting statistics all stop when the operating system asks them to.
  • Text that reflows and remains readable when zoomed, with layouts built on relative units rather than fixed pixel widths.
  • No content that flashes, and no carousels or dialogs that move or dismiss on a timer.
  • No accessibility overlay or accessibility widget. These are known to interfere with assistive technology that people have already configured, so we do not use one.

03Where it falls short

We would rather name these than let someone discover them on their own time.

  • The concept homepages are hidden from screen readers. The sample sites in “Our work” are drawn illustrations, so they are marked as decorative and their text is not read out. Each one’s name, trade and description are provided as text for screen readers instead.
  • The crack checker’s answer is a summary. Each choice is a labelled button you can reach and press by keyboard, and the answer is announced when it changes. The colour of the severity label is always accompanied by its wording, never used on its own.

If any of these blocks you from doing something on this site, the section below is not a formality — write to us and we will get you the information another way while we fix the underlying problem.

04Telling us about a barrier

Email contact@daybreaktechinnovations.com with the page you were on, what you were trying to do, and the assistive technology or browser you were using if you know it. You do not need to identify the WCAG criterion — describing what happened is more useful.

We aim to acknowledge accessibility reports within two business days and to tell you either when it is fixed or, if it is going to take longer, what the workaround is in the meantime. If you need something on this site in an alternative format, ask and we will send it.

05Sites we build for clients

Accessibility is part of the build, not an upsell. Contractors’ offices are places of public accommodation, which means their websites carry the same Title III exposure this one does — and the demand letters that follow an inaccessible contractor site are a real and growing cost in this industry.

We build client sites to the same WCAG 2.1 AA target, we do not install accessibility overlays on them, and we will tell a client plainly when something they have asked for would create a barrier.