Accessibility, often shortened to a11y, makes an interface usable when visual cues alone are unavailable. Screen readers can replace or supplement visual use, so controls need metadata that communicates meaning, hierarchy, and purpose. section 2.3
In .NET MAUI, semantic properties provide this metadata for assistive technologies. A heading’s semantic level can tell a screen reader both its text and its place in the interface hierarchy. section 2.3
Build accessible UI by supplying information that sighted users might otherwise infer visually:
- Describe meaningful images so a screen reader can communicate their content. section 2.3
- Add hints that explain what input is expected and how entered information will be used. section 3.2
- Do not rely on color alone for errors or success; use color and contrast to improve readability alongside other cues. section 3.2
- Use WCAG 2.1 guidance when designing visually accessible interfaces. section 2.3
Describe a name entry field
An Entry can expose a placeholder for the visible UI and a SemanticProperties.Hint for assistive technology. Keep the hint aligned with the displayed instruction, such as explaining that the entered name will be used when sharing a location. section 3.2
<Entry #1
Placeholder="Enter your name" #2
SemanticProperties.Hint="Enter your name to be used when sharing location"
HorizontalOptions="Center"
x:Name="UsernameEntry"/> #3
This Entry shows a visible placeholder paired with SemanticProperties.Hint, giving screen-reader users a fuller explanation of the requested name. section 3.2
