What is built,What is built, and what is missing.and what is missing.

02 Target and scope

The standardThe standard we are aiming at.we are aiming at.

• Target standardWCAG 2.2 Level AA, the version the W3C published as a Recommendation on 5 October 2023. Conformance is partial: the checks listed below pass, and the ones marked as untested are untested rather than assumed.
• Conformance claimNone is made at this time. The page below is a statement of measures and gaps, not a conformance claim.
• ScopeThis website and every route on it, as built on this deployment.
• Out of scopeClient deployments linked from the Work pages, which are separate sites built under each client's own scope, and third party content on other domains.
• Separate applicationsThe client dashboard behind Client log in is a separate application this domain passes through to, outside this assessment. The demo sites that used to sit under /demo, and the pages under /sapore and /proposals, were retired on 10 October 2026 and their links now lead to the home page. The product demos at /demo/analytics and /demo/portal are pages of this site and in scope.
• Assessment methodSelf-assessment against the source by the people who built it, with every route rendered and measured in a real browser engine.
• Formal evaluationNone has been commissioned. Everything stated here was measured in-house and the method is described, so it can be repeated or disputed.
• Statement dateFirst prepared 6 October 2026. Re-checked against the source on 9 October 2026, the day the phone motion layer and the water ripple were added. The zoom, reflow and contrast sweeps in section 04 date from the 6 October build and have not been re-run.

03 What this site does

Measures you canMeasures you can check in the source.check in the source.

This is a heavily animated site, which is exactly why the list below matters. Motion here is an enhancement layered onto a document that is complete without it.

Semantic structure

One h1 per route, headings in order beneath it, and real landmarks: a banner, a primary navigation, a main region and a footer. A skip link to the main region is the first thing that receives focus on every page. Headings, landmarks, skip link

Visible focus

Keyboard focus is always drawn. Buttons, links, work cards, filters and form controls each carry a two pixel brass outline with an offset, so the ring sits clear of the element rather than on top of it. The default outline is never removed without a stronger replacement. The ring is held back only after a tap or a click, never a key press: a dialog or menu opened by touch takes focus as a whole, and focus returned to a button when a dialog closes is not drawn until it moves. Focus is never suppressed for the keyboard

Reduced motion

Under a reduced motion preference, travel is replaced by a cross-fade or by nothing. Reveals resolve in place, the curtains over headlines and work screenshots are skipped, and the foil shimmer is not drawn. Parallax, the scrubbed hairlines and smooth scrolling are never created, and the custom cursor and the magnetic buttons are off. The hero film and the work clips rest on their still posters, the moving rows stand still as ordinary scrollers, and page changes no longer slide.

On phones the touch motion layer is off too: frames do not zoom, drift or lean, headlines do not re-shimmer, buttons do not press in under the finger, and the hero does not push in as you leave it. The water ripple under the finger is never created: no canvas, no touch listener. Nothing is hidden as a result, the same content arrives without the movement. Cross-fade in place of travel

Touch effects are drawing only

The water ripple and the phone motion layer read where your finger is only to draw under it. They collect and send nothing: no position, gesture or timing leaves your device. The ripple canvas is hidden from assistive technology, never takes a tap or holds a scroll, and is off while the quote form or the menu is open. With a mouse or trackpad neither effect runs. Nothing recorded, nothing sent

Content is never gated behind motion

The hidden resting states that make a reveal possible are applied only when scripting is available. With JavaScript blocked, unavailable, or the animation library failing to load or throwing an error, every block renders visible and the page reads as an ordinary document. Two gaps in section 04 are the exceptions: hidden content on the home page, and forms that need scripting to send. No script, still readable

Text alternatives

Every screenshot carries a description of what is actually in the frame rather than a filename. Decorative rules, marquees, dot separators, the hero footage and the looping work clips are marked as decorative and removed from the accessibility tree. The footage and the clips are silent, carry no information that is not also written on the page, and are out of the tab order. Described, or explicitly decorative

No information by colour alone

Every state carries a second signal. The current nav route is marked as the current page, filters expose a pressed state, the package selector on the home page exposes a selected state, each question on the home page reports whether it is open, and an invalid form field is marked invalid and given a written message in a live region rather than only a red border. State is announced, not only tinted

Keyboard operation

Interactive things are buttons and links, not styled div elements pretending to be them. The mobile menu reports whether it is expanded and what it controls, keeps its links out of the tab order while closed, and closes on Escape with focus back on the button. The quote dialog holds focus while open, closes on Escape and returns focus to whatever opened it. The package selector follows the standard tab pattern, with arrow keys, Home and End. Form errors are written into a polite live region, and the first invalid field takes focus on a failed submit. Reachable, operable, announced

Contrast and type

The readable gold is a single value at a measured contrast ratio of 5.05 to 1 on the paper ground, and it is the only gold allowed to carry small text. The decorative leaf gold is restricted to hairlines, surfaces and display sizes. Type is set in relative units and reflows down to a narrow viewport. The typefaces are served from this site's own domain, so they do not depend on a third party being reachable. 5.05 to 1 for small gold text

04 Known gaps

The list we wouldThe list we would rather you heard first.rather you heard first.

• Pause controlsThe hero film and the work clips loop while on screen, the band of words on the home, work, platform and contact pages and on the Aerospace Climate, Clarity, Auverne and Emberfell case studies keeps moving, and the rows of apps and testimonials stop only while a pointer or keyboard focus rests on them. None has a pause button. WCAG 2.2.2, at Level A, asks for a way to pause motion that starts on its own and lasts over five seconds, and the W3C says a pause that holds only while focused does not count. A reduced motion preference stops all of them while scripting runs, but the guidance is silent on whether that is enough, and with scripting off the hero film plays regardless. We record an open failure until there is a control on the page.
• Home page without scriptingThe platform selector the 6 October list described is gone, but the same pattern now sits on the home page: the second and third packages and the answers to the questions are hidden in the markup, so with scripting unavailable only the first package shows and no answer opens. The fix is to show them by default and hide them only once the script runs.
• Selector semanticsClosed for the selector now on the site: each tab is wired to the panel it controls and back. Verified in the markup, not yet with a screen reader.
• Filter target sizeThe blog category filters are 38 pixels high with a mouse or trackpad and 44 on a touch screen. Both clear the 24 pixel Level AA minimum; 38 is under the 44 pixels of Level AAA, which this list measures against. The 6 October review found every other button and form control at least 44 pixels high. Inline text links sit outside that guidance, but they are on the list to review.
• Forms without scriptingThe quote form, the contact form, the guides waitlist and the website audit send only through the page script. With scripting unavailable they cannot send. The email address in the footer of every page works without it. The fix is a form that also sends without the script.
• Anti-spam fieldThe quote form, the contact form and the guides waitlist each carry a hidden field that is labelled but marked as decorative. It is out of the tab order and a person will not reach it, which is a deliberate deviation made to stop automated submissions. It is recorded here rather than left unsaid.
• Third party librariesClosed. On 6 October the motion layer and the typefaces loaded from external providers; both are now served from this site's own domain. If the motion layer still fails to load, the page drops to a finished static document.
• Assistive technology testingOn the 6 October build, tested in WebKit, the engine behind Safari, across every route at 1440px, 390px and 320px. No screen reader has been run against this site. VoiceOver, NVDA and JAWS testing is outstanding, and nothing here should be read as a claim about them.
• Zoom and reflowPasses on the 6 October build. Every one of the 51 routes was rendered at 320 pixels wide and at the viewport sizes equivalent to 200 and 400 percent zoom, and none produced a horizontal scrollbar. Two failures found this way have been fixed: a stack label that refused to wrap, and a nav button pushed off the edge.
• Full contrast sweepDone on the 6 October build. 6,294 text-and-background pairs were measured from the computed styles on every route, each against its own threshold. All 6,294 pass; the tightest is 4.54:1 against a 4.5 requirement. This pass found 519 failures caused by one grey that was documented as large-text-only and then used on captions throughout, and that colour has been darkened.
• Third party auditNo independent audit has been commissioned. The plan is to commission one before this site carries a conformance claim stronger than partial.
• Remediation timetableThe open items are the pause controls, the home page and the forms without scripting, the filter size with a mouse, and screen reader testing. No date is given here, because a date nobody is accountable for is worse than an admission.

05 On the sites we build

The same floor,The same floor, under your site.under your site.

How accessibility goes into a client build, and where it stops. None of it is a certificate, and anything your file needs beyond it is named in the scope or not promised.

Named in the scope

Scope, price and timeline are agreed in writing before any work begins, and the accessibility target belongs in the same document. If your firm needs a named standard, such as WCAG 2.1 AA because a federal rule names it, it is written there. If none is named, the target is this site's, WCAG 2.2 Level AA, reported as partial until tested otherwise. The target is in writing

Built in, not added later

A client site is built with the techniques in this site's source: motion over a page that is complete without it, a reduced motion path for every animation, focus always drawn, real buttons and links, measured colour values, and form errors written out and announced. Part of the build, not a retrofit

Checked before launch

Before a client site goes live, every route is checked: with the keyboard alone, at 320 pixels wide and at the equivalent of 200 and 400 percent zoom, with reduced motion on and with scripting off, for text contrast measured from the computed styles, and for a description or a decorative mark on every image. What passed, failed and was fixed comes to you in writing, with the date and the build. Results in writing, dated

Not checked unless scoped

Screen reader testing with VoiceOver, NVDA or JAWS, and testing with people who use assistive technology, are part of a build only when the scope names them. We have not yet run screen reader testing on our own site and will not claim results that were not run and recorded. An independent audit is not something we can provide: your firm commissions it, and the fixes it calls for are quoted as changes unless the scope covers them. Name any of these before the scope is signed. Untested means untested

Your content and your choices

Product, medical, financial and other regulated claims are approved by you before they go live. Documents you ask us to post, such as PDFs, go up as supplied, and making them accessible is yours unless the scope includes it. Embedded third party tools, such as booking, chat or payment widgets, carry their own accessibility, which we can test and describe but cannot change. We are not your regulatory, legal or compliance reviewer, and that includes deciding which accessibility law applies to you. You approve, counsel decides

Fixes after launch

The website and its code belong to Fluxaro and no copy is handed over, so changes to it, accessibility fixes included, are made by us. A barrier on a site we built comes in through the same address as one on this site, and whether its fix is inside the agreed scope or quoted as a change depends on the scope: the practical reason to name the target there. When the service ends the site goes offline and the domain transfers to you on request, with any registrar or transfer fee yours, so a replacement site starts its own accessibility record. One address, one owner of the code

06 The rules your sector works under

The law your fileThe law your file already answers to.already answers to.

• ADA Title IIITitle III of the Americans with Disabilities Act covers public accommodations, and the statute's own list includes the office of an accountant or lawyer, a bank, an insurance office, a pharmacy, a hospital and the professional office of a health care provider. The Department of Justice has consistently taken the position that the ADA applies to what such businesses offer on the web.
• No Title III web ruleThe Department has no regulation setting a technical standard for private websites. Its guidance of 18 March 2022 calls existing standards such as WCAG helpful guidance and leaves businesses flexibility in how they comply. The choice of a measurable target is yours, which is why we ask for one in the scope.
• Section 508Section 508 binds federal agencies, not private firms, but it reaches suppliers through procurement: technology an agency procures, develops, maintains or uses must conform to the Revised 508 Standards, which apply WCAG 2.0 Level A and AA to web content. Selling to a federal agency is the setting the 508 edition of the VPAT was written for.
• HHS Section 504 ruleIn May 2024 the Department of Health and Human Services adopted a rule under Section 504 of the Rehabilitation Act requiring recipients of its federal financial assistance to make their web content and mobile apps conform to WCAG 2.1 Level A and AA. The duty sits with the recipient and covers content it provides directly or through contractual, licensing or other arrangements, so a site an outside studio builds for a recipient is still the recipient's to answer for. The rule has limited exceptions. It can matter to medical and dental groups that receive HHS funding, and to some pharmaceutical and research work.
• HHS compliance datesOriginally 11 May 2026 for recipients with fifteen or more employees and 10 May 2027 for smaller ones. An interim final rule, effective 7 May 2026, moved both by a year: to 11 May 2027 and 10 May 2028. Only the dates moved; the standard did not. Whether your firm is a recipient is a question for counsel.
• State lawSome states add their own remedies. In California the Unruh Civil Rights Act makes a violation of the ADA a violation of state law as well, with damages of no less than four thousand dollars for each offence. Whether a state law like this reaches your site is a question for counsel.
• European Accessibility ActDirective (EU) 2019/882 has applied since 28 June 2025 to covered products and services placed on the EU market after that date, including online shops and banking services, and a provider must describe how its service meets the requirements. Service businesses with fewer than ten employees and under two million euros in turnover are exempt. If your firm sells covered services to consumers in the EU, ask counsel whether the Act, and the member state law that carries it, applies to you.

07 Reports and attestations

What to ask for,What to ask for, and what we can supply.and what we can supply.

• VPATThe Voluntary Product Accessibility Template, from the Information Technology Industry Council: a blank form that turns a standard into testing criteria. The current version, 2.5Rev, has four editions: 508 for US federal procurement, EU for EN 301 549, WCAG for WCAG 2.2, and INT, which covers all three.
• ACRAn Accessibility Conformance Report is a VPAT completed for one specific product. The Council does not review or approve them, or require third party review, so a report is worth what its testing was: who, how and when. Ask for the method and the date with it.
• We can provideFor a site we build: a self-assessed accessibility statement in the form of this page, and on request a self-assessed ACR on the WCAG or 508 edition of the VPAT. Each is labelled as self-assessed, dated, tied to a named build and states its method. Name either in the scope so it is priced with the work.
• We cannot provideAn independent audit, an ACR prepared by a third party, a certification or seal of any kind, or screen reader results we have not run. Fluxaro holds no SOC 2, ISO 27001, HIPAA or GxP attestation and has commissioned no independent security or accessibility assessment. If your process requires one, say so before the scope is signed.
• Questions for any vendorWhich standard and level, who tested, with which tools and assistive technology, on what date and build, what failed, and who fixes it after launch. A report that cannot answer those is a claim, not evidence, and the same questions apply to us.