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.

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

Place region of elements in a logical reading order #9696

Open
manfromjupyter opened this issue Jan 28, 2021 · 1 comment
Open

Place region of elements in a logical reading order #9696

manfromjupyter opened this issue Jan 28, 2021 · 1 comment

Comments

@manfromjupyter
Copy link
Contributor

manfromjupyter commented Jan 28, 2021

WCAG 1.3.2 (A), 2.4.3 (A)

Reading capability and order

Expectation: The reading order of assistive technology is complete, logical, and intuitive

  • When testing to see if the site is still usable or logical when loading without a stylesheet which is how you test this and also how a super small % of users may choose to view the site when fonts, contrast, and background images are too prolific and busy…
  • All of the dropdown’s links are showing up in the tab order and shouldn’t until you expand it.
  • Text is overlapping indicating usually hardcoded styling regarding positioning.
  • Every icon, every, is missing screenreader-only text.

To Fix

Only things that really need to be changed by the looks of it are the header. The entire header section is placed below in the DOM than all of the panels and notebook so no wonder the user can never tab to it (because they get to the endless tabbing notebook cell and don't ever go past it). In addition when dropdowns open they are at the very bottom of the page, not the very next tab or element for the user so need to change where those open. There may be other things to fix to completely satisfy this requirement but as far as I can tell these are the only changes necessary.

header move closer to the top of the DOM (above the panels)
header dropdown move under menu item

@t03857785
Copy link
Contributor

I cannot recreate this issue, it looks like it has been resolved @manfromjupyter @isabela-pf can you confirm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Accessibility
Content, Organization, and Navigation
Development

No branches or pull requests

2 participants