If you can share a URL with the affected CSS, I can look it over for you and see what might be going on. But just moving the bottom share buttons visually would probably result in the behavior you are experiencing, because the buttons still technically come after the content. One way to change that would be to use a different hook to place the vertical buttons, so they don’t come immediately after the content.
You are correct that a style should be added for :focus … thanks for bringing it to my attention! I’ll see what I can do to remedy that.
Thread Starter
Karis
(@askel45)
Here is the CSS I am referring to. Just try to put the top and bottom icons then add the CSS and then try to tab through the content. You will see what I mean. Regarding the hook, I tried to hook the shortcode three times (I use a starter theme which I created do_action hooks for my custom plugin. Mind you, I am not a developer, I just learnt some code to help me manage my site). Then I assigned one parent class to the top and bottom icons and a different one to the vertical ones. I set each version not to display at a certain width with media query (max-width 1200 for top and bottom and min-width 1201 for the vertical). The problem arises that when I hide the top and bottom icons, they also disappear for the vertical ones. I am assuming this is due to the icons sharing the same CSS in both instances. If you have a workaround, let me know. (For focus styling, I just adapted the buttons to use my CSS for buttons sitewide (I prefer colour #666)).
If you are creating a custom parent class for each set of buttons, that’s a solid idea and should help accomplish what you want. As long as the classes are unique, you should be able to use them to style each set of buttons differently. If you can share a link, I can offer more specific help based on what is on your site.
Yes, the buttons will be part of the flow of tabbing through the site, wherever they are in the source code. If you do not want them immediately after the content, then you will need to use a filter or action hook to move it “physically” in the page output, as the CSS will only move it visually.
Thread Starter
Karis
(@askel45)
I finally figured it out with some CSS. And it even fixes properly inside the post-content container.