All page content should be contained by landmarks

As part of Deque Systems accessibility testing platform, their DevTools provides you with the opportunity test for accessibility issues. One such issue is landmarks.

Asked and answered by Deque’s own developers

The following question was posted in Deque System’s Office Hours with Dev A11y Experts webinar on May 21, 2024.

Why does DevTools identify the HTML element, <section>, as an issue when the best practice option is turned on, and not an issue when the best practice is turned off?

Unfortunately, the webinar was not recorded so I could not really capture the reply. My eyes were too busy going back and forth between ASL interpreter and captions.

I did not think to check for the transcript and capture the response. I am documenting the answer here to the best of my memory almost two hours after the fact.

Three of the developers deferred to the fourth developer who works on the axe-core rules. It seems like the fourth developer did not fully understand the question.

As a result, there was no answer that was memorable enough for me to recall from memory so I could document it here.

What I do remember is that the developer gave a standard answer regarding the need to examine the exact scenario in order to answer the question.

That brings me to the next point.

Document everything

DevTools’ Best Practices turned off

Firefox inspector panel with DevTool showing an issue with one landmark when Best practices is turned off.

DevTools’ Best Practices turned off

Firefox inspector panel with DevTool showing an issue with one landmark when Best practices is turned on.

Question posted in Deque System’s Office Hours with Dev A11y Experts webinar

Why does DevTools identify the HTML element, <section>, as an issue when the best practice option is turned on, and not an issue when the best practice is turned off?