Re: In-page links: Href with no corresponding ID

Thank you Patrick. Typically we have always gone down the 2.4.1 route for the in-page error link, but this was recently up for debate. So if  a regular in-page link uses the ‘href’ with no corresponding ID (therefore having no functionality) this doesn’t fail? Thanks for your help.


Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: Patrick H. Lauke <redux@splintered.co.uk>
Sent: 01 April 2022 11:54
To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org>
Subject: Re: In-page links: Href with no corresponding ID

On 31/03/2022 10:12, Tom Shaw wrote:
> Hi.
>
> I'm looking for some advice. I've been trying to understand whether or
> not an in-page skip link (for example...an error link which takes user
> focus to the problematic input) is a failure under wcag2.1 or not if it
> does not work. Example: The link uses a the href attribute #case-log for
> example but does not match an ID or the page so has no functionality.
> I'm under the impression this affects everyone and is may not be
> specifically an accessibility issue.

If it's specifically a skip link implemented to jump over repeating
blocks of content, then it fails 2.4.1. If it's a "regular" in-page link
that's broken, then no it doesn't fail 2.4.1, but is just a general
bug/error of the page.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke