Avalonia Accessibility and Validation
Start with:
../../references/22-validation-pipeline-and-data-errors.md../../references/23-accessibility-and-automation.md../../references/60-automation-properties-and-attached-behavior-patterns.md
Load these when keyboard behavior is involved:
../../references/19-focus-and-keyboard-navigation.md
Workflow
- Define how validation state is surfaced in the viewmodel, control, and visual layer.
- Verify labels, focus order, and automation metadata together instead of as isolated fixes.
- Keep automation names, help text, and control relationships stable.
- Make the final accessibility contract easy to test.
Rules
- Prefer
INotifyDataErrorInfo-friendly flows for rich validation.
- Do not treat automation metadata as optional polish.
- Keep keyboard-only navigation credible before declaring a surface accessible.