What we build to
We build to the Web Content Accessibility Guidelines at level AA, the current version.
We say build to rather than conform on purpose. Conformance is judged page by page and state by state, so a flat claim would have to stay true on every page we ship after the day we made it — including the ones we have not written yet.
What that means in practice, on every page: every image carries a text alternative or is marked as decorative; every form field has a label; colour is never the only way something is signalled; text meets the contrast the guidelines set; everything that works with a mouse works with a keyboard; the focus outline stays visible; and links say where they go.
How we check
We check every page of this site with an automated checker — every page, not a sample — on a desktop and on a phone at the narrowest width the guidelines ask for. We also check that everything can be reached and used with a keyboard alone.
An automated checker finds roughly a third of real problems, so passing one is a floor and not a result. We re-run the checks when the site changes, not on a calendar.
What we do not claim
We do not claim this site is fully conformant. No outside body has assessed it — the checks are our own, and we would rather say that than imply otherwise. No automated tool, plugin or overlay makes a website conform, and we do not sell one.
Our interactive demos are the hardest part of this site to get right. They are covered by everything above, and they are where we expect to be wrong first.
If something here blocks you
Email hello@noorflows.com and tell us what you were trying to do and what stopped you. We will fix it, or tell you plainly why we cannot and what to use instead. How and when we reply is the same as for anything else you send us, and it is written down in our terms.
You do not need to know the name of the problem. The menu will not open with my keyboard is enough.
Work we build for clients
When we build something for a client, the client runs it under their own name, so the legal duty for it sits with them rather than with us — the same way it does for their own website.
What we do is build to the level agreed in writing before the work starts, test it, and hand over the record of what was tested and what it showed, including anything it does not support. Where part of what we build has no interface for a person to use, there is nothing for the guidelines to attach to, and we say so rather than pretending it passed.
How we work and who carries which duty is set out on our trust page.