Web Accessibility Errors for Download Buttons

This is not a unique or custom problem with our installation specifically, but an overall accessibility issue within your own plugin. Please see your own Demo pages as an example: https://try.wpdownloadmanager.com/list-packages/. Any time there is a button on the frontend from your plugin (“View More”, “Download”, “Add to Cart”, “Details”, etc.), you need to apply a unique, contextual “aria-label” attribute to it with more context for screen readers. Otherwise, it fails basic WCAG compliance (https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html). Having a long list of files with the exact same “Download” labeled button one after the other does not provide enough context to users and screen readers on what that link/button will actually do or which file it will download. I’ve just manually added an aria-label=’Download {$post_vars[‘title’]} file’ to your code mentioned to remedy this and fix this accessibility issue temporarily. The preference would be the plugin actually gets fixed and updated throughout for this specific accessibility issue though. Thank you!

Thank you. Yes, the Link Label would work for a small number of items to make them unique and add context. However, we currently have 700+ documents, so manually adding a custom label or copy/paste the title individually is not a great option. Ideally, the default plugin settings without a custom Link Label should be accessible out of the box. Please add to your future release.

That add-on looks interesting for initial default settings for new or copied downloads, but I already have 700+ documents input so isn’t helpful in this case. This also still does not fix the WCAG accessibility issue (2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) ). Each download link/label needs to be contextual and different from the others around it. You would need to be able to apply the document title dynamically for this to be a manual solution. Why not just take this as a future suggestion to make your plugin web accessible by default?

Thanks for clarifying. Please understand the actual accessibility issue though. It is not good enough to just apply the exact same link label text on all of my links either. They have to all be different from each other to comply. This is not accomplished with a single bulk update unless I can use some dynamic shortcode or way to use the document’s title within the label (like “Download {{Post_Title}} file”). Understand?