• I am a user of Internal Link Juicer pro and I notice that this plugin continues to be affected by serious accessibility issues; if possible, there have been also some regressions.
    I am totally blind and use NVDA – NonVisual Desktop Access – screen reader – https://www.nvda-project.org
    The issues are many, but in this topic I report the main ones:

    Keyword adding:
    the control “add keyword” is not detected by the screen reader, as a button; pressing the Enter key currently works on “add keyword” wherever it appears, but it is not a standard button – please consider adding on that code, the role=”button” attribute and tabindex=”0″ attribute.
    Then:
    Removing a keyword once set, is now impossible. In a few versions ago it was possible by pressing the Enter key on a blank space before the keyword – screen reader cannot even detect the “x” sign, if it is as such.
    But now, screen reader intercepts the keywords, but it’s impossible to remove them with keyboard only.
    There are also many issues in the keyword interval interface, but as the inaccessibility is also in the documentation as there are many screenshots instead of texts explaining how to use it, I really do not understand how to use that function, as I do not see.
    I contacted you privately still in August when I bought the Pro version, you promised that you could fix issues but they became worse instead.
    I’ll not ask money back (it also may be too late) because I use the plugin every day and enjoy pro features. But, at least, do not discriminate blind customers in this way and solve those accessibility issues ASAP!
    WordPress core is accessibility compliant, Web Content Accessibility Guidelines 2.1 level AA (intermediate), why plugins shouldn’t be, especially paid ones?
    Thanks.

Viewing 1 replies (of 1 total)
  • Plugin Contributor Internal Links

    (@internallinkjuicer)

    Thank you for following up on this.

    We have already created an entry for this topic in our backlog. Until now, we have not had the resources to work on this (very important) topic. This goes along with a prioritization tied to a redesign of our user interfaces, where accessibility will have a prominent place. When a solution can be presented here, I cannot foresee at the moment. But we will keep you up to date in any case.

Viewing 1 replies (of 1 total)
  • The topic ‘Accessibility issues in adding and removing keywords’ is closed to new replies.