1.1 Target: WCAG 2.2 Level AA. Web Content Accessibility Guidelines 2.2, conformance level AA, is the target for every property listed above.

1.2 Related frameworks a buyer may ask about. Pensieve does not claim conformance with any of these; it records how they relate to the target, so that a procurement question can be answered without a meeting.

1.3 Why AA and not AAA. Level AAA is not achievable across a dense clinical interface without degrading the clinical workflow, and a claim to it would not survive testing. Pensieve targets what it can meet.

Each item below is verifiable by a reader with a browser, which is why it is stated at this level of specificity.

2.1 Structure. Semantic HTML with a correct heading hierarchy and no skipped levels. Landmarks for navigation, main content and complementary regions. Every page has a unique, descriptive title.

2.2 Keyboard. Every interactive control is reachable and operable by keyboard. Focus order follows reading order. Focus is always visible. There are no keyboard traps. A skip-to-content link is present.

2.3 Colour and contrast. Text meets the Level AA contrast ratios. No information is conveyed by colour alone: a status is a colour and a label or an icon. This rule is also binding on every document in the Trust Center under SPEC-005 Section 7.

2.4 Text. Text resizes to 200% without loss of content or function. The interface reflows rather than requiring horizontal scrolling at standard zoom levels.

2.5 Non-text content. Images that carry meaning have text alternatives. Decorative images are marked as decorative. Every diagram in a Pensieve document has a text description, and the document is comprehensible without the image (SPEC-005 Section 7).

2.6 Forms. Every field has a programmatically associated label. Errors are identified in text, not only by colour or position, and describe how to correct them. Required fields are marked in text.

2.7 Tables. Every data table has a header row. Merged cells are not used, because they break both screen readers and print pagination.

2.8 Motion and timing. No content flashes more than three times per second. No essential process has a time limit that cannot be extended, other than a session timeout, which warns before it expires and can be extended.

2.9 Language. The page language is declared. Documents declare en-IN.

3.1 The Platform is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means parts of the content do not fully conform.

3.2 The assessment is self-assessed and internal. It was performed by Pensieve's own engineers using automated testing and manual keyboard review. It has not been audited by a third party, and no independent Accessibility Conformance Report exists.

3.3 There is no VPAT today. An Accessibility Conformance Report in VPAT format is planned as REP-GL-018, targeted at Roadmap vpat target, owned by Roadmap vpat owner. A hospital that requires one before signature should say so early; it is one of the few artefacts Pensieve cannot produce inside the fourteen-day window.

3.4 No assistive-technology test matrix is published. Pensieve has not completed a formal test pass against a published matrix of screen readers, magnifiers and voice-control software, and therefore does not claim support for any specific assistive technology by name. Claiming support that has not been tested is worse than admitting the gap. The first published matrix is targeted at Roadmap accessibility at matrix target.

3.5 No user testing with people with disabilities has been conducted. This is the most significant gap in this statement, and automated tooling does not substitute for it.

Listed so that a hospital can plan around them, not so that they are excused.

4.1 Dense clinical grids. High-density tabular views (ward lists, order queues, billing worksheets) are the hardest surfaces to make fully conformant and the most likely to contain barriers. They are the first target for remediation.

4.2 Complex interactions. Drag-to-reorder, canvas-based views and multi-pane layouts may not be fully keyboard-operable in every case. Where a keyboard alternative is missing, that is a defect, not a design decision.

4.3 Third-party components. Embedded components (a payment gateway page, a mapping view, an authentication widget belonging to the hospital's own identity provider) are outside Pensieve's control. Pensieve states which are present and will replace a component whose accessibility cannot be remediated.

4.4 Content supplied by the hospital. Templates, letters, form labels and images that a hospital configures in its own tenancy are the hospital's content. Pensieve provides accessible defaults and will not overwrite a hospital's choices.

4.5 Scanned documents. A scanned image uploaded into a patient record is not machine-readable text. Pensieve does not perform optical character recognition on it and does not claim to.

4.6 PDF and print output. Generated documents follow the structural rules in SPEC-005 Section 7: heading hierarchy, header rows, no merged cells, text descriptions, but are not tagged PDF today. A hospital requiring tagged PDF should raise it; it is a known gap with no committed date.

4.7 Older releases. Under DM-4, a hospital running an older release does not have accessibility improvements shipped after that release. POL-GL-064 governs version currency.

5.1 Where. Through the Support Center at [TO BE SUPPLIED], or by e-mail to info@pensievelabs.org with "Accessibility" in the subject line. A member of the public who is not a Pensieve customer may use info@pensievelabs.org.

5.2 What to include. The page or screen, what you were trying to do, the barrier, and the assistive technology, browser and operating system in use if any. A description in a sentence is enough; a hospital should not have to write a bug report to be heard.

5.3 What happens.

5.4 Escalation. If the response is inadequate, escalate under POL-GL-056 4. A barrier affecting a member of staff with a disability may also be raised as a grievance under POL-GL-066.

5.5 Reported barriers are counted and the count published in the Transparency Report (POL-GL-068).

6.1 Accessibility acceptance criteria are part of the definition of done for interface work under POL-GL-118. A control that cannot be operated by keyboard is not finished.

6.2 Automated accessibility checks run in the build pipeline. They catch a minority of issues, and Pensieve does not present a passing automated check as conformance.

6.3 The Document Authoring Standard (SPEC-005 Section 7) binds every author of every artefact in the Trust Center. Accessibility is therefore enforced on documents as well as on the Platform.

6.4 Where a hospital's procurement requires an accessibility commitment in the contract, it is recorded on the Order Form. Pensieve will commit to this statement and to the remediation timelines in 5.3; it will not commit to a conformance level it has not tested.

8.1 Reviewed semi-annually under POL-GL-502, and after any significant interface change.

8.2 The conformance status in 3 is restated at each review with a date. A statement that is not re-tested is withdrawn rather than left standing.