As clearly stated in the first post of this thread, Access Aide entire purpose is to make sure an epub meets the criteria for:
schema:accessMode: textual
schema:accessMode: visual
schema:accessModeSufficient: textual
schema:accessibilityFeature: structuralNavigation
schema:accessibilitySummary: This publication conforms to WCAG 2.0 AA.
schema:accessibilityHazard: none
It can NOT make this claim reliably for anything that includes media or javascript ( ie. movies, animations, or audio) as Access-Aide has no ability to see or hear if the media contains hazards such as quickly flashing images or loud noises that could induce seizures or other create potential accessibility or health hazards.
http://kb.daisy.org/publishing/docs/...ityHazard.html
That is why I limit its use to standard fiction epubs. There are human based ACE accessibility certification boards that can and will certify that an epub with those features do not present any hazards.
You can always run Access-Aide on early versions of the epub before adding in media and javascripts for animations to help fill in alt descriptions, update descriptions and semantic tags, but ... once media are added, you really should use a true certification service to make sure that there are no visual or audio hazards unless you are an expert in exactly which video or audio elements might present as hazards. I am not. Someone would have to hear and see every movie frame and audio, and watch any javascript created animation or movements.
Access-Aide itself, can not and will not make the claim there are no accessibility hazards, as it can not verify that.
If you want, I can create a version of Access-Aide that does NOT include the certification metadata. Then you can of course run it on anything, but you must then take the risks associated with whatever certification *you* decide to apply.