Improve Accesibility

[jalisaNT]

This is a Feature Request

Hi,

I ran the website through an accessibility site called EXPERTE. Most of the pages within the site had 89% rating. I would like to improve this / increase the rating to make the website even more accessible to users.

I would like be assigned this issue to improve this?

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dipesh-rawat]

Thanks for reporting this. Could you please explain why we should consider reports from EXPERTE and the significance of their reports compared to other available tools? Additionally, would you be able to list the specific issues (here) that were identified in EXPERTE's assessment?

/priority awaiting-more-evidence

[jalisaNT]

Why consider reports from EXPERTE and significance in comparison to other available tools: As EXPERTE is a free accessible site that does the following:

• It is able to crawl the entire site and provide feedback and a rating on the all pages checking accessibility of the navigation,ARIA, Labels, Contrast, Lists, multimedia, internalization and localization.
• It provides the file location of where the pitfalls take place.
• It provides a link to solutions and explanations of errors specifically from Duque university

List of most common accessibility issues with website :

• Buttons not having accessible names. Explanation : When a button does not have an accessible name, screen readers announce it as "button", which makes the attribute unusable by users who need screen readers
• Links not having discernible name. Explanation : link text and alt text when used as links, should have unique and clear which improves the navigation to make the links visible to screen readers
• The not enough of a colour contrast between the background and foreground colours
• The heading elements are not in sequentially descending order

[sftim]

Right now this issue isn't really actionable: someone can't come in and start work on an already-prioritized fix.

If you can identify pages that are obviously problematic, please file an issue for each page that needs to be more accessible. Ideally, validate the gaps with someone who typically uses an accessibility tool, or using an accessibility simulator.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.