Release requirement
Accessibility
Vaylan UI treats accessible behavior as part of each public component contract.
Semantic markup
Buttons, links, tables, fields, progress, and native dialogs retain the correct browser semantics.
Keyboard access
Interactive controls remain reachable, operable, and visibly focused without a pointer.
Names and descriptions
Form labels, help text, errors, dialog titles, and loading states are connected programmatically.
Theme contrast
Semantic content tokens must remain readable on their paired backgrounds in every published theme.
State beyond color
Text, roles, exact progress values, and icons reinforce status colors.
Reduced motion
Motion must not be required to understand state and should honor the visitor's preference.
Consumer responsibilities
- Supply meaningful labels, link text, image alternatives, and table captions.
- Keep page heading levels and landmarks coherent.
- Use one primary action per context and avoid using badges for long explanations.
- Test application-specific flows with a keyboard and assistive technology.
- Validate custom theme contrast before release.