Skip to main content

Improvements on DOM for accessibility and SEO

I have gone through the DOM of FluentCommunity and noticed that there is room to make some improvements to the DOM structure for better accessibility and SEO practices.

I'll sum them up here:

  • Title of topics should have a H-tag (specifically on list view)

  • The title should be higher up in the DOM before all the other stuff (above feed user)

  • Currently each topic has two URLS one on the feed user and one one the "title", there should only be one url for the whole "card" but semantically attached to the title.

  • Either add a aria label to the title or move the meta info into it's own div. Or do both. Currently when using a voice reader the user data get's told within the same action, this should not be happening it's not correct conforming accessibility rules.

  • The dark/light switcher is not accessible through keyboard navigation

  • The search is not accessible through keyboard navigation

  • The notification tab is not accessible through keyboard navigation
    All of these are also missing aria labels and button attribute

  • The heart symbol and discussions symbol should have aria label. Currently you don't know when using voice-over what this is about.

  • The overall amount of divs could be less

  • There are some links that open a new page, but don't tell this to the voice reader.

  • There is no skip link for screen readers / voice over

    • Navigation tags are missing in left menu for screen reader, telling user it's on a navigational element
  • The (sub)menu is missing statements for being A: being a submenu, B: missing a statement for being collapsed or not and aswell is missing a way to open close.

  • A lot of alt tags on images are missing, failing the requirements for accessibility

  • The topic label when on a topic should have a describing aria label

  • The 'comment' text editor doesn't tell you it's to comment on the existing topic.

  • It's nearly impossible, cumbersom to let the screen reader read the body text of a topic

    Beside it is just good practice. It's also a necessity for European Users by upcoming law. A lot of useful information can also be found on the A11Y website.

I really hope this can get priority. It's a very important for disabled people as well for seo practices to have this fixed.

Karl Emil Nikka

It’s honestly surprising that a new product with the frontend written from scratch isn’t accessible. Since we saw the same thing with the two previous products (FluentCRM and FluentSupport), I hope WPManageNinja starts taking accessibility more seriously, just like they must to with GDPR compliance (calling something 100Β % GDPR compliant doesn’t make it GDPR compliant.)

Wilco

Karl Emil NikkaΒ agree! I hope this gets priority above the other features. First get your basics right, then built upon that.

Admin j

Title of topics are H2, or am I wrong?

Wilco

Olmo jΒ Your example is either in topic view or the "card" view. There is no semantic title tag on the list-view (see example below).

Erkan Kilic

Great recommendations

Sam Jansen

If the community is private, we don't need this for SEO?

Wilco

Sam JansenΒ if it's private no, but then still accessibility is an issue! Also there a many people that don't use this for private communities.

Vibe Code

well done... but also sad that wpmanageninja doesn't care

Wilco

Tom RobakΒ Jup, it's the reason I still haven't switch although I have a license. Also no response from Shahjahan JewelΒ it's a shame they don't care.

Wilco

It feels so wrong nobody of FluentCommunity is even responding.

Wilco

Still nothing from anyone of FluentCommunity.