Tagged: 

Viewing 21 posts - 1 through 21 (of 21 total)
  • Author
    Posts
  • #1086720

    Hey Kriesi,

    I have a client asking about ADA compliancy – a bit one being that there is some kind of change when you press tab on your computer. How do I make it so when I press tab an underline will appear on the button or menu link that is being highlighted?

    #1087341

    Hey Andrea,

    You could try something like this in Quick CSS to see if you have any luck with it:

    a:focus {
      text-decoration:underline !important;
    }

    Best regards,
    Rikard

    #1088450

    That worked perfectly! Thanks!

    #1089002

    Hi,

    Great, I’m glad we could help. Please let us know if you should need any further help on the topic or if we can close it.

    Best regards,
    Rikard

    #1089148

    Hey Rikard,

    I’ll post the rest of the accessibility report – I’d be curious if some of these items could be addressed in the next update for Enfold? They’re relatively “minor” but I’m having more and more people come to me quite concerned about whether or not their company will be sued.

    Developer updates

    Add :focus (tab) styling to all links (primarily an issue in the site’s footer)
    Focus styles allow users to easily navigate the site using only their keyboard, which is a must for users who have difficulty using a mouse/trackpad.

    Make sure that all“id” attributes are unique on every page
    Duplicate “id” attributes is a violation of HTML standards, and can cause issues with older screen readers.

    Add appropriate “aria-label” attributes to links that do not have discernible text (primarily for the social media links in the footer)
    Links without discernible text in them cannot be read by screen readers. The solution to this is to use appropriate “aria-labels” to tag all textless links, allowing screen readers to infer their purpose.

    Remove the “maximum-scale=1” attribute from “<meta name=”viewport”>” tag
    The “maximum-scale=1” attribute disallows mobile users from zooming in on your website. Removing this is necessary to allow visually impaired visitors to enlarge any portion of the site when browsing on their phone/tablet.

    Make sure all site content is contained within “landmark” regions (<header>, <nav>, <main>, <footer>)
    Using these landmark tags allows screen readers to clearly understand the split between the site’s high-level sections.

    Ensure that all elements have sufficient color contrast
    Users with poor vision or color blindness are unable to distinguish text against a background without sufficient contrast. Ensuring that the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds is incredibly important for accessibility.

    ARIA hidden element must not contain focusable elements
    The site has a hidden “scroll to top” button that is still focusable via the tab key. A focusable element with aria-hidden=”true” is ignored as part of the reading order, but still part of the focus order, making its state of visible or hidden unclear.
    Guidelines for the client to focus on moving forward

    Make sure that all headings (H1-H6) are contextually appropriate, and ordered correctly
    Screen readers use headings to summarize content sections, allowing non-sighted users to quickly navigate through the site. Ensuring that headings are contextually and semantically valid, as well as used to describe the structure of the page, not just highlight important text, speeds up this process.

    Make sure that heading levels only increase by one (H1 followed by H2, never H1 followed by H4)
    The underlying purpose of headers is to convey the structure of the page. While text size can be used to structure the page for sighted users, the same can not be done for non-sighted/visually impaired users. Only properly structured headings can achieve the same for screen readers, because a screen reader identifies a header only if it is properly marked-up.

    Make sure that all pages contain a top-level H1 tag
    Many of the site’s pages are missing H1 tags. Generally, it’s a best practice to ensure that the beginning of a page’s main content starts with an h1 tag, and also to ensure that the page contains only one h1 element. Screen readers have keyboard shortcuts to navigate directly to the first h1, which, in principle, should allow users to jump directly to the main content of the page. If there is no h1, or if the h1 appears somewhere other than at the start of the main content, screen reader users must listen to more of the page to understand its structure, wasting valuable time.

    Ensure that all inline images have appropriate “alt” tags
    Screen readers have no way of translating an image into words that gets read to the user (even if the image only consists of text). As a result, it’s necessary for images to have short, descriptive alt text so screen reader users clearly understand the image’s contents and purpose.

    #1089162

    Hi,

    Thanks a lot for this detailed description.

    I have opened an issue for that in our dev repo and will keep an eye on it.

    For the next update which is close I’m afraid we will not be able to adress any of the points.

    Best regards,
    Günter

    #1103808

    Hi Günter, I hope you guys will look into that topic ( ADA compliance ) as soon as possible. One of my Clients ( using enfold ) got sued :(
    For now, I will stop using the theme for US-based customers.
    I own a lot of other bestseller themes bought on theme forest and no one is 100% ADA compliance.
    So i guess it would be great to be the first one to promote an ADA compliance ready theme.

    #1105330

    Hi,

    1.) The css code above should add a focus state to every link in the page.

    Add :focus (tab) styling to all links (primarily an issue in the site’s footer)

    a:focus {
      text-decoration:underline !important;
    }

    2.) Just make sure that there are no elements with the same ID in the page.

    Make sure that all“id” attributes are unique on every page

    3.) Use the “avf_social_media_icon_aria_label_value” and “avf_social_share_links_aria_label_value” the to add an aria-label attribute to the social icons.

    Add appropriate “aria-label” attributes to links that do not have discernible text (primarily for the social media links in the footer)

    4.) This should be editable in the header.php file.

    Remove the “maximum-scale=1” attribute from “” tag

    Look for this line.

    if( strpos($responsive, 'responsive') !== false ) echo '<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">';
    

    5.) This might take a while to implement.

    Make sure all site content is contained within “landmark” regions (, , , )

    // https://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks_to_identify_regions_of_a_page

    6.) You should check your design and make sure that the color or theme has the right contrast.

    Ensure that all elements have sufficient color contrast

    This plugin might help: https://getkontrast.now.sh

    7.) Edit the footer.php file and look for this code.

    ARIA hidden element must not contain focusable elements

    <a href='#top' title='<?php _e('Scroll to top','avia_framework'); ?>' id='scroll-top-link' aria-hidden='true' <?php echo av_icon_string( 'scrolltop' ); ?>><span class="avia_hidden_link_text"><?php _e('Scroll to top','avia_framework'); ?></span></a>
    

    Add the aria-hidden=”true” attribute.

    8-9.) The heading tags (h1-h6) should be added in the page in a consecutive manner. You shouldn’t add an h4 after an h2 or h3 after an h1.

    Make sure that all headings (H1-H6) are contextually appropriate, and ordered correctly

    Make sure that heading levels only increase by one (H1 followed by H2, never H1 followed by H4)

    Try to follow this guideline:

    // https://www.w3.org/TR/WCAG20-TECHS/ARIA12.html

    If you don’t want to use the special heading element, you can add an element manually using a text or code block and then add the role=”heading” and “aria-level” attribute to it.

    // https://www.w3.org/TR/WCAG20-TECHS/ARIA12.html

    10.) Add an h1 special heading element in every page.

    Make sure that all pages contain a top-level H1 tag

    11.) Make sure that every image in the Media > Library contains a description, alt and title attribute.

    Best regards,
    Ismael

    #1170803

    re: aria landmarks

    it appears that if you add a “Colour Section” or “Grid Row” or “Tab Section” layout item in Enfold these get put outside of the <main> content and therefore breaks the correct accessibility landmark structure

    this would presumably be fixed by not breaking them out of their wrapping container.

    are we likely to see a fix to this?

    thanks

    #1170903

    Hi codemonkeynorth,

    Please open a new thread and include details to where we can see the problem you are having.

    Best regards,
    Rikard

    #1317540

    Re #7 above, one of my clients is working with an accessibility expert and they recommended removing the aria-hidden=true attribute from the scroll-top-link. They think that attribute was put there to hide that link on the phone, but that method apparently creates an accessibility concern on the desktop, where it’s visible. So they’re suggesting removing the attribute and using css to hide it in mobile. Is there a way for me to remove that aria-hidden attribute via my child theme? Thanks!

    • This reply was modified 3 years, 4 months ago by sky19er.
    #1317647

    Hi,


    @sky19er

    Via a filter in child theme – currently not.

    You can update the core file enfold\footer.php in line 295 you find:

    
    echo av_icon_string( 'scrolltop' );
    

    Replace this with:

    
    echo av_icon_string( 'scrolltop', false );
    

    You need to update this whenever you update the theme.

    If we might add a filter in future version it will be documented in place.

    Best regards,
    Günter

    #1317666

    OK, thanks, Günter,, but would yo please elaborate on “documented in place” — what do you mean by that?

    #1317719

    Hi,


    @sky19er

    documented in place

    in the file where we add the filter we add a comment with the parameters.

    Best regards,
    Günter

    #1317748

    I’m sorry, I still don’t understand — I thought the filter was something I would add to my child theme, so where would you be adding the filter, in the footer.php file? Are you saying I can just keep an eye on the footer.php file to see if you make that change in future updates? Thanks.

    #1317752

    I want to jump in on this topic — in the USA, many sites are being sued for ADA compliance now including friends who are going through this right now. This is like GDPR in the EU in terms of importance… absolutely essential that we address immediately. And on top of that… it’s the right thing to do for our differently-abled friends. I am hoping the mods / Gunter / etc can discuss this important topic, and I’m glad to see this here on the Enfold forum.

    Thanks
    Rob

    #1317759

    I just installed the plugin called “One Click Accessibility” and it’s extremely easy to use and looks great. It took me about 5 mins to install and customize it, and it works well on both mobile and desktop.

    If you want to see it in action, go to:

    http://www.thomashenthorne.com

    #1317767

    @goldengate415. FYI, my client’s accessibility specialist said those plugins are no good — maybe they’re biased, but you may want to look into that. Here’s an article, for example: https://creative-boost.com/overlays-and-plugins-arent-the-answer-to-accessibility/

    #1317771

    It’s an interesting dilemma… there are recommendations but no firm standards, and lawsuits are being file against websites for not adhering to these grey areas. Some websites are paying $50 a month for these accessibility overlays but there are guarantees even at $1000 or more a year. I do like that this plugin adds some options like larger fonts and higher contrast that should help low vision visitors to the site. I am definitely open to suggestions and hope this is now on Enfold’s radar.

    #1318678

    Hi @sky19er,

    Currently there is no filter for it. Günter meant that if we add a filter for it, we will add a comment in footer.php file and of course in change log :)


    @goldengate415
    thanks again for your suggestion! We have forwarded it to Günter :)

    Best regards,
    Yigit

    #1318708

    OK, thanks, Yigit!

Viewing 21 posts - 1 through 21 (of 21 total)
  • The topic ‘ADA compliancy’ is closed to new replies.