Accessibility

SentraDeed Accessibility Conformance Report

VPAT® Version 2.5 (Revised Section 508 and WCAG edition), covering WCAG 2.1 Level A and AA.

Report information

Name of product
SentraDeed recorder notification system: (1) staff console web application, (2) resident alert portal web application, (3) notice PDFs generated for county mailing
Version
Pre-release build, September 2026
Report date
Product description
Software for California county recorders under Government Code §27297.7. County staff match recorded documents to Assessor ownership, resolve exceptions and download print-ready, tagged PDF/UA notice batches that the county prints and mails. Residents can sign up for email alerts in English or Spanish.
Contact information
Computer Systems Plus, Inc., 2134 North Fine Ave, Fresno, CA 93727 USA · 559-251-7767 · [email protected]
Notes
This report was prepared by Computer Systems Plus, Inc. from its own testing of a pre-release build. It has not been reviewed by an independent third party. Levels marked “Supports (automated checks; manual verification pending)” are covered by automated tests and by design, but have not yet been confirmed with assistive technology.
Evaluation methods used
  • Automated axe-core checks (WCAG 2.0 and 2.1 A and AA rules) on every staff console and resident portal page, in the console’s light and dark themes and in the portal’s English and Spanish versions, with zero violations.
  • Automated keyboard-only Playwright flows: resident sign-up, confirmation, manage and unsubscribe; console skip link and drawer focus.
  • veraPDF validation of notice PDFs against PDF/UA-1, for every template path (Word template, fillable PDF, default template).
  • No independent third-party audit has been performed.
  • Full screen-reader testing with JAWS, NVDA and VoiceOver has not yet been completed.

Applicable standards and guidelines

Standards covered by this report
Standard or guidelineIncluded in report
Web Content Accessibility Guidelines 2.1Level A (Yes) · Level AA (Yes) · Level AAA (No)
Revised Section 508 standards (36 CFR Part 1194)Yes
EN 301 549No

Terms

WCAG 2.1 report

Tables 1 and 2 also document conformance with Revised Section 508 Chapter 5 (501.1) and Chapter 6 (602.3), which incorporate WCAG 2.x Level A and AA.

Table 1: Success Criteria, Level A

WCAG 2.1 Level A
CriteriaStaff consoleResident portalNotice PDFsRemarks and explanations
1.1.1 Non-text Content (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Console and portal: images, icons and document page images have text alternatives (for example “Page 1 of document …, APN … outlined”); decorative icons are hidden from assistive technology. axe-core finds no violations. Quality of alternative text has not yet been reviewed with a screen reader. PDFs: the county logo is tagged with alternative text; veraPDF checks that figures have alternatives.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableNot ApplicableNot ApplicableNo audio or video content.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableNot ApplicableNot ApplicableNo audio or video content.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableNot ApplicableNot ApplicableNo audio or video content.
1.3.1 Info and Relationships (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Semantic headings, landmarks, labeled form controls and data tables with header cells. axe-core finds no violations. PDFs are tagged (headings, paragraphs, table with header cells) and pass veraPDF PDF/UA-1 validation. Manual screen-reader verification is pending.
1.3.2 Meaningful Sequence (Level A)Partially SupportsPartially SupportsPartially SupportsDOM order and PDF tag order are designed to match the visual order. Automated tools cannot fully confirm reading order; screen-reader review is pending.
1.3.3 Sensory Characteristics (Level A)Partially SupportsPartially SupportsPartially SupportsInstructions refer to control names, not shape or position, by design. Not yet reviewed manually.
1.4.1 Use of Color (Level A)Partially SupportsPartially SupportsPartially SupportsDeadline and status pills carry text (for example “14 · On track”, “Open”) in addition to color. Not yet reviewed manually across every page.
1.4.2 Audio Control (Level A)Not ApplicableNot ApplicableNot ApplicableNo audio.
2.1.1 Keyboard (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableAutomated keyboard-only Playwright flows cover resident sign-up, confirmation and unsubscribe, the console skip link and opening and closing drawers. Not every console workflow has a keyboard-only test yet. PDFs contain no interactive content.
2.1.2 No Keyboard Trap (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableDrawers and menus close with Escape and return focus; covered by automated keyboard tests for drawers. Manual verification of every dialog is pending.
2.1.4 Character Key Shortcuts (Level A)Supports (automated checks; manual verification pending)Not ApplicableNot ApplicableConsole: single-key shortcuts (“/” to search; Enter, J, K, S and ? when working a queue) can be turned off under Profile › Preferences; Escape still closes. Portal: no single-character shortcuts.
2.2.1 Timing Adjustable (Level A)Partially SupportsPartially SupportsNot ApplicableConsole sessions end after 30 minutes of inactivity (12-hour maximum), a security requirement; a warning with an option to extend has not been verified. Portal: emailed confirm and manage links expire (48 hours and 30 minutes); a new link can be requested at any time.
2.2.2 Pause, Stop, Hide (Level A)Partially SupportsNot ApplicableNot ApplicableNo auto-playing, blinking or scrolling content by design. Console progress indicators for file processing have not yet been reviewed against this criterion.
2.3.1 Three Flashes or Below Threshold (Level A)SupportsSupportsSupportsNo flashing content.
2.4.1 Bypass Blocks (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableSkip link to main content and landmarks on every page; the skip link is covered by automated keyboard tests. PDFs are short letters without repeated blocks.
2.4.2 Page Titled (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Each page sets a descriptive title; axe-core checks it. PDFs have a document title displayed in the title bar (checked by veraPDF).
2.4.3 Focus Order (Level A)Partially SupportsPartially SupportsNot ApplicableFocus order follows DOM order; drawers move focus in and return it on close. Only partly covered by automated tests; manual review pending.
2.4.4 Link Purpose (In Context) (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Links have descriptive text; axe-core checks accessible names. Manual review of link wording is pending.
2.5.1 Pointer Gestures (Level A)SupportsSupportsNot ApplicableNo multipoint or path-based gestures.
2.5.2 Pointer Cancellation (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableActions use standard buttons and links that activate on release. Not manually verified for every control.
2.5.3 Label in Name (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableVisible labels are part of the accessible names; axe-core checks this rule where it applies. Manual verification pending.
2.5.4 Motion Actuation (Level A)Not ApplicableNot ApplicableNot ApplicableNo functionality is operated by device motion.
3.1.1 Language of Page (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)The page language is set (English or Spanish in the portal). PDFs declare their language (checked by veraPDF).
3.2.1 On Focus (Level A)Partially SupportsPartially SupportsNot ApplicableNo context changes on focus by design. Not yet reviewed manually.
3.2.2 On Input (Level A)Partially SupportsPartially SupportsNot ApplicableFilters update results in place without moving focus; the portal language switch changes the page language, which the user requests explicitly. Not yet reviewed manually.
3.3.1 Error Identification (Level A)Partially SupportsSupports (automated checks; manual verification pending)Not ApplicablePortal: client-side errors are shown as text next to the field and linked with aria-describedby; covered by automated tests. Console: errors are shown as text; not every form has been reviewed.
3.3.2 Labels or Instructions (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableForm fields have visible labels; axe-core checks label associations.
4.1.1 Parsing (Level A)SupportsSupportsNot ApplicableFor HTML, this criterion is treated as always satisfied under the WCAG 2.1 errata (it is removed in WCAG 2.2). Duplicate IDs are also checked by axe-core.
4.1.2 Name, Role, Value (Level A)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableStandard HTML controls and ARIA attributes; axe-core finds no violations. Custom widgets (tabs, drawers, menus) have not yet been tested with a screen reader. PDFs contain no form fields in the mailed notice.

Table 2: Success Criteria, Level AA

WCAG 2.1 Level AA
CriteriaStaff consoleResident portalNotice PDFsRemarks and explanations
1.2.4 Captions (Live) (Level AA)Not ApplicableNot ApplicableNot ApplicableNo live audio.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableNot ApplicableNot ApplicableNo video.
1.3.4 Orientation (Level AA)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableLayouts work in portrait and landscape; no orientation lock. PDFs are letter-size documents.
1.3.5 Identify Input Purpose (Level AA)Partially SupportsSupports (automated checks; manual verification pending)Not ApplicablePortal: the email field uses the email input type and autocomplete. Console: staff forms collect little personal data; autocomplete attributes not yet reviewed.
1.4.3 Contrast (Minimum) (Level AA)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Partially SupportsConsole (light and dark themes) and portal pass axe-core color-contrast checks. PDFs use dark text on white by design; contrast is not measured by veraPDF.
1.4.4 Resize Text (Level AA)Partially SupportsPartially SupportsNot ApplicableRelative units and responsive layouts; not yet verified manually at 200% zoom on every page. PDFs can be zoomed in any reader.
1.4.5 Images of Text (Level AA)SupportsSupportsSupportsText is real text. The console shows scanned document pages and APN crops, which are images of a recorded document and are essential to the review task.
1.4.10 Reflow (Level AA)Partially SupportsSupports (automated checks; manual verification pending)Not ApplicablePortal: single-column layout at 320 CSS pixels. Console: wide data tables scroll horizontally inside their own region, which is allowed for tables; other pages not yet verified at 320 pixels.
1.4.11 Non-text Contrast (Level AA)Partially SupportsPartially SupportsNot ApplicableBorders of inputs and focus indicators are designed for 3:1 contrast; not measured automatically.
1.4.12 Text Spacing (Level AA)Partially SupportsPartially SupportsNot ApplicableNo fixed-height text containers by design; not yet tested with a text-spacing override.
1.4.13 Content on Hover or Focus (Level AA)Partially SupportsPartially SupportsNot ApplicableNo hover-only content by design; menus open on click and close with Escape. Not yet reviewed manually.
2.4.5 Multiple Ways (Level AA)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableConsole: navigation menu plus document search. Portal: small set of pages linked from the header and footer.
2.4.6 Headings and Labels (Level AA)Partially SupportsPartially SupportsSupports (automated checks; manual verification pending)Headings and labels are descriptive by design; wording not yet reviewed manually. PDF headings are tagged.
2.4.7 Focus Visible (Level AA)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableA visible focus outline is defined for all interactive elements in both console themes and the portal. Not yet verified manually on every control.
3.1.2 Language of Parts (Level AA)Not ApplicableSupports (automated checks; manual verification pending)Partially SupportsPortal: Spanish content is served with the Spanish page language. PDFs: English and Spanish templates set the document language; bilingual notices with mixed-language passages are not yet verified to tag each passage.
3.2.3 Consistent Navigation (Level AA)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableThe same navigation appears in the same place on every page.
3.2.4 Consistent Identification (Level AA)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableComponents with the same function use the same labels throughout.
3.3.3 Error Suggestion (Level AA)Partially SupportsSupports (automated checks; manual verification pending)Not ApplicablePortal: errors say how to fix the entry (for example “Enter a valid email address.”). Console: not reviewed on every form.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)Partially SupportsNot ApplicableNot ApplicableConsole: batch approval, voiding and marking mailed are explicit actions; not every data-changing action has a confirmation step. Portal: no legal or financial transactions.
4.1.3 Status Messages (Level AA)Supports (automated checks; manual verification pending)Supports (automated checks; manual verification pending)Not ApplicableStatus messages (toasts, form results) use live regions; axe-core checks ARIA usage. Screen-reader announcement not yet verified.

Table 3: Success Criteria, Level AAA

Not evaluated.

Revised Section 508 report

Chapter 3: Functional Performance Criteria

Chapter 3: Functional Performance Criteria
CriteriaConformance level (all three products)Remarks and explanations
302.1 Without VisionPartially SupportsDesigned for screen readers (semantic HTML, tagged PDFs, automated checks), but testing with JAWS, NVDA and VoiceOver has not been completed.
302.2 With Limited VisionPartially SupportsResizable text, contrast checked by axe-core, dark theme in the console. Zoom and magnifier testing not completed.
302.3 Without Perception of ColorPartially SupportsStatus is conveyed with text as well as color by design; see 1.4.1.
302.4 Without HearingNot ApplicableNo audio.
302.5 With Limited HearingNot ApplicableNo audio.
302.6 Without SpeechSupportsNo speech input is required.
302.7 With Limited ManipulationPartially SupportsAll functions are designed for keyboard use; automated keyboard-only tests cover key flows. Single-key console shortcuts can be turned off (see 2.1.4).
302.8 With Limited Reach and StrengthSupportsWeb and document content; no physical controls.
302.9 With Limited Language, Cognitive, and Learning AbilitiesPartially SupportsPlain-language notices and portal text in English and Spanish. Not formally evaluated.

Chapter 4: Hardware

Not applicable. SentraDeed is web software and generated documents.

Chapter 5: Software

Chapter 5: Software
CriteriaConformance level (all three products)Remarks and explanations
501.1 Scope – Incorporation of WCAG 2.1 AASee WCAG 2.1The staff console and resident portal are web applications; see the WCAG 2.1 tables above.
502 Interoperability with Assistive TechnologyNot ApplicableWeb applications running in a browser; the browser provides the platform accessibility services.
503.2 User PreferencesSupports (automated checks; manual verification pending)The console and portal follow browser and system settings for text size, and the console follows the system light or dark preference.
503.3 Alternative User InterfacesNot ApplicableNo alternative user interface is provided.
503.4 User Controls for Captions and Audio DescriptionNot ApplicableNo video.
504.2 Content Creation or Editing (authoring tool)Partially SupportsThe console generates notice PDFs from county templates. Every generated notice is tagged and validated against PDF/UA-1 with veraPDF; the accessibility of a county-supplied Word or PDF template before conversion depends on the template.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionPartially SupportsWord templates are converted to tagged PDF and fillable PDFs are re-tagged; output is validated with veraPDF. Preservation of every tag from arbitrary county templates is not guaranteed.
504.2.2 PDF ExportSupports (automated checks; manual verification pending)Notice PDFs are exported as PDF/UA-1 and validated with veraPDF.
504.3 PromptsPartially SupportsTemplate upload shows the validation result; accessibility guidance for template authors is planned.
504.4 TemplatesSupportsThe default English and Spanish notice templates produce PDF/UA-1 output.

Chapter 6: Support Documentation and Services

Chapter 6: Support Documentation and Services
CriteriaConformance level (all three products)Remarks and explanations
602.2 Accessibility and Compatibility FeaturesPartially SupportsThis report and the security page describe accessibility features; a user guide section is planned.
602.3 Electronic Support DocumentationPartially SupportsDocumentation is provided as web pages designed to WCAG 2.1 AA; not all onboarding documents have been checked.
602.4 Alternate Formats for Non-Electronic Support DocumentationPartially SupportsAlternate formats are available on request.
603.2 Information on Accessibility and Compatibility FeaturesPartially SupportsSupport staff can answer accessibility questions by phone; a documented process is planned.
603.3 Accommodation of Communication NeedsPartially SupportsSupport by phone and email; other channels on request.

This report describes the accessibility of a pre-release build as of the report date, based on the evaluation methods above. It is provided for information and procurement review and is not a warranty. Features and conformance may change as the product develops; the report will be updated after screen-reader testing. To report an accessibility barrier, call 559-251-7767.

VPAT® is a registered service mark of the Information Technology Industry Council (ITI).

See it run on your files

We'll walk your Recorder and Assessor teams through a full cycle on a few days of your own exports: intake, matching, exceptions, a print-ready batch and the resident portal.

Request a demo