man, I am not with it today - getting accessibility.cache.enabled mixed up

accessibility.force_disabled obviously exists - but, and I read a lot of bugzillas, I thought the rollout didn't take the force pref into account for some reason. That's not true AFAICT, and the pref was simply for the rollout (i.e to change from the old method to CtW)

So we have two options

• check on some aria test page that force_disabled still works, make it inactive, move it (it has no privacy/security implications) - maybe to personal
• remove it from the user.js and be done with it

I'm in favor of removing it. Class discuss