Keyboard
Links, controls, menu buttons and disclosures are intended to be reachable without a pointer.
Accessibility
Information designed
to remain usable.
Progress at Work aims to provide clear, navigable content across devices and interaction methods. Feedback helps identify barriers that testing does not reveal.
Commitment
Accessibility is part of content quality
The site uses semantic headings, landmarks, ordinary links, readable text and visible focus states. Content is written to avoid unnecessary complexity and key information is not conveyed by images alone.
Non-home pages use text, tables and CSS-built diagrams rather than decorative images. Tables may scroll horizontally on small screens to preserve meaning.
Interaction
Supported navigation patterns
Focus
Interactive elements show a visible focus state, and closing a menu returns focus to its trigger.
Menus
Desktop menus support Escape and outside-click closing; the mobile drawer uses expandable groups.
Motion
Reduced-motion preferences are respected by shared transitions and scrolling behavior.
Responsive content
Designed for narrow and wide screens
320–390
Small screens
Single-column reading, wrapping actions and scrollable data tables.
650
Intermediate screens
Comfortable content flow with simplified diagrams.
900
Navigation boundary
Mobile navigation and responsive multi-column layouts.
1280
Wide screens
Constrained reading widths and full editorial composition.
Content approach
Meaning should survive presentation changes
StructureHeadings follow the page hierarchy.
LabelsControls use meaningful names.
ContrastPalette choices support readability.
LanguageInstructions use direct wording.
AlternativesKey meaning is available as text.
Browsers and assistive technology
A practical expectation
The site is intended to work in current standards-based browsers and with common assistive technologies. Exact combinations vary, and a successful automated check cannot guarantee every individual experience.
If a browser extension, device setting or assistive technology changes presentation, the semantic reading order should remain understandable.
Feedback and remediation
Report a specific barrier
What to include
Send the page address, what you were trying to do, the barrier encountered, device or assistive technology if relevant, and a preferred contact method. The report can then be reviewed and an appropriate response discussed.