Accessibility
The work should be usable, too.
The Explainable Broker is working to make its website and digital content usable by people with disabilities. Clear reasoning is not very useful if the page itself gets in the way.
The commitment
Make the path to the answer clear.
Accessibility is part of the site’s ongoing design and publishing work. The target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We review the experience as pages, newsletter issues, forms, and embedded services change.
Accessibility is not a one-time badge. When we find a barrier, the job is to repair it, provide another way through, and use what we learned in the next release.
The practical work
What we are working to support.
-
Keyboard access
Clear focus indicators, sensible focus order, and controls that do not require a mouse.
-
Structure and labels
Useful headings, landmarks, link names, and form labels for assistive technology.
-
Readable presentation
Strong contrast, responsive layouts, and content that remains usable when text is enlarged.
-
Meaning beyond the image
Alternative text or nearby explanation when an image carries information.
-
Plain language
Benefits terminology is explained when it matters, without hiding the limitation or tradeoff.
Where control is shared
Some parts of the experience come from other providers.
Beehiiv powers the website, subscriptions, newsletters, and comments. Cal.com supports scheduling. Cloudflare helps protect the case form. Those providers control parts of their interfaces, so some barriers may not be fixable directly in The Explainable Broker’s page code.
We still want to know when a third-party control gets in the way. We will look for a practical correction or an accessible alternative.
Tell us where you got stuck
A report should lead to a next step.
If you have difficulty accessing a page, reading an issue, submitting a case, or scheduling time, email [email protected]. Include the page and the task you were trying to complete. Your browser, device, or assistive technology is helpful context, but it is not required.
We will work to provide the information or service through an accessible alternative and use the report to improve the site. Do not include protected health information, claimant details, or confidential employer information in an accessibility report.
Need another route?
Tell me what you were trying to do.
Name the page and the task. I will help find an accessible way to the information or service and use the problem to make the site better.