Keyboard
Interactive controls should be reachable in a logical order and show visible focus.
Trust and governance · Accessibility
Accessibility is an operating control, not a badge.
SERPIFAI uses WCAG 2.2 as a public reference point for web accessibility review. This statement separates design intent, static checks and direct user-interface testing instead of claiming unverified full conformance.
WCAG 2.2 referenceDirect-test boundariesBarrier reporting
What the public accessibility standard is for
The objective is practical: important public content, navigation, forms and decision tools should remain perceivable and operable across common input methods, zoom levels and responsive layouts. WCAG 2.2 is used as a reference point; this page does not claim independent certification.
Zoom + reflow
At enlarged text or narrow layouts, content should remain readable without forcing two-dimensional scrolling for ordinary reading.
Motion
Non-essential animation should respect reduced-motion preferences and should not carry meaning that disappears when motion is reduced.
Structure
Headings, landmarks, labels and link purpose should support navigation beyond visual styling.
Forms
Labels, instructions and errors should explain the next correction rather than relying on color alone.
Downloads
Portable resources need their own accessibility review; an accessible HTML page does not prove an attached document is accessible.
Four evidence modes
Accessibility evidence is strongest when the mode is named. A static file inspection cannot substitute for a real keyboard, browser or assistive-technology test.
FOCUSName the evidence modeEach mode answers a different accessibility question.
Static review
Inspect semantic structure, labels, CSS risks, contrast candidates and reduced-motion rules in the exact files.
Browser review
Test responsive layout, text resizing to 200%, reflow at 320 CSS pixels (commonly equivalent to 400% zoom from a 1280 CSS-pixel viewport), focus visibility, target usability, form states and overflow.
Assistive-technology review
Use representative screen-reader or other AT workflows when the component materially depends on them.
Document review
Test PDF/workbook/download structure and interaction independently from the web page.
The laptop-readability rule
Accessibility is not satisfied by technically fitting text into a component. Interface labels must remain comfortably legible at normal viewing distance, and the page must simplify before essential text becomes microscopic.
DIRECT TEST
200% text resize + 320 CSS-pixel reflow
These are related but distinct checks. Text resizing should preserve content and functionality at 200%; Reflow should be checked at a width equivalent to 320 CSS pixels for ordinary vertically scrolling content. SERPIFAI should test both directly on the installed route rather than inferring either from CSS alone.
A practical review path
- 01Navigate by keyboard
Tab through the page without using the mouse. Focus should remain visible, logical and unobscured.
- 02Resize text to 200%
Check that content and controls remain available and usable when text is enlarged without treating this as a substitute for reflow testing.
- 03Test 320 CSS-pixel reflow
For ordinary vertically scrolling content, confirm the layout reflows without loss of information or functionality and without two-dimensional scrolling; test justified exceptions such as data tables separately.
- 04Reduce motion
Enable the operating-system reduced-motion preference and confirm that meaning remains available.
- 05Inspect semantics
Check heading order, landmarks, form labels, button/link names and status messaging.
- 06Retest after change
A meaningful component or layout change can reopen the relevant accessibility test.
Current evidence boundary
Static controls
Can be checked from source files and stylesheets. This is useful but not sufficient for final accessibility acceptance; automated or static checks do not establish conformance on their own.
Browser behavior
Requires direct testing on the exact installed route, including responsive states and actual native controls.
Assistive technology
Should remain pending unless a representative AT test was actually performed on the relevant surface.
Full conformance claim
Not made here. A public reference to WCAG 2.2 is not the same as a verified conformance statement.
Report an accessibility barrier
If something prevents you from reading, navigating or completing a public SERPIFAI task, report the route, device/browser if known, what you were trying to do and what blocked you. Do not include sensitive information that is unnecessary to reproduce the issue.
NON-COMMERCIAL NEXT ACTION
Email accessibility report →Report the barrier
Email support@serpifai.com with “Accessibility barrier” in the subject. The issue should be reviewed against the affected surface and retested after remediation.
Accessibility questions
Does SERPIFAI claim WCAG 2.2 AA conformance?
No full conformance claim is made on this page. WCAG 2.2 is a reference point for review, and direct testing remains tied to the exact surface.
Why are 200% text resize and reflow tested separately?
They answer different questions. Text resize checks whether content remains usable when text is enlarged to 200%. Reflow checks whether ordinary content can fit a width equivalent to 320 CSS pixels without loss of information or functionality and without two-dimensional scrolling, except where a two-dimensional layout is required for meaning or use.
Are animated hero instruments required to understand a page?
They should not be. The semantic meaning must be available in text, and reduced-motion preferences should suppress non-essential motion.
Does fixing one page prove the whole site is accessible?
No. Accessibility evidence is surface-specific. Shared components can reduce risk, but materially different tools, forms and downloads need appropriate review.
Complexity should collapse before text size does
A dense analytical product should not solve information overload by shrinking labels until normal laptop users struggle to read them.
Answer, Proof, Next
Expose the primary decision path before analyst controls so users can complete the core task without processing the full evidence graph.
Analyst detail on demand
Detailed scoring, source records and sensitivity belong behind clear controls rather than being visually compressed into the first screen.
Preserve the same task model
Mobile may simplify layout and navigation, but it should not hide material evidence states or change the meaning of the result.
Evidence and source roles
W3C WAI provides the accessibility reference material used here. Its evaluation guidance also makes clear that quick checks and tools are not a complete accessibility evaluation. SERPIFAI's implementation status must still be established through the named review modes on the exact routes.