Document has no main content area

[LukasHirt]

No description provided.

[pascalwengerter]

Closing this since we now have the Vue.js app wrapped in a <main> tag.

[marcus-herrmann]

But is it wrapping the main content of the page or everything?

[marcus-herrmann]

@pascalwengerter It looks like it is wrapping everything, and this is not how the main element is intended/could be a WCAG violation:

web/packages/web-container/index.html.ejs

Line 28 in 695d3df

<main id="owncloud"></main>

[pascalwengerter]

@marcus-herrmann sorry, was under the wrong impression that your commit had fixed it. How critical is fixing this for the accessibility certification?

@kulmann maybe we need to be solving this on the extension level, currently we're using <main> in web-container/index.html.ejs and web-runtime/src/App.vue (and from the definition below I'm not sure at which level we should be applying it, so are we wrapping extentions (e.g. draw-io) inside a <main> tag already or are they "bringing their own"?

The content inside the

element should be unique to the document. It should not contain any content that is repeated across documents such as sidebars, navigation links, copyright information, site logos, and search forms.

Note: There must not be more than one

element in a document.

[marcus-herrmann]

How critical is fixing this for the accessibility certification?

@pascalwengerter Rather critical. Wrongly applied landmarks are worse than no landmarks at all. I'm quite certain this can be seen as a violation of WCAG SC 2.4.1, Bypass blocks.

My fix back in the day fixed this, but another <main> element wrapping it all, and one inside an app, wrapping the router is certainly difficult in an audit.