Skip Links and Landmark Navigation - Bad Example

This example demonstrates the accessibility issues caused by missing skip links and poor landmark navigation that force users to navigate through repetitive content.

Welcome to Our Website

This is the main content area. Users must tab through all the navigation links to reach this content.

Featured Content

This section contains important information that users should be able to access quickly, but there's no way to skip directly here.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Latest Articles

Article Title 1

Article content goes here...

Article Title 2

Article content goes here...

Accessibility Issues

No skip links are provided, forcing users to navigate through repetitive navigation
Navigation uses a generic div instead of semantic nav element with proper landmark role
Main content lacks proper landmark identification and has no ID for targeting
Footer uses a generic div instead of semantic footer element with contentinfo role
No aria-label attributes to provide context for navigation sections
Content sections lack proper labeling and semantic structure

How to Test for the Issue

Press Tab when the page loads and notice there are no skip links available
Use a screen reader to navigate and observe that landmarks are not properly announced
Try to quickly access the main content - you must tab through all navigation links
Notice that navigation sections lack descriptive labels for screen reader users
Observe that the page structure is not programmatically determinable
Test keyboard navigation to experience the frustration of repetitive navigation

WCAG Related Criteria

2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined
4.1.2 Name, Role, Value: For all user interface components, the name and role can be programmatically determined