Kubeflow Dashboard UI - Address A11y Violations

[jenny-s51]

While theming the Model Registry UI for consistency with the Central Dashboard, we identified many accessibility issues using the Axe Chrome extension.

E.g. on the initial screen, there are 66 violations across various severity levels, including critical issues that affect fundamental accessibility. These issues violate WCAG guidelines and need to be resolved for improved screen reader support and keyboard navigation, among other accessibility requirements.

After pulling these style tokens into MR, a violation caused an error in our CI workflow (a color contrast issue), which we are addressing in this PR. However, the majority of the violations remain in the Kubeflow Dashboard UI.

The MR team is aware of these issues, and we’re prioritizing fixes to improve accessibility as we continue driving consistency between these UIs. We encourage the Kubeflow team to also prioritize accessibility in future UI changes cc @ederign

[ederign]

@jenny-s51 thank you so much for opening this. As example when there is a violation in MR here is how we break it via GHA:

We will do the same for Notebooks 2.0. (@paulovmr can you sync with @jenny-s51 and MR team to apply the same action there?)

@tariq-hasan I saw that you are planning to work on 'angular rewrite' of Dashboard. What do you think about adding same time of constraints there to make sure that we address eventual a11y issues?

[ederign]

Meanwhile, if someone is interested in community on working to fix accessibility issues on Kubeflow Central dashboard, just let me know. Those are usually low hanging fruits and excelent first time contributions!

[tariq-hasan]

@jenny-s51 thank you so much for opening this. As example when there is a violation in MR here is how we break it via GHA:

We will do the same for Notebooks 2.0. (@paulovmr can you sync with @jenny-s51 and MR team to apply the same action there?)

@tariq-hasan I saw that you are planning to work on 'angular rewrite' of Dashboard. What do you think about adding same time of constraints there to make sure that we address eventual a11y issues?

Sure. Will keep it in consideration @ederign.