Accessibility

1. Accessibility Statement

Kanobo follows established web accessibility conventions to support a broad range of users. We review and update our interface for compatibility with assistive technologies as part of our routine product maintenance cycle.

2. Product Accessibility

This report describes the conformance of Kanobo with WCAG 2.1 Level AA standards.

Summary Table

Criteria	Level	Remarks
1.1.1 Non-text Content	Partially Supports	Most images and user avatars include `alt` text. Some decorative icons lack explicit labels.
1.3.1 Info and Relationships	Partially Supports	Basic form labels are present. Use of ARIA landmarks (main, nav) is currently limited.
1.4.3 Contrast (Minimum)	Supports	Standard interface uses high-contrast text (Black/White) on light/dark backgrounds.
2.1.1 Keyboard	Partially Supports	Native HTML elements (inputs, links) are keyboard accessible. Custom components may require mouse interaction.
2.4.1 Bypass Blocks	Does Not Support	No skip-to-content links are currently implemented.
2.4.4 Link Purpose	Supports	Links generally include descriptive text or tooltips.
3.1.1 Language of Page	Supports	HTML `lang` attribute is set to "en".
3.2.1 On Focus	Supports	Focus on elements does not trigger unexpected changes of context.
3.3.2 Labels or Instructions	Supports	Form fields generally include labels or placeholders.
4.1.2 Name, Role, Value	Partially Supports	Standard inputs are accessible; custom Vue components (e.g., Modals) lack full ARIA role definitions.

3. Current Accessibility Implementation Details

Based on a review of the codebase:

Alt Text: Consistently applied to <img> tags for user avatars, error graphics, and images (e.g., alt="avatar", alt="Empty", alt="Loading").
Form Labeling: Forms use standard <label> tags with for attributes linking to input IDs.
Tooltips: Navigation icons utilize v-tooltip to provide text descriptions for sighted users, though these may not be fully optimized for screen readers without additional ARIA attributes.
Language: The application is localized to English by default.
Semantic HTML: The application uses a mix of semantic tags and generic div containers. Transitioning to more semantic landmarks (e.g., <main>, <nav>) is a recognized area for improvement.