Title: Accessibility Issues
Last modified: October 6, 2023

---

# Accessibility Issues

 *  Resolved [Morshed Alam](https://wordpress.org/support/users/sumon1068/)
 * (@sumon1068)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/accessibility-issues-35/)
 * Right now there are two accessibility issues created by this plugin:
    1. Links do not have a discernible name
    2. Header tag in Comment area label (h3)
 * When users sign up using their Social accounts, no alternative text is added 
   to their avatars. I emailed Heteor support about it a few years ago. They said
   it will be implied in the next version. Yet, it isn’t added. Please apply users**
   display name** as alt text for their avatars.
 * Comment area label is using h3. This is irrational. Header tag is for heading
   of an article. How can ‘Leave a comment’ be a heading for an article? It should
   be p tag. As Super Socializer is using h3, we get this error in some of our page:**
   Heading elements are not in a sequentially-descending order**.
 *  Please take necessary steps to fix these two problems.
 * Thank you.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Faccessibility-issues-35%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Heateor Support](https://wordpress.org/support/users/heateor/)
 * (@heateor)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/accessibility-issues-35/#post-17105008)
 * See the screenshot.
 * > [View post on imgur.com](https://imgur.com/WVyDvLU)
 * **Links do not have a discernible name** error implies the <a> tags in the HTML
   of your web pages should have
   1. Either some text between the <a href=””> and
   </a>2. Or if you can’t have text (if you have <img> tag for example), these should
   have **aria-label** attribute with the value describing the purpose of the image
   between. In your case, the aria-label in these tags should be something like **
   aria-label=”Author”**This plugin is responsible for the <img tag that is showing
   the image of the author if they have used social login. The <a> tag having this
   image is generated by your theme. Regarding the second problem, Header tags in
   your web page should be in sequentially descending order. If the heading before
   the **Leave a comment** would be **h2** it would have been fine. But if it’s **
   h1** or **h3**, it would generate error. So, it depends on the theme being used
   at the website where social commenting is enabled. We will update it to <p> tag
   or something in the upcoming update.
 *  Plugin Author [Heateor Support](https://wordpress.org/support/users/heateor/)
 * (@heateor)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/accessibility-issues-35/#post-17192598)
 * This has been taken care of in the version 7.13.60
 *  Thread Starter [Morshed Alam](https://wordpress.org/support/users/sumon1068/)
 * (@sumon1068)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/accessibility-issues-35/#post-17192729)
 * Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Accessibility Issues’ is closed to new replies.

 * ![](https://ps.w.org/super-socializer/assets/icon-128x128.png?rev=1866723)
 * [Social Share, Social Login and Social Comments Plugin - Super Socializer](https://wordpress.org/plugins/super-socializer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/super-socializer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/super-socializer/)
 * [Active Topics](https://wordpress.org/support/plugin/super-socializer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/super-socializer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/super-socializer/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Morshed Alam](https://wordpress.org/support/users/sumon1068/)
 * Last activity: [2 years, 7 months ago](https://wordpress.org/support/topic/accessibility-issues-35/#post-17192729)
 * Status: resolved