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.

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

Accessibility - check accessibility tree of all components #376

Closed
1 of 29 tasks
angelicahoyss opened this issue Sep 19, 2023 · 1 comment
Closed
1 of 29 tasks

Accessibility - check accessibility tree of all components #376

angelicahoyss opened this issue Sep 19, 2023 · 1 comment
Labels
🚫 blocked This issue is blocked ⭕ core team issue This is for the core team and should not be done by contributors ⌨️ dev issue Task is for developers

Comments

@angelicahoyss
Copy link
Contributor

angelicahoyss commented Sep 19, 2023

Description / User Story

The goal of this ticket is to check the accessibility tree of all components either manually or automatically and document the findings. This is a prerequisite for follow up tasks, that deal with fixing all the issues that were found.


Requirements


Acceptance Criteria


Background information

  • Lars T. raised a question in Define Accessibility Standard #2 that we may have should look into again:

    Can we provide accessible components without Typescript that enforces/forbids the use of cetrain props?
    Maybe we can only offer AA standard when the team also uses the Types for our components.

@thrbnhrtmnn thrbnhrtmnn added this to the Release 1.0 milestone Sep 29, 2023
@thrbnhrtmnn thrbnhrtmnn removed this from the Release 1.0 milestone Nov 15, 2023
@thrbnhrtmnn thrbnhrtmnn added the ⌨️ dev issue Task is for developers label Dec 1, 2023
@thrbnhrtmnn thrbnhrtmnn added the ⭕ core team issue This is for the core team and should not be done by contributors label Jan 5, 2024
@thrbnhrtmnn thrbnhrtmnn changed the title Accessibility - Test Accessibility of all Components in the First Release Accessibility - check accessibility tree of all components Jan 17, 2024
@thrbnhrtmnn thrbnhrtmnn added the 🚫 blocked This issue is blocked label Jan 17, 2024
@thrbnhrtmnn
Copy link
Contributor

It was decided to split this issue, the first one being #1020 with follow up tasks being created afterwards

@thrbnhrtmnn thrbnhrtmnn closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚫 blocked This issue is blocked ⭕ core team issue This is for the core team and should not be done by contributors ⌨️ dev issue Task is for developers
Projects
None yet
Development

No branches or pull requests

2 participants