.wpmslider-controls .screen-reader-text {
display: none;
}But I’m wondering why this is suddenly happening?
]]>When I add a Divi Search module, there is no label for the Search form input field. I get “Missing form label” error. Does the Divi Accessibility plugin address this in a setting? I would like to add a label with a screen-reader-text class but because there’s no “label,” I’m not sure how to add the label or class to the field.
Have any of you come across this and found a solution?
Thanks so much for your assistance!
]]>I am not a coder so solving this problem has me completely bewildered. I’m using Nisag Theme (which I love) for my blog and I’m creating an RSS Feed auto email through Mail Chimp. The only problem is that the MailChimp software keeps thinking it should show the screen reader text “read more” so that my blog excerpts come up with the excerpt followed by a link saying “read more read more” which REALLY looks like a mistake. How do I hide the screen reader text? Please keep in mind that I have no coding or programming experience, so very specific instructions are necessary! Thank you so much!
]]><h2 class="screen-reader-text">some article title</h2>; for post navigation. Is it possible to change that <h2> by a single ?
Thank you
JB
[Moderator note: code fixed. Please wrap code in the backtick character or use the code button.]
]]>white-space: nowrap; to the screen-reader-text class.
]]>I’m running an RTL site and really like your plugin.
I’ve installed it, translated the needful to Hebrew (Thanks to Loco) and I was happy with it. For a few minutes at least.
Then I wanted to see it on my iPhone. And at start I thought the site broke. The page (only the ones where the Fancier Author Box was showing) was blank.
Then I noticed the screen was pushed deeper to the right. I add to massively scroll to the right in order to see the page.
I’ve fixed it by changing the plugin’s CSS from:
.screen-reader-text {
clip: rect(1px, 1px, 1px, 1px);
position: absolute !important;
left: -9999px;
}to:
.screen-reader-text {
clip: rect(1px, 1px, 1px, 1px);
position: absolute !important;
right: -9999px;
}Actually the only change is replacing the “left” with “right”.
Is there any chance to have a permanent fix so future versions won’t have the same issue (obviously they’ll override my CSS change).
Thanks in advance.
https://www.ads-software.com/plugins/fancier-author-box/
]]>the_content( sprintf(
__( 'Continue reading %s <span class="meta-nav">→</span>', 'twentyfourteen' ),
the_title( '<span class="screen-reader-text">', '</span>', false )
) );The variable %s (title) don’t appear because of the css class “screen-reader-text” which have “position: absolute !important;”
without this attribut it’s ok.
ligne 717 of style.css
For french : la traduction en “Continuer la lecture de” est donc malvenue. Le “de” ne servant à rien
]]>“Read More about {Title of the Page}…”
If so, that means your site does not support the .screen-reader-text CSS class. This class was required in all themes starting in WordPress 4.2.
What Is It?
Screen Readers are software used by visually-impaired website users to listen to the contents of a computer screen. When that computer screen is showing your website, it’s important we ensure people hearing the page get an equivalent experience to those looking at it!
“Read More” links, when implemented with just those two words, say nothing about where the link might go. Here’s a very short video of a screen reader speaking out “More” links.
This plugin uses an accessible read more link so that the link text contains the title of the page it links to. However, that title doesn’t need to be displayed to be spoken.
How to accessibly hide the text
As mentioned above, all WordPress themes are supposed to support the .screen-reader-text class; however, many don’t. If your theme doesn’t, you have two options:
It is important that you DO NOT USE display:none; or visibility: hidden; to hide the text as that would make the link inaccessible again.
Not Just This Plugin
This new theme CSS is required because WordPress now relies on it to output accessible website code in things like the search form and Category widget. In the future, other text will likely be included on your site with this same class. That’s why I did not include the CSS with this plugin and why your site will benefit in many ways from supporting it.
https://www.ads-software.com/plugins/feature-a-page-widget/
]]>It had been extensively tested on a variety of devices.
However, today we were shown a computer where the responsiveness is totally askew. (Windows 7, all the browsers display the same).
Here is what a blog archive looks like on this aberrant computer:
https://www.dropbox.com/s/vtphmbgobceiev2/broken.jpg?dl=0
This is what it is supposed to look like (and does virtually everywhere else):
https://www.dropbox.com/s/lxfzptzg0qpntv7/good.JPG?dl=0
Another symptom is that the screen reader text is visible in various places throughout the website.
Why would the website be behaving like this on this one computer? What would I need to test for in the code to display an alternate version to computers with whatever the limitation is on it?
]]>