US Job AtlasSearch jobs
Menu — navigation

Accessibility

Accessible job discovery for more people.

US Job Atlas is designed to make job discovery easier to navigate, understand, and use across devices and input methods.

Last accessibility review:

Accessibility at a glance

Practical considerations built into the experience.

These are ongoing design and engineering practices, not a certification or a statement of full conformance.

Keyboard-friendly navigation

Links, native controls, and menus are designed to work with a keyboard.

Visible focus indicators

Common interactive controls receive a clear focus outline.

Readable visual hierarchy

Headings, text sizing, and status labels are designed to be understandable.

Responsive layouts

Content reflows for smaller screens and common zoom levels.

Semantic page structure

Landmarks, headings, labels, and descriptive links support navigation.

Reduced-motion awareness

Non-essential motion is minimized when a reduced-motion preference is set.

Our approach

Accessibility is part of useful job discovery.

We aim to make public job search, company, category, location, source, and support pages easier to use with a keyboard, a range of screen sizes, and assistive technology. We review accessibility as pages and components evolve.

Keyboard & focus

Core paths are designed to work without a mouse.

Public navigation, search links, forms, filters, pagination, job-detail links, and standard controls are built with keyboard-operable HTML elements. Use Tab and Shift + Tab to move through controls; native links, buttons, selections, and disclosure controls respond to their standard keyboard behavior.

Interactive links and common form controls receive a visible focus outline. Focus styling is intended to make the current keyboard position clear rather than relying on color alone.

Structure & assistive technology

Information is organized for more than visual scanning.

Pages use semantic landmarks such as header, navigation, main, footer, sections, headings, lists, and native form controls. Search fields and filters use labels or programmatic names; link text is written to communicate destination or action where practical.

Meaningful visual content is given text alternatives where needed. Decorative icons and graphics are hidden from assistive technology so they do not create unnecessary repetition.

Visual & responsive access

Clear hierarchy across screen sizes.

The public interface uses readable type, consistent headings, visible control boundaries, and text labels alongside status or workplace indicators. Layouts are designed to reflow across mobile, tablet, and desktop widths without relying on a single screen orientation.

We review pages at common viewport widths and at enlarged text or zoom where practical. Color is not intended to be the only way to understand a primary action, status, workplace type, or job source context.

Search & job discovery

Public search controls and listings are part of the review scope.

Jobs, company, category, and location pages use native search and selection controls. Job cards and detail pages pair source, workplace, verification, and application context with text rather than requiring a user to infer meaning from decoration alone.

Location discovery can use approximate request context or a manually selected place. Location information is presented in text, and location context can be imperfect—especially with VPNs, mobile networks, or corporate networks. Learn more in the Privacy & Data Practices Center.

Motion & current limitations

We respect motion preferences and continue to look for barriers.

Non-essential transitions and animations are reduced when a visitor’s device requests reduced motion. The public experience does not rely on flashing content or motion alone to communicate a core result or action.

We continue to review accessibility as the product changes and may identify issues not yet documented here. A report from a visitor can reveal a barrier that automated checks or a limited manual review did not catch.

Feedback & review

Tell us when something gets in the way.

If you encounter an accessibility barrier, email contact@usjobatlas.com. Including the page URL and the feature or task that was difficult helps us investigate. Browser or device details and assistive technology information are optional.

Please do not include passwords, application credentials, medical information, or other sensitive personal information in an accessibility report.

01

Receive

We receive the report through the official contact channel.

02

Review

We review the affected page, feature, and available context.

03

Test

We check the component and relevant user path where practical.

04

Prioritize

We prioritize work based on impact, scope, and available information.

05

Follow up when useful

We may request more context when it helps us understand the issue.

Official accessibility contact

Accessibility feedback and questions

Use the official US Job Atlas address for a barrier report or an accessibility question.

Standards & related pages

How we review the public experience.

Our ongoing checks include keyboard-only paths, visible focus, semantic structure, labels and descriptive links, responsive layouts, reduced-motion behavior, and manual visual review. Automated checks can help find issues, but do not replace human testing or feedback from people who use assistive technology.

WCAG 2.2 provides a useful technical reference for this work. For related public information, see our Privacy & Data Practices Center, Terms of Use, Contact Center, About page, and Sources & Transparency Hub.