Rian Rietveld

Hi Nir,

The Hebrew translation has been added to the new plugin update (version 1.1)

Hi Gerxke,

The plugin just has been updated to version 1.1. This version should work better with the new Genesis 2.1. Your site looks allright to me, but can you test it also on your own device?

Rian

Hi jouielovesyou,

Change the default form from:

<p>Your Name (required)<br />
[text* your-name] </p>
><p>Your Email (required)<br />
[email* your-email] </p>
<p>Subject<br />
[text your-subject] </p>
<p>Your Message<br />
[textarea your-message] </p>
<p>[submit "Send"]</p>

into (for example):

<fieldset>
<label for="name">Name (required)</label>
[text* your-name id:name]
<label for="e-mail">Email address (required)</label>
[email* your-email id:e-mail]
</fieldset>
[submit "I want your newsletter"]

More on:
https://blog.rrwd.nl/2014/03/01/how-to-set-up-an-accessible-form-using-contact-form-7-in-wordpress/

Hi Nir,

Thanks for using my plugin.

There is standard no RTL css delivered with Genesis Framework, but you can add that easily yourself, see

• https://codex.www.ads-software.com/Right-to-Left_Language_Support
• https://www.warriorforum.com/website-design/550930-how-change-genesis-child-theme-into-rtl.html

At the moment I’m setting up the GlotPress for the plugin. If you mail me directly, I will give you access. (for my e-mailaddress see https://genesis-accessible.org/about/).

About the .search-form input[type=”search”]
You are right, I have to look into that and change it in the next update.
What you can do for now is change for example your css:

/* Display search button */
.search-form .search-form input[type="search"] {
here your different settings
}

So add an extra class before .search-form input[type=”search”]
This will overrule the style in genwpacc-skiplinks-style.css

Hi Srarden,

Thanks for posting this.
We discussed this issue in the Accessibility team chat.
Joe Dolson investigated this and his conclusion was the following:

I don’t believe that WordPress provides the iframe if there is one; that appears to be provided in the rich OEmbed object received from the source. In which case, if there’s a problem, it’s not one that can be easily fixed by WordPress.

Hypothetically, WP could filter the HTML returned in the OEmbed object to add a title, but that would be some very fragile code, dependent on the source API not changing their HTML. Probably not a good idea to attempt.

So this is out of WordPress hands I’m afraid.

Hi Gerxke,

Thanks for the feedback, I will look into it!

Rian

Ni Nir,

Your feedback will be much appreciated.
What is needed most is testing, finding accessibility issues still there. If you find anything, please let me know. Maybe it can be fixed and/or implemented in the plugin.

Hi Nir,

The plugin works for Genesis 2.0 and higher, so to works for child themes compatible from Genesis 2.0 (preferable 2.0.2)
Because the plugin changes the heading structure, the headings of some child themes may look different after installing the plugin.
If that is a problem you can disable the headings changes in the options of the plugin.

Kind regards,
Rian

Hey Takayuki,
Tested the functionality and it works very good. Thanks!

Hi,

Found what was wrong:
I loaded the jquery-ui wrong, in the header via the Genesis theme options
<script src="//code.jquery.com/ui/1.10.4/jquery-ui.js"></script>

after adding it in my theme’s php like
wp_enqueue_script('jquery-ui', '//code.jquery.com/ui/1.10.4/jquery-ui.js', array('jquery'), '1.10.4', true);
it worked.

Hi all,

Is there already a solution for this? I’m having the same problem. The search suggestions are unreachable.
ul.ui-autocomplete changes from display: block; into display: none; after trying to select the suggestions.

This occurred after adding the jquery range-slider
https://jqueryui.com/resources/demos/slider/range.html

The range slider only needs one extra (inline) script like

<script>
	$(function() {
		$( "#slider-range" ).slider({
			range: true,
			min: 0,
			max: 500,
			values: [ 75, 300 ],
			slide: function( event, ui ) {
				$( "#amount" ).val( "$" + ui.values[ 0 ] + " - $" + ui.values[ 1 ] );
			}
		});
		$( "#amount" ).val( "$" + $( "#slider-range" ).slider( "values", 0 ) +
			" - $" + $( "#slider-range" ).slider( "values", 1 ) );
	});
	</script>

But the two shares css classes

Range slider e.g.:
<div id="slider-range" class="ui-slider ui-slider-horizontal ui-widget ui-widget-content ui-corner-all" aria-disabled="false"><div class="ui-slider-range ui-widget-header ui-corner-all" style="left: 10%; width: 80%;"></div><a class="ui-slider-handle ui-state-default ui-corner-all" href="#" style="left: 10%;"></a><a class="ui-slider-handle ui-state-default ui-corner-all" href="#" style="left: 90%;"></a></div>

Kind regards,
Rian

This is great, thank you Joe!

Takayuki Miyoshi, you are the best!
Thank you for adding more accessibility to cf7, this is much appreciated.

Thanks ??

Sorry, maybe i did’t write it clearly enough
Your code does that by itself when I move the [response] to the top op the form.
Thanks to
https://phptechnologytutorials.wordpress.com/2014/01/09/remove-empty-p-tags-from-contact-form-7/
I found the option define ( ‘WPCF7_AUTOP’, false );
I know… RTFM…
But maybe you want to add a line to wpcf7_autop() preventing adding a p before a div