Skip to content

Conversation

@phette23
Copy link
Member

@phette23 phette23 commented Jan 8, 2026

While reviewing the site, I noticed a few accessibility improvements we can make.

Document does not have a main landmark — a Lighthouse recommendation. We have <div id=main> in our templates but that's not semantic, we need either <main> or <div role=main>. After this PR, the recommendation no longer appears in Lighthouse (Chrome > Dev Tools > Lighthouse > use the Accessibility category).

Redundant link — a WAVE warning because the Code4Lib logo and "home" links both go to the site home page. Visually, they float to opposite sides of the page, but they are adjacent in the source code. I added aria-hidden and tabindex=-1 to the logo link so keyboard users skip it and interact only with the "home" link. If you run WAVE, this warning still appears because WAVE intentionally ignores aria-hidden and tabindex=-1. To verify the fix: confirm that keyboard navigation first goes to the "skip to main content" link, then the "home" link, skipping the logo.

Finally, I also removed a bunch of commented out code in our nav.html template. Please confirm the mobile site view is not broken (e.g. use dev tools to emulate a phone screen).

phette23 and others added 5 commits January 5, 2026 08:58
this changes the Sponsors main menu link to go to the list of sponsors
rather than the prospectus also
we have 2 sponsors now, both bronze, one streaming
Index Data details are here but commented out until they finalize payment
skip the logo link by adding aria-hidden and tabindex -1
the 'home' link goes to the same location so this saves keyboard
users a step
this is an accessibility best practice, we had <div id=main> but
needed to use either <main> or role=main, using the element works
I don't think we'll need to return to this commented out structure
and if we do, we have previous versions of the site on github
@phette23
Copy link
Member Author

phette23 commented Jan 8, 2026

The sponsors commit is here because I based this off the wrong branch then messed up a force push (good lesson to be more careful). It shouldn't be a problem when merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants