Studio document

Accessibility Statement

Accessibility approach, structure, keyboard behaviour, typography, forms, known limits, testing, and feedback.

1. Commitment

Got Ur Web aims to provide a perceivable, operable, understandable, and robust static experience. Accessibility is treated as an ongoing practice rather than a permanent certification.

2. Structure and navigation

Pages use landmarks, one main heading, ordered heading levels, a skip link, descriptive navigation labels, and consistent footer routes. The mobile menu uses a native button and exposes its expanded state.

3. Keyboard and focus

Links, buttons, fields, selects, and text areas can be reached with a keyboard. Browser-native focus is preserved, and interactive controls do not depend on hover alone.

4. Typography, colour, and motion

Body text and long-form articles use readable measures and strong contrast. Accent colour is not the sole carrier of required meaning. The site uses no autoplay video, parallax, or required motion.

5. Forms and local tools

Fields have visible labels and native validation. Status messages use live regions. The site explicitly distinguishes local validation and storage from transmission.

6. Known limits

Remote Google Fonts may be unavailable or blocked, in which case fallback fonts appear. The highly expressive display type can create unusual line breaks at extreme zoom, but content remains in source order and responsive layouts collapse to one column.

7. Testing approach

Release review covers keyboard operation, heading structure, zoom and narrow widths, colour contrast, browser console errors, route integrity, and core local-only interactions. Automated tools are supplemented by manual checks.

8. Feedback

Accessibility feedback can be sent to [email protected]. Include the route, device, browser, assistive technology if relevant, and the barrier encountered. The static site cannot guarantee delivery of that archived-domain address.