Forum Replies Created

Viewing 30 posts - 1 through 30 (of 158 total)

Hi all – any thoughts?

in reply to: 404 page search field accessibility issue #1423326

Hi anyone have any ideas?

in reply to: Add H1 heading to category/archive pages only. #1422041

Sorted it – did this:

				<main class='content <?php avia_layout_class( 'content' ); ?> units' <?php avia_markup_helper( array( 'context' => 'content', 'post_type' => 'post' ) );?>>
				<div class="archive-header" style="text-align: center;"><h1><?php post_type_archive_title(); ?><?php single_term_title(); ?></h1></div>
in reply to: Clickable hotspots rather than rollover in 2023 #1418874

Lovely work, Mike – really happy with that.

Thanks again for your hard work.

Dominic

in reply to: Clickable hotspots rather than rollover in 2023 #1418799

Actually on the z-index I may need some help in inserting it into our existing code. Thanks

Dominic

in reply to: Clickable hotspots rather than rollover in 2023 #1418798

Hi Mike

When I say wrapping I mean the text auto-wraps as the tooltip ‘grows’ – I’ve got quite a bit of content in my tooltips and I think this looks a bit hokey. Check out https://oxwedev.wpengine.com/this-is-a-map-test/ to see this happening. If we could fix that then the drawer effect would bother me less. Otherwise, maybe a simple fade would suffice.

I’ll try the z-index now.

Dominic

in reply to: Clickable hotspots rather than rollover in 2023 #1418787

Plus, is there a way to get the tooltip to sit above the hotspots? At the moment, a higher numbers hotspot appears on top of the activated tooltip.

in reply to: Clickable hotspots rather than rollover in 2023 #1418785

Yeah, it’s pretty good. I’m not sure I like the way the tooltip draws from top left to bottom right on activation – I don’t like the way the text wraps. Is there a way to tweak that?

Thanks again, Mike

Dominic

in reply to: Clickable hotspots rather than rollover in 2023 #1418761

Hi Mike – fixed it. I had an old bit of Javascript hiding in an enqueued file that was trying to do the same thing and broke it!

  • This reply was modified 1 year, 2 months ago by domchocolate.
in reply to: Clickable hotspots rather than rollover in 2023 #1418748

Hi Mike thought I’d fixed it but I haven’t… ignore this message/edit

  • This reply was modified 1 year, 2 months ago by domchocolate.
in reply to: Clickable hotspots rather than rollover in 2023 #1418747

Hi Mike thought I’d fixed it but I haven’t… ignore this message/edit

  • This reply was modified 1 year, 2 months ago by domchocolate.
in reply to: Clickable hotspots rather than rollover in 2023 #1418745

Hi Mike
I have removed the code that was needed for the section tabs, and I am just running your code (I tried it as a JS snippet, as a PHP snippet and PHP in functions.php). The code is doing something because the tooltips are appearing and not showing them all at once. But they are disappearing as quickly as they appear.

I have set up an instance on a dev server here.

https://oxwedev.wpengine.com/this-is-a-map-test/

Any ideas? Thanks again for your hard work on this.

Dominic

  • This reply was modified 1 year, 2 months ago by domchocolate.
in reply to: Clickable hotspots rather than rollover in 2023 #1418733

Thanks, Mike

Close, but no cigar for me yet. If you check this page: https://oxwedev.wpengine.com/this-is-a-map-test/ – password below – you’ll see the hotspots appear and disappear quickly. I think this is because the code is clashing with:

// custom script: hide the tooltip on the tab click
function ava_custom_script_hide_tooltip()
{
    ?>
    <script type="text/javascript">
        (function($) {
            $(document).ready(function() {
                $('.av-tab-section-tab-title-container').on('click', function(event) {
                    $('.avia-tooltip').css({
                        opacity: 0,
                        display: 'none'
                    });
                });
            });
        })(jQuery);
    </script>
    <?php
}
add_action( 'wp_footer', 'ava_custom_script_hide_tooltip', 9999 );

This code hides any visible tooltips when we click on a section tab – very important.

The clash is causing:
1. The clickable hotspots to open and close really quickly, and;
2. The clickable hotspots to stop working at all if you navigate away from the tab and back again.

Is there a way to tweak this/these code/s so that they don’t clash?

I really appreciate any help you can provide.

Dominic

in reply to: Clickable hotspots rather than rollover in 2023 #1418686

Anyone? Any thoughts?

in reply to: Clickable hotspots rather than rollover in 2023 #1418428

Hi, further to above – I got it HALF working with the following code and setting the tooltip as – always

//Clickable hotspots on ALWAYS
(function( $ ) {
	 $(window).ready(function() {
               jQuery('.avia-tooltip').hide();	
	       $('.av-image-hotspot_inner').on( "click", function(e) {
		      jQuery(this).siblings('.avia-tooltip').toggle('slow');
	        });
         });
})(jQuery);

However, the tooltip doesn’t close/hide when I click on another hotspot.

See example: https://oxwedev.wpengine.com/this-is-a-map-test/
Username and password below.

Thanks in advance

Dominic

in reply to: Image hotspot Tooltips with click – again – again 2018 #1418373

Hi

I see there are a lot of threads kike this one around creating clickable hotspots rather than rollover ones. However, none do exactly what I need them to do or work in more recent versions of Enfold. So I wonder if anyone can help.

This is how I’d like it to work:
1 A Hotspot activates a tooltip onclick (rather than rollover) and stays activated (to enable users to click for more information on that tooltip)
2 The tooltip closes when the user clicks on the corresponding hotspot OR selects a new hotspot by clicking on it.

I appreciate that Show on mouse hover – hide on click does something similar but it is confusing users in testing.

Can anyone help?

  • This reply was modified 1 year, 2 months ago by domchocolate.
in reply to: Post Slider and Accessibility #1415999

Hi, thinking about this further – would it fix it if, for example:

<a href="#5" class="goto-slide" role="link" style="transition: none 0s ease 0s;">5</a>

was changed to

<a href="#5" class="goto-slide" role="button" style="transition: none 0s ease 0s;">5</a>

and/or adding

<a href="#5" class="goto-slide" role="button" aria-hidden="true" style="transition: none 0s ease 0s;">5</a>

I also found this:

Accessibility of non-semantic controls: When a series of nested <div>s along with CSS/JavaScript is used to create a complex UI-feature, or a native control is greatly enhanced/changed via JavaScript, accessibility can suffer — screen reader users will find it difficult to work out what the feature does if there are no semantics or other clues. In these situations, ARIA can help to provide what’s missing with a combination of roles like button, listbox, or tablist, and properties like aria-required or aria-posinset to provide further clues as to functionality.

  • This reply was modified 1 year, 3 months ago by domchocolate.
in reply to: Cookie settings privacy policy accessibility issue. #1415950

Thanks Yigit

That worked.

Dominic

in reply to: Pause slider button for Accessibility #1415917

Thanks, Yigit. I thought it might be.

Viewing 30 posts - 1 through 30 (of 158 total)