dtwx

This string

@daniellaivanova – is there a list of all the filters somewhere? I don’t want to make a post in support if the thing I need is already supported!

Seems to have fixed itself.

I changed a setting in the backend, it lost a bunch of the settings, so I re-applied them.

Basically, until that, it looks like it was just reading all the posts “as too long” and sending them as links.

Now it’s sending the content as expected.

• This reply was modified 1 year, 7 months ago by dtwx.

But it is only the first element on the page if other tabindex have been set starting at 1 or higher and this is bad practice for accessibility reasons:

https://webaim.org/techniques/keyboard/tabindex

In a properly formatted, accessible page, everything should be tabindex=”0″ and the elements should be arranged logically/in “reading order”. That way, when you tab through, from top to bottom, the order will aways be correct.

I don’t want to be a d!ck but if you keep tabindex set >0 in your plugin you’re favouring developers who’ve made web pages that aren’t accessible at the cost of those that have made accessible pages.

I guess you could add a setting for each instance to set the tabindex to 0? That’d be simpler than letting people set their own tabindex, I think?

• This reply was modified 2 years, 1 month ago by dtwx. Reason: Added suggestion

In a very similar vein, it would be good to have aria-hidden="true" on the class="innericon" <div>’s – accessibility checkers think the icon is an unlabelled image.

Good work! You’re right that we probably shouldn’t have that call to the_meta(), so I did remove it, but I knew yarrp must be doing something “wrong” because otherwise we would have seen similar before.

Thanks for checking it out!

Fixed in 5.7.9 without any changes from me.

Have fixed everything except the The called constructor method for WP_Widget... messages because I simply don’t understand why that is appearing. I fixed all the constructor methods in June and the server is running PHP 7.3 and everything works… ?

However, when I enable minify HTML it still breaks completely.

Oh, I see! It takes the existing <textarea>s and modifies them. Yes, I probably should have checked my own code first… Thanks for the pointers!

Also, I notice that you have type="text/javascript" declared in some scripts. WCAG warns about that too. Not the end of the world.

Thanks, I can confirm the change works. My before and after code is shown.

However, this doesn’t do what I expected. I didn’t expect this code to be placed before title. I expected it to be placed after title but before the pagination links. The FAQ may need rewording.

Thanks again!

Thanks, it’s here: https://www.staging2.healthwatchbucks.co.uk/category/news/

I’ve marked the section with <!-- mobile wp-paginate -->

Excellent, thanks! That function didn’t exist when you started the plugin. I imagine it’s hard to account for that sort of evolution unless you’re working on something fulltime.

And thanks for making/maintaining the plugin!