Generating WCAG Compliant Output

I agree the tool is imperfect and our scans require additional review, however, I think many of these problems still need addressed. Any component needs to communicate its identity and state to assistive technology. With native elements, that’s more straightforward, but in Robohelp output just about every clickable item outside of the iframe is dependent on Java elements, so ARIA is required to bridge the gap. If that’s the case, then I’d assume the ARIA should be on-point with WCAG standards. Also, the examples do have links. Every item in the TOC and navigation buttons are technically links, however, they’re constructed using Java commands in order to be dynamic. Most “buttons” are also anchor tags wrapped in divs, so I would expect it to flag a missing href on those.

I suppose I’d just like some more basic guidance from Adobe on the accessibility front because as it stands, out of the box, bog-standard stuff like the skip-to button on these sites doesn’t even function properly. Yes, they exist, but you should be able to select the link from first keyboard tab press and right now you need to shift+tab up until you get to it since it always focuses at the top of the TOC (when TOC is your default tab).