Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

header and footer are not output correctly #216

Closed
JAWS-test opened this issue Jul 12, 2019 · 6 comments
Closed

header and footer are not output correctly #216

JAWS-test opened this issue Jul 12, 2019 · 6 comments
Labels
Fixed in JAWS 2024 triaged

Comments

@JAWS-test
Copy link

JAWS-test commented Jul 12, 2019 •
edited

Summary

The html elements header and footer are not output according to the specification.

http://www.w3.org/TR/wai-aria-practices-1.1/#aria_lh_banner
http://www.w3.org/TR/wai-aria-practices-1.1/#aria_lh_contentinfo
http://www.w3.org/TR/html-aam-1.0/

Unfortunately, the specification of when to output header and footer contradicts each other, but this has no effect on the present case.

Example:

  1. Save the source code as html file:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>header/footer</title>
</head>
<body>
<div id=1>
<header>The header element </header>
<main>The main element </main>
<footer>The footer element </footer>
</div>
</body>
</html>
  1. Press Ctrl+INS+R or press R or navigate with arrow keys (reading mode)

Expected result

The html elements header and footer are either always output or at least outside article, aside, main, nav and section.

It would also be useful if the output of html element and corresponding ARIA role were equivalent. However, this is a problem of specification and not of JAWS.

Actual result

IE 11: No output as soon as, for example, a child element of <div>
Chrome: Correct.
Firefox: Is always output, even if it is a child element of <main> etc.
Edge:

  • Ctrl+INS+R does not work at all
  • when reading linearly <header> and <footer> are not output
  • when using quick navigation with R <header> and <footer> are reached (as long as they are not inside elements such as <main>), but the role is not output.

Additional Information

JAWS version and build number

JAWS 2019.1904.60
To perform the test correctly, the output of landmark regions must be activated (INS+6 > Web/HTML/PDF > Reading > High).

Operating System and version

Windows 10

Browser and version:

IE 11, Firefox, Chrome, Edge (always current version)
@scottaohara
Copy link
Contributor

FYI @JAWS-test, if posting HTML tags inline you'll need to wrap them in ` marks, otherwise when your comment is published, GitHub will try to render those tags.

I've edited your comment to fix GitHub trying to render the markup you posted, so you can check out what i did there :)

@JAWS-test
Copy link
Author

@scottaohara Sorry for my mistake and many thanks for the correction.

@scottaohara
Copy link
Contributor

no worries at all :)

@scottaohara
Copy link
Contributor

Back to the issue at hand...

can confirm that markup structure has an impact on how landmarks are exposed / discoverable by JAWS, with the greatest variability being with IE11 (which makes sense due to it's lack of native support for the landmark roles).

Test cases:

@JAWS-test JAWS-test mentioned this issue Jul 14, 2019
Closed
@scottaohara
Copy link
Contributor

Additional tests for header and footer:

@JAWS-test JAWS-test mentioned this issue Aug 22, 2019
Closed
@stevefaulkner
Copy link
Contributor

The html elements header and footer are either always output or at least outside article, aside, main, nav and section.

Works for me in JAWS 2024.2310.70, Chrome and Firefox, so closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Fixed in JAWS 2024 triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stevefaulkner @scottaohara @JAWS-test