Accessibility Statement
Our commitment
The Semiconductor Hub targets WCAG 2.1 Level AA across the platform. We run an automated accessibility scan (axe-core) on every code change against our key flows: home, registration, directory search, job applications, community posts and published articles. Critical violations block release.
Known limitations
Our own testing currently shows two recurring, non-critical issues we are actively working through: some text does not meet our full color-contrast target on certain surfaces, and a few in-text links are not clearly distinguishable from surrounding text without relying on color alone. Neither blocks core functionality, and both are tracked internally for a fix.
What we have built in
- A skip-to-main-content link for keyboard users on every page.
- Full keyboard navigation of the primary menu, command palette and account controls.
- Support for a system or manually chosen dark theme.
- Semantic landmarks and heading structure on every page template.
Feedback
Accessibility is an ongoing effort, not a one-time checklist. If you hit a barrier anywhere on the Hub, please report it using the form below. We track every report on the same acknowledgement and resolution timeline as any other grievance filed with us.
This is the standard the Hub is built and tested against. It is a target we test toward, not a certified claim of full conformance. Running body text is held to a contrast of at least 7 to 1 in both the light and dark themes.
What the latest audit covered
- Automated scan: not yet run for this release. It covers every public page in both themes, on a desktop and a phone screen size, and fails on any rule violation.
- Screen reader on Windows (NVDA with Chrome or Firefox): Not yet carried out.
- Screen reader on Apple (VoiceOver with Safari on macOS or iOS): Not yet carried out.
- Keyboard only: Not yet carried out.
- Magnification to 200 and 400 percent, reflow at 320 CSS px: Not yet carried out.
Known limitations
- The manual passes with a screen reader (NVDA on Windows, VoiceOver on Apple devices), keyboard only, and magnification and reflow have not yet been carried out.
- Signed-in pages (account, dashboard, workspace and admin) are not covered by the automated scan.
- The scrolling company logo strip on the home page pauses when a pointer or keyboard focus is on it, but has no separate pause button.
- Content supplied by members, companies and third parties (uploaded images, embedded media, linked documents such as PDFs) may not meet the standard. When told about a problem, we ask the contributor to correct it or correct it ourselves.
- Charts and data visualisations may be harder to use with a screen reader than the text and tables that accompany them.
Who is responsible
The platform owner holds the accessibility gate: no release ships without their sign-off on the audit record.
How quickly we respond
We aim to acknowledge every barrier report within 24 hours. Some regions have their own timing, shown when you file a report. No barrier reports have been received in the last 12 months.
- Press Ctrl and K together (Command and K on a Mac) on any page to open the command palette. If you cannot use a key combination, the search button in the site header, or the "Jump to anywhere on the Hub" row in the mobile menu, opens the same palette.
- Type to filter pages and matching content. The up and down arrow keys move between results, Enter opens the highlighted one, and Escape closes the palette. Tab stays inside the palette while it is open.
- Screen readers are told how many pages and content results match as you type, which result is highlighted, and the name of the group it belongs to.
- If nothing matches, pressing Enter runs a full search of the Hub for what you typed.
If something on the Hub is hard to use with a screen reader, keyboard-only, or any other assistive technology, tell us. It goes straight to a real person, tracked on the same acknowledgement and resolution timeline as every other grievance filed here.
Report a barrier →