Website Accessibility
What we have implemented on inappcode.com
- Semantic structure: All pages use proper heading hierarchy (h1 → h2 → h3), landmark elements (header, main, footer, nav), and article/section elements with meaningful labels.
- ARIA attributes: Navigation menus, interactive controls, and live regions use ARIA labels and roles. The mobile nav toggle has aria-expanded and aria-controls.
- Keyboard navigation: All buttons, links, and interactive elements are reachable and operable via keyboard. Focus order follows document structure.
- Colour contrast: Text and interactive elements use colour combinations that meet WCAG 2.1 AA contrast ratios. We do not rely on colour alone to convey information.
- Reduced motion: A prefers-reduced-motion media query disables animations including the ambient orbs, typewriter, and cursor blink for users who prefer it.
- Responsive design: The layout adapts to any viewport width and supports browser text scaling without horizontal overflow.
- Image alt text: Decorative images carry empty alt attributes. Informative images carry descriptive alt text.
Android App
Accessibility in the InAppCode app
The InAppCode app is built with React Native and Expo, which uses Android's native
accessibility APIs. We have implemented:
- Screen reader labelling on primary interactive elements
- Touch targets sized per Android accessibility guidelines
- High-contrast colour choices in the dark theme
Known limitations in the current version:
- The Monaco Editor inside the WebView may have limited screen reader support. We are evaluating alternative approaches for users who rely heavily on screen readers for code input.
- Some animated elements in the home screen do not yet have a user-controlled motion preference. This is on our roadmap.
Known Issues
Areas we are actively working on.
- Monaco Editor screen reader compatibility in the Android WebView
- App-level motion preference control
- Improved focus management in the code submission flow
- Additional ARIA live region coverage for AI feedback results
If you encounter an accessibility barrier not listed here, please report it. We
prioritise fixes that prevent users from completing core practice flows.
Report a Barrier
How to contact us about accessibility.
If you find any part of InAppCode difficult or impossible to use due to an
accessibility barrier, please email:
connect@inappcode.com — subject: Accessibility Report
In your message, include:
- Which part of the website or app you were using
- The assistive technology or accommodation you rely on
- A description of the barrier you encountered
- Your Android version and device model, if applicable
We aim to respond within 5 business days and will work with you to find a solution.