Legal
Accessibility Statement
Galeo Strategy is committed to making galeostrategy.com accessible to all users, including those with disabilities.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. These guidelines explain how to make web content more accessible to people with disabilities. Conformance with these guidelines helps make the web more user-friendly for everyone.
The accessibility audit below was conducted as part of the initial site build. We review accessibility continuously and update this statement as issues are identified and resolved.
Conformance status: Partially conformant. The site meets most WCAG 2.1 AA criteria. Known gaps are listed in the audit findings below.
Audit Findings
WCAG 2.1 AA review
Conducted July 2025 — galeostrategy.com initial build.
Color contrast — body text
Body text (#141A22 on #FFFFFF) and muted text (#5B6472 on #FFFFFF and #F6F5F1) meet AA contrast ratios. Navy headings on bone/white pass at all tested sizes.
Color contrast — accent elements
The accent color (#3B5B8C) on white yields approximately 5.2:1 — passes AA for normal text (≥4.5:1) and large text. Eyebrow labels at 0.75rem/600 weight are borderline; recommend verifying with a contrast tool once brand colors are finalized.
Focus states
Global :focus-visible rule applies a 2px solid accent outline with 3px offset to all interactive elements. Tested on nav links, buttons, form inputs, and accordion triggers.
Keyboard navigation
All interactive elements are reachable and operable via keyboard. Mobile navigation overlay traps focus correctly. TestimonialCarousel responds to arrow keys. FAQAccordion uses button elements with proper expand/collapse.
Skip navigation
No skip-to-main-content link is present. Screen reader and keyboard users must tab through the full header on every page. Recommend adding a visually hidden skip link as the first focusable element in layout.tsx.
Heading hierarchy
All pages use a single H1 in the hero section. H2s and H3s follow logical document order. No heading levels are skipped.
Image alt text
Logo images in Header and Footer use alt="Galeo Strategy" — appropriate. The HeroMotif component renders decorative SVG shapes; confirm aria-hidden is present on those (not verified in this audit). No content images exist yet — alt text requirements apply when real photography or diagrams are added.
Form labels
Contact form inputs are each associated with a visible <label> via htmlFor/id pairing. Required fields use the required attribute. Placeholder text supplements but does not replace labels.
ARIA live regions
TestimonialCarousel uses aria-live='polite' on the quote region. No other dynamic content regions were identified that require live region markup.
Motion and animation
The Reveal component and TestimonialCarousel both check prefers-reduced-motion and disable animations accordingly. No auto-playing video or flashing content is present.
Semantic HTML
Pages use appropriate landmark elements: <header>, <nav>, <main> (via layout), <footer>, <section>, <article>. Lists use <ul>/<li>. Buttons use <button>.
Link purpose
Several CTA links and footer links use generic text like "↗" as the only visible label. The framed arrow in the footer bottom row has no accessible label. Recommend adding aria-label to icon-only links.
Feedback and Contact
We welcome feedback on the accessibility of galeostrategy.com. If you encounter accessibility barriers, please contact us:
info@galeostrategy.com
(312) 205-9695
We aim to respond to accessibility feedback within 5 business days.
Technical Specifications
Accessibility of this site relies on the following technologies working in conjunction with your browser: HTML, CSS, JavaScript, WAI-ARIA. These technologies are relied upon for conformance with the accessibility standards used.
Assessment Approach
Galeo Strategy assessed accessibility through self-evaluation during the initial site build. We evaluate code-level conformance (semantic HTML, ARIA usage, focus management, color contrast ratios) as part of ongoing development. We have not yet conducted user testing with assistive technology users — this is planned before public launch.