I think this plugin is creating ADA issues with the social media links module

[mrbm]

I started reviewing the social media module and why it keeps getting contrast errors vs the demo sites on divi not having. contrast errors.

Upon reviewing the rendered code...on this area of code: <span class="et_pb_social_media_follow_network_name" aria-hidden="true">Facebook</span>

.da11y-screen-reader-text, .et_pb_contact_form_label, .et_pb_search .screen-reader-text, .et_pb_social_media_follow_network_name, .widget_search .screen-reader-text {
    clip: rect(1px,1px,1px,1px);
    -webkit-font-smoothing: subpixel-antialiased;
    font-family: -apple-system,BlinkMacSystemFont,Segoe UI,Roboto,Oxygen-Sans,Ubuntu,Cantarell,Helvetica Neue,sans-serif;
    font-size: 1em;
    font-weight: 600;
    height: 1px;
    letter-spacing: normal;
    line-height: normal;
    overflow: hidden;
    position: absolute!important;
    text-shadow: none;
    text-transform: none;
    width: 1px;
}

.et_pb_contact_form_label, .et_pb_search .screen-reader-text, .et_pb_social_media_follow_network_name, .widget_search .screen-reader-text {
    display: block!important;
}

Any ideas?

[gjeflec]

I have been adding the following CSS to divi and it has eliminated errors when I check using WAVE -

.da11y-screen-reader-text, .widget_search .screen-reader-text, .et_pb_search .screen-reader-text, .et_pb_social_media_follow_network_name  {color: #000 !important; background-color: #fff !important;}

.et_pb_social_media_follow_network_name {display:none !important;}

/Colleen D. Gjefle/ /Visit my Fine Art Website: gjefle-art.com https://gjefle-art.com/ /Get a FREE art download! https://gjefle-art.com/free-art-download//

Turn on image viewing to see artwork pictures

---

On 3/23/2023 10:11 PM, mrbm wrote:

I started reviewing the social media module and why it keeps getting contrast errors vs the demo sites on divi not having. contrast errors.

Upon reviewing the rendered code...on this area of code: |<span class="et_pb_social_media_follow_network_name" aria-hidden="true">Facebook|

|.da11y-screen-reader-text, .et_pb_contact_form_label, .et_pb_search .screen-reader-text, .et_pb_social_media_follow_network_name, .widget_search .screen-reader-text { clip: rect(1px,1px,1px,1px); -webkit-font-smoothing: subpixel-antialiased; font-family: -apple-system,BlinkMacSystemFont,Segoe UI,Roboto,Oxygen-Sans,Ubuntu,Cantarell,Helvetica Neue,sans-serif; font-size: 1em; font-weight: 600; height: 1px; letter-spacing: normal; line-height: normal; overflow: hidden; position: absolute!important; text-shadow: none; text-transform: none; width: 1px; } | |.et_pb_contact_form_label, .et_pb_search .screen-reader-text, .et_pb_social_media_follow_network_name, .widget_search .screen-reader-text { display: block!important; } |

Any ideas?

— Reply to this email directly, view it on GitHub https://github.com/campuspress/divi-accessibility/issues/81, or unsubscribe https://github.com/notifications/unsubscribe-auth/APSJRTPZLTA2ZY4JF6K7VXDW5T7FLANCNFSM6AAAAAAWF7IGF4. You are receiving this because you are subscribed to this thread.Message ID: @.***>