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

Technique G1 resource outdated #3746

Closed
anevins12 opened this issue Mar 13, 2024 · 1 comment · Fixed by #3767
Closed

Technique G1 resource outdated #3746

anevins12 opened this issue Mar 13, 2024 · 1 comment · Fixed by #3767
Assignees

Comments

@anevins12
Copy link
Member

anevins12 commented Mar 13, 2024

Hello,

I've noticed that the resource in Technique G1 is outdated: Skip Navigation

The resource was fantastic at the time and described a bug with IE 5, 6, and 7 where the tabindex="-1" attribute was necessary for linked-to content.

During the last decade, I've heard reasoning from technical and accessibility folks that they no longer need to use the tabindex="-1" attribute on the destination of skip links because they don't support old IE any more. I believed them at the time, but this outdated reasoning.

The Skip Navigation resource, through no fault of its own, leads folks into thinking this.

Since 2014 and perhaps 2015 when it was adopted, the HTML standard introduced sequential focus navigation. Sequential focus navigation reinstated the need for the use of the tabindex attribute in the context of internal links that lead to non-interactive content. A relevant example of this is when a skip link leads to the main section of content. This is where the user agent determines the "focusable area".

Without meeting the criteria of a focusable area, keyboard focus is not moved to the destination. To clarify, I am not talking about what happens when you press the TAB key. This is when you activate a skip link and do nothing else.

I get that the onus is on folks to keep up to date with the HTML spec, but I also think that the resource could be updated to clarify the need of tabindex.

Do you agree and if so, do you think that we need a new resource?

@mraccess77
Copy link

I run into this issue with JAWS and Chrome - so I think it makes sense to update it to cover that possibility.

fstrr added a commit that referenced this issue Mar 28, 2024
Closes #3746

Change outdated link to HTML spec on focus.
@fstrr fstrr self-assigned this Mar 28, 2024
mbgower pushed a commit that referenced this issue Apr 30, 2024
Closes #3746

Change outdated link to HTML spec on focus.
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 a pull request may close this issue.

3 participants