We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some accessibility fixes I'm planning on patching when I've got some time, jotting it down as a start...
div
nav
role="presentation"
The text was updated successfully, but these errors were encountered:
Happy to accept PR! Loved your previous contribution 😄
Sorry, something went wrong.
Skip to content
skip to content was moved to nextra/components in v4 and is built in with nextra-theme-docs v4
nextra/components
nextra-theme-docs
nextra/packages/nextra-theme-docs/src/layout.tsx
Line 102 in c9db20f
Skip to content skip to content was moved to nextra/components in v4 and is built in with nextra-theme-docs v4 nextra/packages/nextra-theme-docs/src/layout.tsx Line 102 in c9db20f <SkipNavLink />
Ah nice! good to know, I'll cross that off my list for v3 fixes then.
I haven't tried v4 yet -- will have a look at that too. Are you guys aiming towards a stable release data for v4?
yes, first blog post with migration guide and v4.rc.0, and after couple of weeks stable release
v4.rc.0
No branches or pull requests
Some accessibility fixes I'm planning on patching when I've got some time, jotting it down as a start...
Skip to content for keyboard navigation (something like GDS)WONT FIX : this is avaliable in v4div
tonav
role="presentation"
when pre-described by other contentThe text was updated successfully, but these errors were encountered: