Just a note that the current UI configuration you have setup here has some accessibility issues for users of assistive technology (screen reader programs such as JAWS). I am not sure how easy it would be to make changes to out-of-the-box layouts like this, though. I work in web development for accessibility, however, and I'm blind myself.
A brief list of the issues: - No text label on the Search button. This can be fixed with an aria-label attribute. - Many other links with no accurate text label that I am assuming are images/icons of some sort. Rule of thumb: if there is an image, provide an alternative text label using aria-label or visually hidden text in a span. Mouseover/mousehover text is not read by a screen reader and does not count. - No headers/regions/landmarks at the beginning of each reply in a post. This makes it difficult to jump from reply to reply. If you don't want to use an actual h2/h3 for visual reasons, you can use role="heading" on any span or div and that will be noted as a heading for a screen reader. - Some items are not properly setup with keyboard access. The "compose..." interactable above the text box in this post box is not set up properly. It must be a clickable span or div or something - it needs to be ensured to be keyboard accessible with a tabindex and also with role="button" or role="link"
There are probably more things that I haven't noticed yet as I haven't tried all the features, though one of the usual culprits is also not properly indicating to a screen reader when something is selected or expandable, which is also an easy fix if you can actually make changes to the layout code.
As an example, this is what I see in that ul (unordered list) of unlabelled links/images at the top of this page: List of 8 items Link Link 42 ? 42 Link Link Link Link Link Link
(The above is all in a navigation region, but none of the links have text labels so it is impossible to tell what these links do. There are unlabelled links like these scattered all over the layout.)