o30m Academy aims to meet WCAG 2.2 Level AA where practical and has regard to the Rights of Persons with Disabilities Act, 2016 (India). This statement describes the measures taken, known limitations, and how to report a barrier. It is not a claim of full conformance.
Measures
- Semantic HTML landmarks, headings, lists, tables, and form labels.
- A skip link and visible keyboard focus styles.
- Status is communicated with text and icons, not color alone.
- Responsive layouts that avoid horizontal page overflow.
- Support for
prefers-reduced-motion. - Readable type sizes, line lengths, and contrast-checked colors.
- Code blocks and wide tables scroll inside their own containers.
- Native form controls and radio buttons for checkpoints and assessments.
Known limitations
- Some long code listings and wide tables require horizontal scrolling on small screens. This preserves the original formatting.
- Diagrams are preserved as preformatted text. Screen-reader output can be verbose; the surrounding lesson explains the same flow in prose.
- Google's sign-in page is operated by Google and is outside our control. Its accessibility is governed by Google's own statement.
- The final assignment is submitted by email. If email is a barrier, contact us to discuss an alternative.
Feedback
If you encounter a barrier, emailo30macademy@gmail.com with the page address and a description of the problem. We will review it and respond as soon as we can.
Assessment
Automated and manual checks are part of the release process. Results and any accepted limitations are recorded in the project's engineering report. This statement will be updated when the review is complete.