Accessibility
Accessibility Statement
Adviser Forum should be usable by every UK financial services professional, including those using assistive technology. This page explains what we aim for, what we know isn't perfect yet, and how to get in touch if you hit a barrier.
Our commitment
We aim to conform to WCAG 2.1 level AA across the public forum, sign-in, registration, discussions, member directory and account settings. During beta, some areas are still being reviewed against that standard.
What we've built in
- Keyboard navigation across all interactive controls.
- Semantic HTML with visible focus indicators and skip-to-content targets on primary layouts.
- Colour choices tested for contrast against WCAG AA on body text, interactive components and status indicators.
- Form fields with associated labels, inline validation and error summaries.
- Support for OS-level dark mode via the Theme preference in your account.
- Responsive layouts that reflow down to 320 px width and up to 200% browser zoom.
Known limitations during beta
- Rich-text discussion composer relies on standard textarea and does not yet announce toolbar state changes with ARIA live regions.
- Some third-party OAuth screens (Google sign-in) are not controlled by us and may not meet WCAG 2.1 AA in every locale.
- Older discussions imported from other systems may have inconsistent heading structure until re-edited by a moderator.
These are on our backlog and will be resolved before the beta label is removed.
Reporting an accessibility issue
If something on Adviser Forum is difficult or impossible to use with assistive technology, email accessibility@adviserforum.co.uk with the page URL and a short description. We aim to acknowledge within 2 working days and to fix critical issues within 20 working days.
Enforcement
The Equality and Human Rights Commission (EHRC) enforces the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. Adviser Forum is a private-sector service and is not in scope of those regulations, but we hold ourselves to the same WCAG 2.1 AA benchmark. If you are not satisfied with our response, contact us again and ask for a senior review by the Adviser Forum team.