Quote Originally Posted by dbltoe View Post
It looks as if you have the problems identified in WebAIM solved.

It should be noted that the problem was identified as an empty button which is not fixed by adding a title. The lack of title or label would probably be identified when/if the button had some text. Having an ID for each MAY have eliminated the need for a title or label.

Code:
<button type="button" id="cboxPrevious"></button>
is one example and should probably, as a minimum, be
Code:
<button type="button" id="cboxPrevious">Previous</button>
The reason they were not seen in the text of the page and were seen by the tool is that the surrounding div was display:none.

display:none does NOT keep some accessibility tools or Search Engines from "seeing the code" that is hidden in the background of your browser.
What I have found interesting is that the browser being used to run the WAVE check makes a difference.

When using microsoft edge no problem is reported in this area, so far when using Google Chrome, the error was identified but also the title content wasn't carried over. In part not sure if there is some caching involved through the process. As to an ID being present, thus far all cases of a problem "empty button" have included an ID, so I would say that particular theory doesn't apply in WAVE's evaluation.

Continuing to look into ways to modify the js code to produce more globally acceptable accessibility results.