morriscountynj

Thank you!

Thank you!!

done! ??

Awesome! Thank you so much!

Thanks for responding!

I cleared the autoptimize cache (as well as cloudflare), but am still getting the same issue.

At the top right, in the header, you’ll see a little search widget with two options: Library Catalog and Site Search. If you click on Site Search, the search bar that appears is Ivory Search.

My apologies for not getting back!

Try this out, working on my end:

includes/emailpetition.php

line 272 is originally:
<a name="' . $petition->id . '" class="dk-speakout-submit"><span>' . stripslashes( esc_html( $options['button_text'] ) ) . '</span></a>

CHANGE IT to:
<button name="' . $petition->id . '" class="dk-speakout-submit">' . stripslashes( esc_html( $options['button_text'] ) ) . '</button>

I don’t think so, but was wondering if you had any ideas why the site went down via Simple History, or any steps I can take to avoid it in the future.

I tried via specificity a few times, but nothing seemed to work. The important! declaration did do the trick, however, thank you!

And for reference, the plugin code I’m referring to is

$output = "<h3 class='azc_tsh_toggle$expand_active' style='$border$background_title$disable_image'><a href='#' style='$title_color$title_font$title_font_size$title_font_weight'>$title</a></h3>";

this is what I have to change manually, I’d love a more sustainable way of doing this.

• This reply was modified 6 years, 12 months ago by morriscountynj.

Hi again ??

So for reference, here’s a link to an accessibility survey of the page, and the issue that comes up: https://accessibility.page.report/GBXGDGIFJJABIHIIAUFJ/473035/22656539416#automatic/3.2.2/52

It suggests either two things — making the submit link into a button, or adding a WAI-ARIA role to the link.

I did a little testing (you should try on your end too). It looks like the submit functionality of the form is depending on there being an link, so using an <input> didn’t work.

I believe that one of these two solutions would do the trick. I’m no expert though so take a look ??

ok added the issue there. thank you!

No trouble!

I was advised by the accessibility expert at Siteimprove to remove them.

Also referring to this article: https://www.sitepoint.com/avoiding-redundancy-wai-aria-html-pages/

As well as this, from the spec:

7.4. Implicit WAI-ARIA Semantics

WAI-ARIA is designed to provide semantic information about objects when host languages lack native semantics for the object. WAI-ARIA is designed, however, to provide additional semantics for many host languages. Furthermore, host languages over time can evolve and provide new native features that correspond to WAI-ARIA features. Therefore, there are many situations in which WAI-ARIA semantics are redundant with host language semantics. These host language features can be viewed as having “implicit WAI-ARIA semantics”. User agent processing of features with implicit WAI-ARIA semantics would be similar to the processing for the WAI-ARIA feature. The processing might not be identical because of lexical differences between the host language feature and the WAI-ARIA feature, but generally the user agent would expose the same information to the accessibility API. Features with implicit WAI-ARIA semantics satisfy WAI-ARIA structural requirements such as required owned elements, required states and properties, etc. and do not require explicit WAI-ARIA semantics to be provided. For example, if an element with the functionality already exists, such as a checkbox or radio button, use the native semantics of the host language. WAI-ARIA markup is only intended to be used to enhance the native semantics (e.g., indicating that the element is required with aria-required), or to change the semantics to a different purpose form the standard functionality of the element.

great, thanks ??

strangely enough, it seems to be working fine now, without the error. if it pops up again i’ll post here.

I think I’m confused by

So if you use the plugin or not, with your setup you cannot use SSL on your root domain, due to the way browsers handle this.

Do you mean that I just can’t use SSL? Or that it’s an all-or-nothing proposition – once I install SSL on the root domain, it’s there for all subfolders?