-
Notifications
You must be signed in to change notification settings - Fork 123
Accessibility Guideline
Arlo Godfrey edited this page Mar 12, 2024
·
1 revision
We'll follow this guideline to ensure the basic accessibility features for each control.
- Controls must support the 4 high contrast themes by default on Windows, in addition to changing the theme while the app is running.
- Controls must have a contrast ratio of at least 4.5:1 between the text (and images with text) and the background behind it.
- Controls must support keyboard navigation (tabs and arrow keys), the tab order must be the same as the UI and non-interactive elements mustn't be focusable.
- Composite elements must ensure proper inner navigation among the contained elements
- Clickable UI elements must be invokable with the keyboard (The trigger keys are enter and space).
- Focusable elements must have a visual focus indicator. It's usually a rectangle shape around the control's normal bounding rectangle.
- Controls must support the Narrator.
- We are following the coding guidelines of .NET Core Foundational libraries. See Coding Style and Conventions.
The Accessibility Insights tool can help with identifying some of these concerns.

- Home ๐
- Welcome ๐
- Principles โ๏ธ
- Roadmap ๐บ
- .NET Foundation
- Why Microsoft supports this project
- License ๐
- Getting Started ๐
- Sample App ๐ฑ
- NuGet Packages ๐ฆ
- Preview Packages ๐
- Toolkit Labs ๐งช
- Questions โ
- Discussions ๐ฅ
- Submitting an Issue โ๏ธ
- Good First Issue ๐
- Help Wanted ๐
- Bug Fixes ๐
- Feature Requests ๐ซ
- Component Quality Evaluation ๐ฎ
- Create and Submit PullRequest ๐
- Documentation ๐
- Review PR ๐
- Avoid Roadblocks ๐ง
- Required Dependencies ๐
- Quick Start โก
- Sample Development ๐ฑ
- Testing ๐งช
- Accessibility Guideline โฟ
- Coding Style and Conventions โ
- Building XAML Controls ๐
- CI and Infrastructure ๐พ
- Updating ToolkitLabs.dev ๐
- Migration Guide from v7 to v8 ๐
- How the Project is Organized ๐๏ธ
- Join the Toolkit Organization ๐ช
- Hall of Fame ๐