Our commitment
GeorgeSt is committed to ensuring that our product is accessible to users of all abilities. Accessibility is not an afterthought — it's part of how we design and build every page.
We aim to conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the current international standard for digital accessibility. Where we fall short, we treat it as a bug to fix, not an edge case to ignore.
What we do
Semantic HTML — we use proper heading hierarchy, landmark regions, and ARIA labels where they add clarity.
Keyboard navigation — every interactive element on GeorgeSt is operable with a keyboard alone. We test with tab-order, arrow keys, enter, and escape.
Screen reader compatibility — we test with VoiceOver (macOS, iOS) and NVDA (Windows). Form fields have associated labels. Images have descriptive alt text. Icons have text alternatives.
Color contrast — our body text meets 4.5:1 contrast ratio against its background. Large display text meets 3:1. We don't rely on color alone to convey meaning.
Reduced motion — animations respect the prefers-reduced-motion system setting. Pulse indicators and marquees are disabled for users who request it.
Resizable text — text can be resized up to 200% without loss of content or functionality.
Known limitations
We document known accessibility issues publicly as we discover them. At launch, we are aware of the following:
The pre-flight upload drop zone relies on drag-and-drop as a primary interaction. We provide a keyboard-accessible "browse files" fallback, but screen reader users may find drop zones more verbose than typical file inputs.
Color-severity indicators on the pre-flight report (green / amber / red status pills) are supplemented by text labels so users who cannot perceive the color can still read the severity. We are working to also add iconographic severity markers.
If you encounter an issue not listed here, please tell us — we want to fix it.
Reporting an accessibility issue
If you encounter an accessibility barrier using GeorgeSt, please email us at only@halfdays.ai with the subject line "Accessibility Issue." Include the page URL, a description of the issue, and the assistive technology you were using (if applicable).
We aim to respond within two business days and to fix reported issues within 30 days, depending on complexity. We'll follow up with you on the status.
Ongoing work
We run accessibility audits as part of every major release. We use automated tools (axe DevTools, Lighthouse) in our CI pipeline, and we do manual keyboard and screen reader testing on new features before they ship.
Accessibility is a commitment we take seriously and a standard we're continuously trying to meet better.
Contact
Questions, concerns, or suggestions about accessibility? Email only@halfdays.ai or write to Halfdays AI, LLC, 516 King Street, 2nd Floor, Charleston, SC 29403.