Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Accessibility] Accessibility requirements should be indicated per-control #1230

Open
citelao opened this issue Mar 25, 2023 · 0 comments
Open

[Accessibility] Accessibility requirements should be indicated per-control #1230

citelao opened this issue Mar 25, 2023 · 0 comments
Labels
accessibility Issues related to accessibility enhancement Expand an existing sample or add feature to app help wanted Extra attention is needed

Comments

@citelao
Copy link
Contributor

citelao commented Mar 25, 2023

Which version of the app?

WinUI 3 Gallery

Description

Certain controls always have specific accessibility requirements—for example, TextBoxes and Images (and typically *Views) always need an accessible name.

We should be explicit and add that information to the examples for each page. For example, we should indicate that requirement on the TextBox page and the Image page (not just the Screen reader page).

Screenshots

No response

Windows version

No response

Additional context

No response
@citelao citelao added the bug Something isn't working label Mar 25, 2023
@bpulliam bpulliam added the accessibility Issues related to accessibility label Apr 19, 2023
@karkarl karkarl added help wanted Extra attention is needed enhancement Expand an existing sample or add feature to app good first issue and removed bug Something isn't working labels Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accessibility Issues related to accessibility enhancement Expand an existing sample or add feature to app help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@citelao @bpulliam @karkarl