Can you describe the issue, and provide a link to the site?
Very simple. After upgrading, my site turned LTR. I managed to fix it by body { direction: rtl; }.
I disabled the plugin, so there is no use of a link.
Your entire site turned LTR? That’s — incredibly strange. WP Accessibility doesn’t do anything to adjust the text direction; the only application of ltr/rtl in WP Accessibility is detecting what your site currently is (based on the language in WP config), and adding some classes to its own code on that basis.
It would be helpful to see the issue; but I understand if you’ve chosen to disable the plug-in.
Look at this website. Same problem, and plugin is on.
Link (temp)
It looks like the site’s default language is English, so WP Accessibility is injecting the default language into the HTML tag. That’s not at all new, however, so I don’t know why that would have caused a change in an upgrade.
However, you should turn that feature off; it won’t help you with a multi-lingual site.
It’s just a WPML feature, changing to English according to your browser language. Delete the /en/ from the URL to see the Hebrew site, which is LTR.
Yes. That’s why I’m saying you should disable that feature in WP Accessibility; it’s the only thing in WP Accessibility which has any impact on ltr/rtl behavior, and you can’t benefit from it, because the setting it’s based on is being overridden by WPML.
Come on, it only redirects. And the first install was Hebrew.
Now I removed WPML, and it still has this issue. Did you check on a clean RTL WordPress installation?
I don’t think you understand what I’m asking you to do; I don’t want you to change anything about WPML. WPML is fine.
Go to the WP Accessibility settings, and disable the option with the label “Add Site Language and text direction to HTML element”.
It was turned off. Turning it on actually fixed the problem, but I don’t think it is the right solution.
If turning that on fixed the problem, then WP Accessibility may not be the problem. What is the language attribute in your theme’s header.php file?
I’ll be damn. I tried to recreate the problem on a clean WordPress install, and it worked fine.
I owe you an apology!
Quite all right. I’m glad it’s something else!
