Accessibility Statement

1. Our commitment

Lumabyte is committed to making this platform — used by coaches, event organizers, and supporters for WRO (World Robot Olympiad) event registration and donations — as accessible as we can to people of all abilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We recognize that accessibility is an ongoing effort, and we continue to make improvements over time.

2. Measures we take

We work toward accessibility in the following ways:

• Semantic HTML. We use native HTML elements — headings, landmarks, lists, tables, fieldsets, and form labels — so that page structure is meaningful to assistive technologies without relying solely on visual layout.
• Keyboard accessibility. All interactive elements — navigation, forms, registration steps, and donation controls — are reachable and operable using a keyboard alone. A skip-to-content link is present on every page so keyboard users can bypass repeated navigation.
• Screen reader support. We use appropriate ARIA roles and live regions to announce status changes (such as form submission progress and error messages) to screen reader users. We test core flows for screen reader compatibility and are continuing to improve coverage — see the known limitations below.
• Color and contrast. Text and interactive elements are styled to meet or exceed the WCAG AA contrast thresholds (4.5:1 for normal text, 3:1 for large text and UI components). We do not rely on color alone to convey meaning.
• Automated testing. Our test suite includes automated accessibility checks (axe-based scans run via npm run test:a11y with Playwright) that run against core pages and flows. These checks are part of our development process and catch a broad class of structural and labeling issues before they ship.
• Manual testing. We supplement automated checks with keyboard-only walkthroughs of every core task — signing in, selecting a team, completing registration, and making a donation. Manual screen-reader testing with VoiceOver and NVDA has not yet been performed; it is a planned next step, and specific verification items are tracked internally.

3. Known limitations

We are aware of the following areas where our accessibility work is not yet complete:

• Focus ring styling is not yet consistent on every inline link throughout the application. We are addressing this incrementally.
• After dismissing certain inline notices (for example, the post-donation confirmation banner), keyboard focus is not always restored to a predictable location. We have identified the affected components and a fix is planned.
• Human verification with VoiceOver and NVDA is still pending for route-change focus announcements, the donation amount radio group announcement wording, and the notice-dismiss focus behavior. No automated tool can substitute for this testing, and we plan to complete it.

If you encounter an accessibility barrier not listed here, please let us know using the contact information in the next section.

4. Reporting an accessibility barrier

If you experience difficulty using any part of this platform because of an accessibility barrier, or if you have a suggestion for how we could improve, please email us at info@bytewiseholding.com. Please describe the barrier you encountered and, if possible, the page or step where it occurred.

We are committed to reviewing every report and responding within a reasonable time. Where a reported barrier is within our control, we will work to address it in a future update.

5. Ongoing work

Accessibility is not a one-time project. We conduct periodic audits of the platform — combining automated scans and keyboard-only testing — and address findings through our normal development and review process. We plan to add screen-reader testing to this practice on an ongoing basis. This statement will be updated to reflect the current state of our accessibility work as improvements are made.