GRIDEX INC. / ACCESSIBILITY SAMPLES

Demonstration sample by Gridex Inc. — synthetic data; not a State of Minnesota system

Accessibility remediation log

Prepared by Gridex Inc. on October 4, 2026. All records and identities are synthetic. No State or production tenant is connected.

Issues and remediation
Issue observedChangeVerification
Reverse Tab from the first draft-dialog button reached an empty browser focus target.Added explicit first/last-button Tab wrapping inside the native modal dialog. Escape remains available.Keyboard tests verify Tab, Shift+Tab, Escape and return focus. axe scans cover save and cancel dialog states.
A queued dialog close listener could move focus back to Restore after the user had advanced the form.Removed the asynchronous focus override; rely on native close restoration and explicit heading focus after restore/reset.Save, reload, restore, advance and cancellation journeys pass.
macOS headless Chromium did not operate native select/date widget default actions through synthetic keyboard events.Use a labeled plain-text fictional agency field and consistent typed YYYY-MM-DD date inputs. Validate actual calendar dates and ordering; no custom calendar widget.Complete keyboard-only journey passes, including invalid email, impossible February date, chronology error and corrected submission.
The current workflow video documents a DAC consultation prerequisite.Added a required consultation checkbox while retaining the ability to save an incomplete draft.Empty-step error summary includes consultation; draft save works before full validation.
Word's default Title style rendered a blue border.Removed paragraph borders from styles and document paragraphs.Re-rendered and inspected all pages; title remains a real Word Title style.
Chromium tagged-PDF output lacked document language, display-title preference and PDF/UA identification metadata.Added en-US, title/author metadata and PDF/UA-1 identification; preserved tagged content.veraPDF PDF/UA-1 automatic profile and structural audit pass.
Chromium drew untagged non-text page elements and used unmapped Strong tags.Marked untagged drawing/state operators as artifacts, asserted no untagged text is discarded, and mapped Strong to Span for PDF 1.7.veraPDF has zero failed rules/checks; rendered output and extracted text verified.
Approval list LI elements contained body children directly.Wrapped body content in LBody while retaining labels and updating parent references.veraPDF list checks pass; four approvals retain correct order and text.
Printed definition labels could separate from their content at a page break.Added keep-with-next print behavior for definition terms.Final PDF pages rendered and inspected.
The original guide illustration repeated text without showing the configuration relationship clearly.Added three source-list nodes feeding a workflow configuration node; supplied the equivalent relationship in alternative text and surrounding prose.Word image description, PDF Figure Alt, HTML alt and contrast inspected.

Remaining verification limitations

Required follow-up test

An accessibility reviewer should use VoiceOver with Safari (or NVDA with a supported browser) to complete the form, inspect linked errors, hear draft status announcements, operate both draft dialogs, and verify review/submission focus. Read each PDF and the Word guide by heading, table and list navigation; confirm the illustration alternative. Record exact spoken outcomes before updating the ACRs. These checks are implementation-independent and do not require a State tenant.

October 4 additional programmatic and virtual reading evaluation