Which skin does this bug relate to?

If all skins what markup are you suggesting we add to the page and where?

In T301888#7939045, @Jdlrobson wrote:

Which skin does this bug relate to?

All skins.

If all skins what markup are you suggesting we add to the page and where?

Not sure I understand the question. Navigation portlet links should expose aria-current="page" when are located on the page in question, similarly to how class="selected" is done in (all?) skins on page tabs that correlate to current location.

I think my issue might be with the teminology "portlet". What is a navigation portlet link look like in the mobile skin Minerva, for example? Are we talking about any link inside a menu or just the link to the current page that's next to talk tab?

e.g. are we talking about these links?

Perhaps there is overlap with this ticket and this one: https://phabricator.wikimedia.org/T20465 if the goal is accessibility? I think the only place the link should be to the current page is the tab next to talk page?

Minerva does not have navigation portlets per se because it implements its own sidebar, though I think even its mobile menu can benefit from this change. T20465: Tabs in Monobook and Vector should indicate selected state for assistive technology is similar to this, yes, but I am not talking strictly about tabs. As for ‘the only place the link should be to the current page is the tab next to talk page’, it is not strictly true: sidebar links can lead to the same page that we are on, and this should be indicated to screen reader users.

As for ‘the only place the link should be to the current page is the tab next to talk page’, it is not strictly true: sidebar links can lead to the same page that we are on, and this should be indicated to screen reader users.

Could you give me some examples? That would be helpful in helping prioritize this work.

Well, the basic example is that the sidebar link to ‘Main Page’ leads to the same page you are on if you are located on the project’s main page.