Any node using this module fails WebAIM WAVE accessibility testing

It appears that this module's authors have gone to great pains to include ARIA accessibility features. The most popular tool for testing web pages for accessibility errors is WebAIM's WAVE accessibility testing tool. But when tested with this tool, any node using the Universal Share button will show two accessibility errors (links containing no text) and a further error (same) for each service button that is enabled with the default settings. It also generates over 100 WAVE alerts.

Both the current versions of the Drupal 7 and Drupal 8 modules display this issue, and my feature request is that the module be modified so that it no longer generates WAVE accessibility errors on pages where it is used.

This is an issue for developers of accessible web sites, as it is very useful to place a WAVE link within a site's theme (the URL http://wave.webaim.org/refer will send the page that it is on to WAVE for testing) so that site editors can easily evaluate that they have not created any accessibility issues when they publish new content on their sites.

I have created a very simple demonstration of this problem on http://testd8.hyperlink.ie/node/1 - on that page, if the link "Test this page with WAVE" is clicked, the problem is immediately apparent. I have used the module's defaults, other than disabling its use of external analytics services. While the service buttons could easily be fixed, the 2 errors caused by the main Share button can not.

The sources of the errors are easier to see within WAVE if its "no styles" option is selected.

The WAVE alerts are not so important, as Drupal's Bartik also generates some: these are mainly due to having 2 identical adjacent links, usually where a linked button icon and adjacent linked text both point at the same URL, as screen-readers can read the link twice, which can become tedious very quickly. Most of the current generation of screen-readers can deal with this automatically, and it can be difficult to avoid creating them, but if they can be avoided then they should be: for example, a linked 'print' icon only needs to have alt text to be "visible" both to sighted and blind people, but when the linked text "print" is placed beside it then this creates an accessibility alert, and the solution is best explained here: http://webaim.org/techniques/alttext/ - see Example 3, specifically its second part.

I would really appreciate it if you could take the matters that I have discussed above on board in a future revision of your module.