“ARIA role must be appropriate for the element” on html/head/body
up vote
-1
down vote
favorite
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
asked Nov 9 at 15:13
Mike
1,05641638
add a comment |
up vote
-1
down vote
favorite
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
asked Nov 9 at 15:13
Mike
1,05641638
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
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
asked Nov 9 at 15:13
Mike
1,05641638
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,05641638
asked Nov 9 at 15:13
Mike
1,05641638
asked Nov 9 at 15:13
Mike
1,05641638
asked Nov 9 at 15:13
Mike
1,05641638
asked Nov 9 at 15:13
Mike
1,05641638
1,05641638
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
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
634k718531023
add a comment |
up vote
0
down vote
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,23031018
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
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
634k718531023
add a comment |
up vote
1
down vote
accepted
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
634k718531023
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
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
634k718531023
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
634k718531023
answered Nov 9 at 15:15
Quentin
634k718531023
answered Nov 9 at 15:15
Quentin
634k718531023
answered Nov 9 at 15:15
Quentin
634k718531023
634k718531023
add a comment |
add a comment |
up vote
0
down vote
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,23031018
add a comment |
up vote
0
down vote
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,23031018
add a comment |
up vote
0
down vote
up vote
0
down vote
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,23031018
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,23031018
answered Nov 12 at 12:20
QuentinC
2,23031018
answered Nov 12 at 12:20
QuentinC
2,23031018
answered Nov 12 at 12:20
QuentinC
2,23031018
2,23031018
add a comment |
add a comment |
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
