“ARIA role must be appropriate for the element” on html/head/body
Whilst running the aXe accessibility tool in Chrome Developer, I am getting the following error on my head and body elements
ARIA role must be appropriate for the element
My HTML is as follows..
<html>
<head role="banner">
...
</head
<body role="main">
...
</body>
If I remove the roles, I get an error saying a page must have a landmark role but if I add main back to either html, head or body, I still get the error
What are the acceptable ARIA roles for head and body that also relate to a landmark?
html accessibility wai-aria
add a comment |
Whilst running the aXe accessibility tool in Chrome Developer, I am getting the following error on my head and body elements
ARIA role must be appropriate for the element
My HTML is as follows..
<html>
<head role="banner">
...
</head
<body role="main">
...
</body>
If I remove the roles, I get an error saying a page must have a landmark role but if I add main back to either html, head or body, I still get the error
What are the acceptable ARIA roles for head and body that also relate to a landmark?
html accessibility wai-aria
add a comment |
Whilst running the aXe accessibility tool in Chrome Developer, I am getting the following error on my head and body elements
ARIA role must be appropriate for the element
My HTML is as follows..
<html>
<head role="banner">
...
</head
<body role="main">
...
</body>
If I remove the roles, I get an error saying a page must have a landmark role but if I add main back to either html, head or body, I still get the error
What are the acceptable ARIA roles for head and body that also relate to a landmark?
html accessibility wai-aria
Whilst running the aXe accessibility tool in Chrome Developer, I am getting the following error on my head and body elements
ARIA role must be appropriate for the element
My HTML is as follows..
<html>
<head role="banner">
...
</head
<body role="main">
...
</body>
If I remove the roles, I get an error saying a page must have a landmark role but if I add main back to either html, head or body, I still get the error
What are the acceptable ARIA roles for head and body that also relate to a landmark?
html accessibility wai-aria
html accessibility wai-aria
asked Nov 9 at 15:13
Mike
1,05641639
1,05641639
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
What are the acceptable ARIA roles for head and body that also relate to a landmark?
There aren't any.
Your landmarks should be inside the body element.
The W3C provide some examples.
add a comment |
I would like to add to the previous answer that you have probably made a confusion between head and header.
Banner is a possible appropriate role for an header element.
The header should itself be present inside the body.
In the opposite, informations in the head element (except title) aren't supposed to be shown on screen and be present in the accessibility tree.
Thus they musn't have a role; that wouldn't make sense.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228387%2faria-role-must-be-appropriate-for-the-element-on-html-head-body%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
What are the acceptable ARIA roles for head and body that also relate to a landmark?
There aren't any.
Your landmarks should be inside the body element.
The W3C provide some examples.
add a comment |
What are the acceptable ARIA roles for head and body that also relate to a landmark?
There aren't any.
Your landmarks should be inside the body element.
The W3C provide some examples.
add a comment |
What are the acceptable ARIA roles for head and body that also relate to a landmark?
There aren't any.
Your landmarks should be inside the body element.
The W3C provide some examples.
What are the acceptable ARIA roles for head and body that also relate to a landmark?
There aren't any.
Your landmarks should be inside the body element.
The W3C provide some examples.
answered Nov 9 at 15:15
Quentin
638k718611031
638k718611031
add a comment |
add a comment |
I would like to add to the previous answer that you have probably made a confusion between head and header.
Banner is a possible appropriate role for an header element.
The header should itself be present inside the body.
In the opposite, informations in the head element (except title) aren't supposed to be shown on screen and be present in the accessibility tree.
Thus they musn't have a role; that wouldn't make sense.
add a comment |
I would like to add to the previous answer that you have probably made a confusion between head and header.
Banner is a possible appropriate role for an header element.
The header should itself be present inside the body.
In the opposite, informations in the head element (except title) aren't supposed to be shown on screen and be present in the accessibility tree.
Thus they musn't have a role; that wouldn't make sense.
add a comment |
I would like to add to the previous answer that you have probably made a confusion between head and header.
Banner is a possible appropriate role for an header element.
The header should itself be present inside the body.
In the opposite, informations in the head element (except title) aren't supposed to be shown on screen and be present in the accessibility tree.
Thus they musn't have a role; that wouldn't make sense.
I would like to add to the previous answer that you have probably made a confusion between head and header.
Banner is a possible appropriate role for an header element.
The header should itself be present inside the body.
In the opposite, informations in the head element (except title) aren't supposed to be shown on screen and be present in the accessibility tree.
Thus they musn't have a role; that wouldn't make sense.
answered Nov 12 at 12:20
QuentinC
2,26531018
2,26531018
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228387%2faria-role-must-be-appropriate-for-the-element-on-html-head-body%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown