Issue Summary

The footer landmark is not programmatically defined and is incorrectly placed inside the main content area.

Steps to Reproduce

1. Open the Confluence Cloud Homepage.
2. From the Sidebar navigation, expand Spaces and open any space.
3. Inspect the code and observe that the footer section is nested within the main content container.

Screenshot

Screen Recording

Footer Landmark Issue

Actual Results

The footer section is not programmatically defined as a landmark. Additionally, it is incorrectly nested inside the <div role="main"> element. As a result, it is not exposed as a proper contentinfo landmark, making it difficult for screen reader users to identify and navigate to the footer region.

Expected Results

Screen reader users should be able to identify and navigate between landmark regions easily. The footer should be programmatically defined as a landmark and exposed as a proper contentinfo region, placed outside the <div role="main"> element.

Apply the following changes:

• Remove the <div> containing the footer from inside <div role="main">.
• Implement the footer using the semantic <footer> element.

Alternatively, if using the <footer> element is not feasible, implement the footer as a <div> element with role="contentinfo".

Code Snippet 1:

This code example is intended only as a general illustration of how to address the violation and should not be considered a complete or production-ready solution. If you have any questions, please attach this ticket to a #help-accessibility request.

<div role="main">
.....Main content area.....
</div>
<footer>
.....Footer section.....
</footer>

Code Snippet 2:

This code example is intended only as a general illustration of how to address the violation and should not be considered a complete or production-ready solution. If you have any questions, please attach this ticket to a #help-accessibility request.

<div role="main">
.....Main content area.....
</div>
<div role="contentinfo">
.....Footer section.....
</div>

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Environment

MacBook Pro (16-inch, 2021)
macOS Tahoe 26.2
Operations - Windows11
Chrome - Version 144.0.7559.133 (Official Build) (64-bit)
Safari- Version 26.2
JAWS- Version 2023
NVDA- Version 2025.3.2
VoiceOver - Version Latest