You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Provide a way to skip repetitive navigation links.
Without a skip link, screen readers read out the navigation links on every page before reading the page content. Headings can be a substitute in limited circumstances, but they're not used by all screen reader users, and many other assistive technology users have no way to navigate via headings. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: [Skip to Content]
Section 508 1194.22 (o)
272 327
2
Files
Acceptance Criteria
Fix 'repetitive navigation links' for all findings from SortSite to be 508 compliant.
The text was updated successfully, but these errors were encountered:
Please review Contribution.md before contributing to this project.
Description
Findings using SortSite. SortSite was run locally with Tophat removed and robots.txt allowing PowerMapper.
SortSite can be downloaded/accessed here: https://inside.nasa.gov/webservices/support/section-508-testing-sortsite
Many of the findings here are repetitive (pointing to the footer).
Files
Acceptance Criteria
Fix 'repetitive navigation links' for all findings from SortSite to be 508 compliant.
The text was updated successfully, but these errors were encountered: