Accessibility

1. Our Commitment

Meneris is built for students, and students have a wide range of abilities. We want everyone to be able to use this product, including people who navigate by keyboard, use a screen reader, rely on magnification, or need reduced motion. We treat accessibility as part of building the product, not as an afterthought.

2. Standard We Aim For

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. These are the guidelines most widely referenced as the benchmark for accessible web content, and they are what we measure ourselves against.

3. What We Have Done

• Every interactive control shows a clearly visible focus indicator when reached by keyboard, so you can always tell where you are on the page.
• A "Skip to main content" link is the first item in the tab order on every page, so you do not have to move through the navigation each time.
• Pages use proper landmarks and heading structure so screen readers can navigate by region and heading rather than reading top to bottom.
• Form fields have programmatically associated labels, and buttons that show only an icon carry an accessible name.
• Status changes that happen without a page reload — setup progress, errors, queue position — are announced to screen readers rather than only appearing visually.
• If your system is set to reduce motion, animations and transitions are suppressed.
• The interface does not rely on colour alone to communicate state; colour is always paired with text or an icon.

4. Known Limitations

We would rather tell you where we fall short than claim we are perfect. As of the date above, we know about the following:

• Auto-submit sign-in: Connecting auto-submit streams a live view of a real browser window so you can sign in to Google yourself. That view is a video-like stream and is not usable with a screen reader. Auto-submit is entirely optional — every other part of Meneris works without it, and you can always turn work in yourself. If this step is a barrier for you, contact us and we will help you complete it another way.
• Third-party content:Google Docs and Google Classroom are Google's interfaces, not ours. We cannot change their accessibility, though we do link out to them rather than trapping you in a wrapper.
• Formal audit: Our conformance work to date is internal. We have not yet commissioned an independent third-party accessibility audit.

5. Tell Us About a Problem

If any part of Meneris is difficult or impossible for you to use, please tell us. You do not need to know why it is broken or use any particular terminology — describe what you were trying to do and what happened.

Email menerissupport@gmail.com with "Accessibility" in the subject line. We aim to acknowledge within 5 business days and will tell you what we intend to do and roughly when.

If it would help to have the same information another way — a document read out, a setup step completed with you, or an alternative to a step you cannot complete — say so and we will arrange it.

6. Assistive Technology We Test With

We test keyboard-only navigation and screen reader output on the browsers our students actually use. If you rely on a configuration we have not covered and something does not work, that is useful information — please report it using the contact above.