Contrast From the Palette
Decided when colours are chosen, not corrected afterwards.
An accessibility audit at the end of a project finds violations a tool can detect and fixes them individually. What it cannot fix is a keyboard order that makes no sense or a flow that loses focus, because those are structural. Accessible website design means making those decisions correctly while the design is still being made.
Automated checks catch a minority of real accessibility problems. The rest are design decisions.
Decided when colours are chosen, not corrected afterwards.
Every interactive element reachable and operable, in a sensible order.
Designed deliberately rather than removed because it looked untidy.
Headings as hierarchy, landmarks as landmarks, buttons as buttons.
Animation reduced for anyone who has asked for that.
Four practical requirements, none of which is exotic.
Discuss Accessibility →Sufficient contrast, text alternatives, content that survives being resized.
Usable by keyboard, with visible focus and adequate target sizes.
Predictable navigation, clear labels, errors that explain the fix.
Semantic markup that assistive technology can interpret.
Decisions made during design, verified by testing rather than discovered by it.
For regulated sectors, this pairs with healthcare and financial website design.
Decisions during design; testing to confirm rather than to discover.
Contrast established before anything is designed with it.
Order and focus as part of the layout.
Real headings, real buttons, real landmarks.
Keyboard and screen reader, on the actual build.
So it survives future changes.
They are useful and they cover a minority of what matters.
Missing alt attributes, insufficient contrast, unlabelled form fields, duplicate identifiers — mechanical failures with a definite answer.
These are worth catching and they are the easy half. A site can pass every automated check and remain difficult or impossible to use with a keyboard or a screen reader.
The tools cannot judge whether alt text is meaningful, whether a heading structure reflects the actual hierarchy, or whether a custom control announces its state.
Because the browser default outline is visually plain, and it appears on mouse clicks as well as keyboard use, which designers read as a flaw.
Removing it makes the site unusable by keyboard: the user has no idea where they are. It is one of the most common and most damaging accessibility failures, and it is always deliberate.
The correct response is to design a focus style that fits the site rather than to remove it. It takes one rule and it is the difference between operable and not.







Accessible website design builds sites usable by people with disabilities — sufficient contrast, keyboard operation, visible focus, semantic structure and respected motion preferences — decided during design rather than audited afterwards.
No. Audits catch mechanical failures like contrast and missing labels. They do not fix keyboard order, focus management or heading hierarchy, because those are structural decisions.
They cover a minority of what matters. A site can pass every automated check and still be unusable with a keyboard or screen reader, which is why manual testing is part of the work.
Because a keyboard user then has no idea where they are on the page. It is one of the most damaging accessibility failures and it is always deliberate. Design a focus style instead of removing it.
Indirectly. Semantic structure, real headings and text alternatives help both. Treat accessibility as its own goal — the search benefit is a side effect, not the reason.
Still deciding if accessible website design is right for you?
Talk to UsThe browser draws a plain ring around whatever element has keyboard focus. It is not attractive, it appears on mouse clicks too, and on nearly every design review somebody asks for it to go.
It goes. One line of CSS, and the site looks tidier. It also becomes impossible to operate by keyboard, because there is no longer any indication of where you are.
It is the most consequential accessibility failure on the web and it is never an oversight. It is a design decision, made deliberately, by someone who did not know what the ring was for.
Send us your site. We will check contrast, keyboard operation and structure, and tell you what is mechanical and what is structural.
