Computing accessibilityIsIgnored is a significant source of runtime issues and it's also responsible for the major differences between Chrome and Firefox accessibility trees.
Let's try to first simplify it dramatically (fewer tests / rules), then consider just setting a flag in Blink and then optionally skipping ignored nodes on the Chrome browser side, if at all.
This will help with performance work, a lot of performance regressions trace back to accessibilityIsIgnored.
Comment 1 by bugdroid1@chromium.org
, Sep 30 2016