-
Notifications
You must be signed in to change notification settings - Fork 80
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 π«
- 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 π