At a glance
We target WCAG 2.2 Level AA for the public website. The Prism candidate receives local automated and manual checks. These checks are not third-party certification or exhaustive assistive-technology testing.
01 / What is included
The public journey should stay operable.
Navigation, guides, tools and enquiry forms use semantic headings, labelled controls and visible focus. Essential marketing content is present in the first HTML response rather than being hidden behind animation or client-side rendering.
- A skip link on shared pages
- Keyboard-operable navigation and browser-local tools
- Reduced-motion handling for transitions
- Responsive layouts and resizable browser text
- Text alternatives for meaningful product imagery
02 / Motion
Content is available immediately.
The Prism homepage has no opening animation or timed reveal. The product explanation and links are available immediately. Interface transitions are suppressed when the browser requests reduced motion.
03 / Current evidence
Automated and manual checks, with an honest boundary.
The Prism candidate is checked locally with Axe rules for WCAG A, AA and 2.2 AA on representative page types, alongside browser checks of keyboard navigation, focus, labelled forms and responsive layouts. Narrow-screen checks include 320 and 390 CSS-pixel widths; tablet and desktop checks include 768, 1024 and 1440 widths. These candidate checks must be repeated at the final deployed origin.
- Representative automated checks are a limited sample, not a complete conformance claim
- No claim of formal WCAG certification or complete conformance
- Not every route, browser, operating system, screen reader, speech-input tool or high-contrast combination has been manually tested
- Field evidence and direct disabled-user feedback require real use over time
04 / Known limits
Passing automation is not the end of the review.
Long resource documents and browser-generated downloads can behave differently across reading and printing software. The sample workspace is a separate demonstration and needs its own application accessibility review.
The enquiry route depends on a working database; when storage is unavailable it should fail honestly instead of presenting a false success. Email remains the alternative contact route.
- The sample workspace demonstrates an interface; it is not a certified accessible SaaS product
- Generated files have not been tested with every document reader
- Future product features need their own accessibility acceptance evidence
05 / Report a barrier
Tell us what got in the way.
Use the contact page or email karan@techgeekuk.com. Include the page address, what you were trying to do, and the browser or assistive technology involved if you are comfortable sharing it.
Messages are reviewed manually and no response-time SLA is published. A stored form receipt does not mean a person has already read the report.
- Do not include passwords, customer artwork or sensitive job data
- A form receipt is shown only after the message has been stored
- Ask for the public-site information in a different format or route if the current one is inaccessible