WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Clarification on 2.4.5

for

Number of posts in this thread: 3 (In chronological order)

From: Sumit Patel
Date: Thu, Dec 19 2024 4:06AM
Subject: Clarification on 2.4.5
No previous message | Next message →

Dear all,

I hope this email finds you well.

I am currently testing the application and have come across a potential
issue concerning WCAG 2.4.5 ("Multiple Ways"). According to this guideline,
there should be **multiple ways** for users to navigate to different
webpages within a website, such as a **sitemap**, **search functionality**,
or **navigation links**.

However, in the application I am testing, I noticed that there is only the
**navigational links** mechanism in place, with no alternative methods like
a **sitemap** or **search function** available for users to locate content.

Given that the application lacks these additional navigational mechanisms,
I believe this might be a **violation** of the WCAG 2.4.5 criteria. Could
you please confirm if this would be considered a failure in compliance?

Your feedback will be greatly appreciated in guiding the next steps.

Thank you for your time and assistance.

Regards,
Sumit.

From: Sumit Patel
Date: Thu, Dec 19 2024 8:50AM
Subject: Re: Fwd: Clarification on 2.4.5
← Previous message | Next message →

---------- Forwarded message ---------
From: Sumit Patel < = EMAIL ADDRESS REMOVED = >
Date: Thu, 19 Dec 2024 at 16:36
Subject: Clarification on 2.4.5
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >


Dear all,

I hope this email finds you well.

I am currently testing the application and have come across a potential
issue concerning WCAG 2.4.5 ("Multiple Ways"). According to this guideline,
there should be **multiple ways** for users to navigate to different
webpages within a website, such as a **sitemap**, **search functionality**,
or **navigation links**.

However, in the application I am testing, I noticed that there is only the
**navigational links** mechanism in place, with no alternative methods like
a **sitemap** or **search function** available for users to locate content.

Given that the application lacks these additional navigational mechanisms,
I believe this might be a **violation** of the WCAG 2.4.5 criteria. Could
you please confirm if this would be considered a failure in compliance?

Your feedback will be greatly appreciated in guiding the next steps.

Thank you for your time and assistance.

Regards,
Sumit.

From: Steve Green
Date: Thu, Dec 19 2024 9:02AM
Subject: Re: Clarification on 2.4.5
← Previous message | No next message

It depends on what the application does. There is an exception for pages that are the result of, or a step in, a process. If the application is just one process with multiple pages, the exception would apply to all pages. If the application is a collection of entirely separate processes, such as an online accounting system, there should be multiple ways to locate the starting point for each process.

Steve Green
Managing Director
Test Partners Ltd