Accessibility Statement
Our Commitment
IncluSend LLC is committed to ensuring that Melaa is accessible to all users, including people with disabilities. We believe that every educator should be able to use our platform to support multilingual learners, regardless of ability.
Standards
Melaa is designed and developed to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We also strive to meet the accessibility requirements set forth by Colorado HB21-1110, which requires state and local government websites to meet WCAG 2.1 Level AA standards.
Accessibility Features
We have implemented the following accessibility features throughout Melaa:
Keyboard Navigation
- Skip-to-content link on every page to bypass repetitive navigation
- Visible focus indicators on all interactive elements
- All primary navigation, forms, and controls are operable via keyboard alone
Screen Reader Support
- Semantic HTML structure with proper heading hierarchy
- ARIA roles and labels where native semantics are insufficient (e.g.,
role="switch"witharia-checkedon toggles,aria-labelon icon buttons) - Live regions (
aria-live="polite") for dynamic content updates such as AI chat responses and form status messages - Descriptive alt text on all meaningful images
Color and Visual Design
- Color contrast ratios of 4.5:1 or higher for normal text
- Focus-visible outlines that meet contrast requirements
- Support for
prefers-reduced-motionto disable animations - Information is never conveyed by color alone-status indicators include text labels
Forms
- All form inputs have associated labels via
<label>withhtmlFor - Autocomplete hints on name, email, and organization fields in our contact and request forms
- Error messages are clearly identified and associated with their fields
Modals and Dialogs
- Our shared dialog component uses
role="dialog"andaria-modal="true", traps and restores focus, and closes on Escape - The Groups and tool menus on the teacher dashboard close on Escape and return focus to their trigger
- Close buttons include
aria-label="Close dialog". A set of secondary admin dialogs are being migrated to the shared component (see Known Limitations and Roadmap)
Responsive Design
- Content reflows at 320px viewport width without horizontal scrolling
- Content is readable and functional at 200% browser zoom
- Touch targets meet 24x24 CSS pixel minimum size
Known Limitations
We are aware of the following accessibility gaps and are actively working to address them:
- Secondary admin dialogs: Our shared dialog component and the primary teacher workflows trap and restore focus and close on Escape. A set of secondary admin dialogs are being migrated to that shared component to add Escape-to-close, focus trapping, and focus restore.
- Status announcements in admin: The AI assistant and primary forms announce status via ARIA live regions. Some admin save and confirmation messages are shown visually but are not yet wrapped in a live region; we are adding
role="status"/role="alert"to those. - Color contrast: An August 2026 remediation darkened gray secondary text, link/accent pink, and status green across the teacher and district-admin surfaces to meet 4.5:1. A small number of secondary-text and marketing-link instances remain below the threshold and are scheduled.
- Data tables: Public-facing tables (including this VPAT and the subprocessor tables) include
<caption>andscope. Some in-app admin data tables do not yet include a<caption>, and sortable column headers do not yet exposearia-sort. - Animated content: The homepage product demo is a CSS/JavaScript animation that automatically stops for visitors who enable the "reduce motion" setting. It does not yet offer an on-page play/pause control for visitors who have not set that preference; we plan to add one.
- AI-generated content: The AI Thought Partner generates instructional recommendations in markdown, rendered with semantic HTML. The structure of AI-generated responses may vary and may not always follow an ideal heading hierarchy.
Voluntary Product Accessibility Template (VPAT)
The following VPAT Version 2.5 documents Melaa's conformance with WCAG 2.1 Level AA as of August 28, 2026.
Product Information
Product:Melaa (melaa.app)Version:1.0Report Date:August 28, 2026Company:IncluSend LLCContact:support@melaa.app
Applicable Standards
- WCAG 2.1 (Level AA) - Included
- Revised Section 508 - Included (WCAG 2.1 mapping)
- EN 301 549 - Not evaluated
Conformance Terms
- Supports: At least one method meets the criterion without known defects.
- Partially Supports: Some functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.1 - Level A
| Criteria | Level | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | All images include alt text. Decorative images use empty alt attributes. |
| 1.2.1–1.2.3 Audio/Video | N/A | Application does not include audio or video content. |
| 1.3.1 Info and Relationships | Supports | Semantic HTML: headings hierarchy, form labels, landmark regions, lists, and tables with headers. |
| 1.3.2 Meaningful Sequence | Supports | Logical reading order. DOM order matches visual presentation. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely solely on shape, size, visual location, or sound. |
| 1.4.1 Use of Color | Supports | Color is not the sole means of conveying information. Status indicators use text labels. |
| 2.1.1 Keyboard | Partial | The shared dialog and the primary teacher workflows (student list, groups, AI assistant, generation tools) are fully keyboard operable; the Groups and tool menus close on Escape. Gap: a set of secondary admin dialogs are being migrated to the shared dialog to add Escape/focus handling (see Roadmap). |
| 2.1.2 No Keyboard Trap | Partial | Most components navigate freely. Gap: some modal dialogs do not implement focus trapping. |
| 2.2.1 Timing Adjustable | Supports | No time limits imposed. Session uses standard auth token refresh. |
| 2.2.2 Pause, Stop, Hide | Partial | Loading indicators auto-stop, and the homepage product demo (a CSS/JS animation, not a GIF) pauses under prefers-reduced-motion. Gap: it does not yet offer an on-page pause control for visitors who have not enabled reduced motion. |
| 2.4.1 Bypass Blocks | Supports | Skip-to-content link on all pages. |
| 2.4.2 Page Titled | Supports | All pages have unique, descriptive titles via Next.js metadata. |
| 2.4.3 Focus Order | Partial | Focus order follows a logical sequence, and the shared dialog moves and restores focus. Gap: some secondary admin dialogs do not yet move focus in on open or restore it on close (see Roadmap). |
| 2.4.4 Link Purpose | Supports | Link text is descriptive or provides context through surrounding content. |
| 2.5.1–2.5.4 Pointer/Motion | Supports | Single-point activation only. Standard up-event behavior. No motion-triggered features. |
| 3.1.1 Language of Page | Supports | lang="en" set on root HTML element. |
| 3.2.1–3.2.2 On Focus/Input | Supports | No unexpected context changes on focus or input. Submission requires explicit action. |
| 3.3.1 Error Identification | Supports | Validation errors displayed as visible, descriptive text messages. |
| 3.3.2 Labels or Instructions | Supports | All form inputs have associated labels. Required fields are indicated. |
| 4.1.2 Name, Role, Value | Supports | Standard HTML elements. Toggle switches use role="switch" and aria-checked. |
WCAG 2.1 - Level AA
| Criteria | Level | Remarks |
|---|---|---|
| 1.2.4–1.2.5 Captions/Audio Desc. | N/A | No live or prerecorded audio/video content. |
| 1.3.4 Orientation | Supports | Content is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose | Supports | Input fields use appropriate type and autocomplete attributes. |
| 1.4.3 Contrast (Minimum) | Partial | Primary text meets 4.5:1 (body #211826 / secondary #4a3f4d on #ffffff). Following an August 2026 remediation, gray secondary text was darkened to #6b7280, link/accent pink to #C4165A, and status green to #166534 across the teacher and district-admin surfaces. Gap: a small number of secondary-text and marketing-link instances remain (see Roadmap). |
| 1.4.4 Resize Text | Supports | Text resizable to 200% without loss of content or functionality. |
| 1.4.5 Images of Text | Supports | No images of text (except the product logo, which is exempt). |
| 1.4.10 Reflow | Supports | Content reflows at 320px without horizontal scrolling. |
| 1.4.11 Non-text Contrast | Supports | UI components meet 3:1 contrast against adjacent colors. |
| 1.4.12 Text Spacing | Supports | Content remains readable with modified text spacing. No clipping or overlap. |
| 1.4.13 Content on Hover/Focus | Supports | Hover content is dismissible, hoverable, and persistent. |
| 2.4.5 Multiple Ways | Supports | Navigation via top menu, skip link, direct URL, and sidebar. |
| 2.4.6 Headings and Labels | Supports | Headings describe sections. Labels describe input purpose. |
| 2.4.7 Focus Visible | Supports | Browser default focus indicators preserved. Custom styles applied where defaults are overridden. |
| 2.4.11 Focus Not Obscured | Supports | Focused elements are not hidden by fixed headers or other content. |
| 2.5.7 Dragging Movements | Supports | No drag-based interactions required. All functionality uses single-point actions. |
| 2.5.8 Target Size (Minimum) | Supports | Interactive targets meet 24x24 CSS pixel minimum. |
| 3.1.2 Language of Parts | Supports | Content is in English. No mixed-language content. |
| 3.2.3–3.2.4 Consistency | Supports | Consistent navigation order and component identification throughout. |
| 3.3.3 Error Suggestion | Supports | Correction suggestions provided for detected input errors. |
| 3.3.4 Error Prevention | Supports | Destructive actions require confirmation. Data is reviewable before submission. |
| 3.3.7 Redundant Entry | Supports | Previously entered information is auto-populated where applicable. |
| 3.3.8 Accessible Auth | Supports | Sign-in is single sign-on only (Google, Microsoft, ClassLink) - no password or memory/transcription test is required. |
| 4.1.3 Status Messages | Partial | The AI assistant (generation start and completed response) and the primary forms announce status via ARIA live regions (role="status"/aria-live). Gap: some admin save and confirmation messages are being wrapped in live regions (see Roadmap). |
Testing Methodology
- Manual: Keyboard-only navigation, screen reader testing (VoiceOver on macOS)
- Automated: Lighthouse accessibility audit, axe-core browser extension
- Color: WebAIM Contrast Checker
- Responsive: Tested at 320px, 768px, 1024px, and 1440px viewports
Accessibility Roadmap
We are committed to closing the gaps above. The table below lists our planned remediation with target windows and interim workarounds. We review and update this VPAT at least annually in accordance with Colorado 8 CCR 1501-11, and we assess Melaa against the U.S. Department of Justice ADA Title II web and mobile accessibility rule, Colorado HB 21-1110, and Colorado HB 25-1152.
| Item | WCAG | Status | Target | Interim workaround |
|---|---|---|---|---|
| Migrate remaining secondary admin dialogs to the shared accessible dialog (Escape, focus trap, focus restore) | 2.1.2, 2.4.3 | In progress | Q4 2026 | Dialogs are labeled and operable by mouse and keyboard; dismiss via the close control. |
| Wrap remaining admin save and confirmation messages in ARIA live regions | 4.1.3 | In progress | Q4 2026 | Confirmations are visible on screen after each action. |
| Complete color-contrast pass on remaining secondary text and marketing links | 1.4.3 | In progress | Q4 2026 | Core teacher and district-admin workflows already meet 4.5:1. |
| Add captions/scope and aria-sort to remaining in-app admin data tables | 1.3.1, 4.1.2 | Planned | Q1 2027 | Tables have visible column headers. |
| Add an on-page play/pause control to the homepage demo animation | 2.2.2 | Planned | Q1 2027 | Animation stops automatically when the visitor's "reduce motion" setting is enabled. |
Reporting Accessibility Issues
We take accessibility feedback seriously. If you encounter any barriers while using Melaa, please let us know so we can address them. You can report accessibility issues through our contact page or by emailing us directly. Please include a description of the issue, the page where you encountered it, and the assistive technology you were using (if applicable).
Contact Us
If you have questions or concerns about accessibility, please contact us: