microsoft webmatrix says main cannot be descendant of body

False negatives are obviously to be preferred over false positives here. We’ve identified a few cases where we feel the browser can detect this with low or no false positives. The problem is that authors and frameworks are using aria-hidden incorrectly in the wild.

Not included, but some browsers make descendant content with aria-hidden='false' avialable in the accessibility treeįolks, I think we’re getting seriously derailed on this conversation, IMHO. Position: absolute top: -300px left: -3000px Only content made visible by descendant elements with visibility: visible is available in the accessibility tree Hiding/Showing Options for the web TechnologyĬontent not rendered, but box dimensions are maintained, descendant content can be rendered by applying visibility: visible A feature that requires more testing is something we should be trying to limit, rather than expand the scope.įrom the authoring practices perspective we should be emphasizing that content should be visible or not visible in both the DOM and accessibility tree, and the use of existing HTML and CSS standards to do this. Maybe modern web development left this principle behind many years ago, but I have mostly heard in this discussion developers using aria-hidden have to do a lot of testing to see if it will have the effect they want, assuming they even understand the effect they are looking for is supporting accessibility. The original goal Tim Burners-Lee had for the web was for people to write something once and have it viewable everywhere.

Do we need an ARIA property or technique that is clearer that content is 'decorative', like role='img' aria-label='' to build off current HTML technique of img alt='' element or an aria-decorative property?.

Do we need a ARIA property that shows content in the accessibility tree, but is not in the DOM rendering tree?.

Can aria-hidden be more like the hidden attribute and have no values, if present it just removes content from the accessibility tree?.

Is there a place for this property in a website that is engineered for accessibility, or is it primary purpose to support some type of repair of an inaccessible website?.

I think we should be limiting rather than expanding the scope of aria-hidden, we should look at limited the creativity of this problematic property.

Microsoft webmatrix says main cannot be descendant of body