I appreciated that the accessibility thing is called out as the top entry on the list of changes it makes you may want to override.

If it's genuinely just munching CPU if you don't use it, then turning it off by default with a warning that it's going to do that seems pretty reasonable.

(I've not tried their user.js and probably won't, but "realising the accessibility tools thing was important enough to go at the top even if the vast majority of users will care more about other entries in the list" seems like an indication that at least some thought has gone into this)

The first two prefs are commented out (using //) and are not in the user.js itself, and the latter two are in the user.js but are 1) easy to re-enable and 2) the repo indicates how to enable them if you need them. Please read the Github page.

* * *