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

title attribute is not accessible #4070

Open
dnz3d4c opened this Issue Nov 14, 2018 · 2 comments

Comments

3 participants
@dnz3d4c
Copy link

dnz3d4c commented Nov 14, 2018

I am using Kanboard with a screen reader.
When using Kanboard as a screen reader, it is inconvenient to access the document with the cursor of the screen reader because of the title attribute.
In many places, the title attribute mentions poor accessibility. You can replace it with an alternative solution through the following resources:

  1. https://a11yproject.com/posts/title-attributes/
  2. https://developer.paciellogroup.com/blog/2010/11/using-the-html-title-attribute/
  3. https://www.mediacurrent.com/blog/dont-rely-title-attribute-accessibility-seo/

Typically, the following elements of Kanboard are provided using the title attribute:

  1. default filter link in the search area
  2. Configure this project link

The title attribute may be used in more places. I hope this issue has been fixed and it will be easier to use Kanboard as a screen reader. Thank you.

@bugwatcher

This comment has been minimized.

Copy link
Collaborator

bugwatcher commented Feb 21, 2019

Please, use the forum for open discussions, suggestions and feature requests. This bug tracker is reserved only for bugs.

@Kolossi

This comment has been minimized.

Copy link

Kolossi commented Feb 21, 2019

The bug is that the title attribute is used when it should not be, which is an issue when using a screenreader - in the same way that there's always a subset of uses that lead to any bug.

OP has given good resources for someone to address this. If "bugwatcher" is automated, maybe that's why it thought it was a discussion?

I'd agree with OP that this is a bug and wish I had the time to address it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.