What is built in, what we know is imperfect, and how to tell us when something does not work for you.
Pages are built from real headings in order, so a screen reader can navigate by structure rather than by guesswork. Every interactive control is reachable and operable by keyboard, and focus is always visible - not removed, which is the usual default. On a phone, interactive targets are at least 44 pixels.
Colour is never the only way something is communicated: regulator badges, comparison ticks and score bars all carry text as well, and the ticks include screen-reader words rather than relying on the shape. Images that carry meaning have alternative text, and decorative ones are hidden from assistive technology rather than described pointlessly. Animation respects the reduced-motion setting.
The contents panel on a phone is a native disclosure element rather than a scripted menu, so it opens, closes and announces itself correctly even if JavaScript never runs.
Wide comparison tables scroll sideways inside their own container. That is better than forcing the whole page to scroll, and it is still harder to read ten columns on a small screen than on a large one. We have not yet found a presentation that is genuinely equivalent rather than merely smaller.
Broker logos come from the brokers themselves and vary in contrast. We set them on a neutral panel rather than altering the artwork, which helps but does not fix every case.
If something here is difficult or impossible to use, please tell us and describe what you were trying to do. A specific report is far more useful than a general one, and we would much rather hear about a problem than leave it standing.