This Accessibility Policy explains the accessibility features that have been included in this site. Please keep in mind that this Accessibility Policy only applies to this Navy Web site for the United States and does not address any other Web site.
Since other Web sites (including those to which we link) have their own practices, we encourage you to refer to the accessibility policies of those sites. Also, we may revise our Accessibility Policy from time to time, so please check this page periodically.
OUR COMMITMENT TO ACCESSIBILITY
We are committed to meet or exceed the requirements of the Workforce Innovation and Opportunity Act (WIOA) of July 22, 2014, the Rehabilitation Act of 1973, as amended, and the Americans with Disabilities Act (ADA) of 1990, as amended. We continually review our site and modify pages to address accessibility problems.
STANDARDS COMPLIANCE
The Web pages of www.navy.com have been designed so they are accessible to all users and compatible with screen readers and other assistive technologies. Generally, we use Extensible Hypertext Markup Language (XHTML) and Cascading Style Sheets (CSS) to create pages and documents that meet accessibility guidelines. In creating XHTML documents, we follow federal regulations along with the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines (WCAG) Priorities 1, 2 and 3.
STRUCTURED SEMANTIC MARKUP
All pages on this site use structured semantic markup: h1 tags are used for main titles; h2 tags for subtitles. This allows people using screen readers to skip around to the various sections of a page.
NAVIGATION AIDS
To aid navigation in text-only browsers, all pages within this site make use of the W3C link relationship names. Netscape 6 and Mozilla Firefox users can also take advantage of this feature by selecting the View menu, Show/Hide, Site Navigation Bar, Show Only As Needed (or Show Always). The following list shows the relationship names and their conventional interpretations:
- alternate – Designates substitute versions for the document. When used together with the hreflang attribute, it implies a translated version of the document. When used together with the media attribute, it implies a version designed for a different medium (or media).
- start – Refers to the first document in a collection of documents. This relationship tells search engines which document is considered by the author to be the starting point of the collection.
- next – Refers to the next document in an ordered collection of documents. User agents may choose to preload the next document to reduce the perceived load time.
- prev – Refers to the previous document in an ordered collection of documents.
- up – Refers to the document above in a hierarchically structured set of documents.
- contents – Refers to a document serving as a table of contents.
- index – Refers to a document providing an index for the site.
- glossary – Refers to a document providing a glossary of terms that pertain to the site.
- copyright – Refers to a copyright statement for the site.
- chapter – Refers to a document serving as a chapter in a collection of documents.
- section – Refers to a document serving as a section in a collection of documents.
- subsection – Refers to a document serving as a subsection in a collection of documents.
- appendix – Refers to a document serving as an appendix in a collection of documents.
- help – Refers to a document offering help (more information, links to other sources of information, etc.).
- bookmark – A bookmark is a link to a key entry point within an extended document or the site. The title attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined for a Site or document.
- meta – Refers to a document that provides metadata in RDF, for instance, about the document.
- icon – Refers to a resource that represents an icon for the document.
- p3pv1 – Refers to a P3P Policy Reference File.
- profile – Refers to a document that defines relationships or provides metadata in RDF, for instance, about the document.