Rian Rietveld

Hi michaelaterndrup,

You can calculate the color contrast of a text and it’s background using a tools like:
the WebAIM Color Contrast Checker https://webaim.org/resources/contrastchecker/
The best is if the contrast ratio is 4.5 or higher.

See also the Accessibility handbook: https://make.www.ads-software.com/accessibility/handbook/quick-start-guide/use-of-color/

Remkus, the skip links and headings, added in G2.2 for a11y are still untranslated and not added to the pot file.
How can I help?

Thanks Alain!

Hi jebswebs,
On my Mac I see the logo, in different browsers.
Did you try to empty the browser cache or just reload?

Hi jebswebs,
I am sorry you had to wait for your reply.
Maintaining this plugin is done in my free time, and sometimes I have too few of that.

What is the apparent bug since Genesis and WP have updated?

Hi jebswebs,
I am sorry you had to wait for your reply.
Maintaining this plugin is done in my free time, and sometimes I have too few of that.
I can’t see what is wrong with your theme, and i’m sorry I can’t give custom theme support here.
What you can try is install the latest version of Genesis and the sample theme.
In fact the most recent version of Sample Theme is the same as Leiden.

About the rest: Leiden is not in the WP Theme repository because of the following:
You have to add the parent theme too, if you post a child theme to the repository.
And for Genesis that is not possible.
That is why Leiden can’t be in the WP Theme repository.
Kind regards,
Rian Rietveld

The screen-reader-shortcut and screen-reader-text.
I’m sorry if I can’t give support for theme development

I’m closing the issue

If you use Genesis 2.2 or higher, the Genesis Widgets are accessible. For lower versionsof Genesis I don’t know an alternative for the Featured Post/Page.

Hi Gerxke, for Genesis the translations are done via the plugin Genesis Translations. The new strings in Genesis 2.2 are not included yet into this plugin.
The plugin autor promised me this will be done soon.

new_B:
What you have to take into consideration is: against what guidelines am I testing.
If you use WAVE you can choose if you validate agains what level of accessibility you want to check. see: https://wave.webaim.org/toolbar/
WCAG 2 AA is worldwide regarded as the standard for web accessibility.

For Genesis the WCAG 2.0 AA guidelines where followed.
With in those guidelines it is ok to use an H2 before an H1.
What validator did you use?

You can also ask these questions the Genesis Slack #accessibility channel.
You can apply here: https://genesis.community/slack

yes ??

new_B, I can’t access the site with the name/password you provided.
For security reasons I delete that data with your reply.
Can you send me a DM in Slack?
you can get a Slack account over here:
https://make.www.ads-software.com/chat/
My slack name is rianrietveld

On the Genesis Slack Channel @robincornett came with the following solution:

.genesis-nav-menu .menu-item:hover,
.genesis-nav-menu .menu-item:focus,
.genesis-nav-menu .menu-item.sfHover {
    position: relative;
}

.genesis-nav-menu .menu-item:hover > .sub-menu,
.genesis-nav-menu .menu-item:focus > .sub-menu,
.genesis-nav-menu .menu-item.sfHover > .sub-menu {
    left: 50%;
    margin-left: -100px;
    opacity: 1;
}

.genesis-nav-menu .menu-item:hover > .sub-menu > .menu-item:hover > .sub-menu,
.genesis-nav-menu .menu-item:focus > .sub-menu > .menu-item:hover > .sub-menu,
.genesis-nav-menu .menu-item.sfHover > .sub-menu > .menu-item:hover > .sub-menu {
    left: 199px;
    margin-left: 0px;
    opacity: 1;
}

I hope this is helpful.
If you need more help, you can join the Genesis Slack channel:
https://genesis.community/slack