
GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
Accessible Navigation for Nested nav-items Β· Issue #4804 Β· squidfunk/mkdocs-material
Description:
Contribution guidelines I've read the contribution guidelines and wholeheartedly agree I want to suggest an idea and checked that ... ... to my best knowledge, my idea wouldn't break someth...
Website Age:
17 years and 8 months (reg. 2007-10-09).
Matching Content Categories {π}
- Social Networks
- Education
- Video & Online Content
Content Management System {π}
What CMS is github.com built with?
Github.com employs WORDPRESS.
Traffic Estimate {π}
What is the average monthly size of github.com audience?
ππ Tremendous Traffic: 10M - 20M visitors per month
Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.
check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush
How Does Github.com Make Money? {πΈ}
Subscription Packages {π³}
We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.How Much Does Github.com Make? {π°}
Subscription Packages {π³}
Prices on github.com are in US Dollars ($).
They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.
Wordpress Themes and Plugins {π¨}
What WordPress theme does this site use?
It is strange but we were not able to detect any theme on the page.
What WordPress plugins does this website use?
It is strange but we were not able to detect any plugins on the page.
Keywords {π}
squidfunk, issue, idea, navigation, open, sign, requests, commented, resolved, projects, nested, navitems, closed, ive, adding, ariaexpanded, labels, added, owner, mentioned, issues, pull, actions, security, accessible, description, mnazzaro, contribution, guidelines, users, tabindex, ariahidden, attributes, event, listeners, expand, make, comment, change, request, feature, improvement, accessibility, project, material, leec, javascript, collapsed, react, unreleased,
Topics {βοΈ}
nested nav-items improvement resolved issue /mnazzaro/mkdocs-material closed issues open projects nav bar easier added aria-hidden contribution guidelines completed dmundra mentioned add event listeners visually impaired users comment metadata assignees aria-expanded attribute propose adding tabindex projects milestone aria-expanded attributes idea description material version 9 open event listeners [aria-] attributes aria-expanded aria-hidden adding tabindex= mkdocs 9 wholeheartedly agree click enter screenshots / mockups suggested solution improving accessibility top priority page size accessibility tree child elements milestone relationships material inline javascript labels //github mentioned github expanded resolved users comment adding hidden idea javascript sign
Payment Methods {π}
- Braintree
Questions {β}
- Already have an account?
Schema {πΊοΈ}
DiscussionForumPosting:
context:https://schema.org
headline:Accessible Navigation for Nested nav-items
articleBody:### Contribution guidelines
- [X] I've read the [contribution guidelines](https://github.com/squidfunk/mkdocs-material/blob/master/CONTRIBUTING.md) and wholeheartedly agree
### I want to suggest an idea and checked that ...
- [X] ... to my best knowledge, my idea wouldn't break something for other users
- [X] ... the documentation does not mention anything about my idea
- [X] ... there are no open or closed issues that are related to my idea
### Description
I propose adding tabindex, aria-hidden, and aria-expanded attributes to the labels on nested nav-items. I would also like to add event listeners to those same labels such that when they are in focus the user can click enter to expand them.
### Use Cases
This would make the nav bar easier to use for visually impaired users. As it stands, they aren't tabbable, and just adding tabindex="0" doesn't make it better because they still need to be clicked on to expand. This is why the event listeners are also necessary.
### Screenshots / Mockups
Here's a link to my suggested solution: https://github.com/mnazzaro/mkdocs-material
It still has some problems, though, as described in my comment in discussion 3156: https://github.com/squidfunk/mkdocs-material/discussions/3156#discussioncomment-4501461
_No response_
author:
url:https://github.com/mnazzaro
type:Person
name:mnazzaro
datePublished:2022-12-27T14:30:40.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:4
url:https://github.com/4804/mkdocs-material/issues/4804
context:https://schema.org
headline:Accessible Navigation for Nested nav-items
articleBody:### Contribution guidelines
- [X] I've read the [contribution guidelines](https://github.com/squidfunk/mkdocs-material/blob/master/CONTRIBUTING.md) and wholeheartedly agree
### I want to suggest an idea and checked that ...
- [X] ... to my best knowledge, my idea wouldn't break something for other users
- [X] ... the documentation does not mention anything about my idea
- [X] ... there are no open or closed issues that are related to my idea
### Description
I propose adding tabindex, aria-hidden, and aria-expanded attributes to the labels on nested nav-items. I would also like to add event listeners to those same labels such that when they are in focus the user can click enter to expand them.
### Use Cases
This would make the nav bar easier to use for visually impaired users. As it stands, they aren't tabbable, and just adding tabindex="0" doesn't make it better because they still need to be clicked on to expand. This is why the event listeners are also necessary.
### Screenshots / Mockups
Here's a link to my suggested solution: https://github.com/mnazzaro/mkdocs-material
It still has some problems, though, as described in my comment in discussion 3156: https://github.com/squidfunk/mkdocs-material/discussions/3156#discussioncomment-4501461
_No response_
author:
url:https://github.com/mnazzaro
type:Person
name:mnazzaro
datePublished:2022-12-27T14:30:40.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:4
url:https://github.com/4804/mkdocs-material/issues/4804
Person:
url:https://github.com/mnazzaro
name:mnazzaro
url:https://github.com/mnazzaro
name:mnazzaro
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:4
interactionType:https://schema.org/CommentAction
userInteractionCount:4
External Links {π}(3)
Analytics and Tracking {π}
- Site Verification - Google
Libraries {π}
- Clipboard.js
- D3.js
- Lodash
Emails and Hosting {βοΈ}
Mail Servers:
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Name Servers:
- dns1.p08.nsone.net
- dns2.p08.nsone.net
- dns3.p08.nsone.net
- dns4.p08.nsone.net
- ns-1283.awsdns-32.org
- ns-1707.awsdns-21.co.uk
- ns-421.awsdns-52.com
- ns-520.awsdns-01.net