Skip to content

Record manual screen-reader and physical-device accessibility checks #4

Closed

Description

@wilkinsantana

Automated browser checks are in place; record the manual coverage needed beyond them.

Acceptance:

  • Test the shared navigation, forms/errors, catalog, native dialog/popover and theme control with a screen reader.
  • Record OS, browser, assistive technology and exact tested revision.
  • Check a physical phone, zoom/reflow, focus return and reduced-motion preferences.
  • Open focused bug issues with minimal reproductions for findings.
  • Describe coverage and limitations without claiming full accessibility conformance.

Coordinate test combinations in this issue to avoid duplicate work. Do not attach personal data.

Activity

  1. moved this to Ready in TendUIon Nov 7, 2026
  2. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Starting the manual-review preparation after the launch update and visual-suite work. I will add a reproducible session checklist covering shared navigation, form recovery, catalog, overlays, themes, zoom/reflow and reduced motion, with explicit Not run/Pass/Fail/Unsupported results and exact website/library revisions. Automated checks will not be represented as screen-reader or physical-device verification. The maintainer has been asked which real device/assistive-technology combination they can exercise; actual observations are still required before this issue can close.

  3. moved this from Ready to In progress in TendUIon Nov 8, 2026
  4. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    The protocol and copyable result record are prepared in draft PR #11 (docs/manual-accessibility.md). The maintainer reports access to iPhone/VoiceOver, Android/TalkBack and a desktop screen reader; those are the planned combinations, not completed results. Shared navigation, catalog search, form error recovery, dialog focus return and theme checks have been sent as the first short session. Device/OS/browser/AT versions and actual observations are still pending.

  5. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Initial maintainer observation, 2026-11-08: “iPhone navigation seems good.” Recorded as an informal navigation result only. Device/iOS/browser versions and whether VoiceOver was enabled are awaiting confirmation; forms, overlays, zoom and reduced-motion checks remain Not run.

    The public /version endpoint sampled during this session reports build 2026.1.0-dev, library v2026.2.0-preview.2 at 5b09328. That endpoint does not identify the website's exact source commit, and this sample does not prove which cached page was on the phone. Keep this limitation with the manual observation.

  6. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer follow-up for the manual session on 2026-11-08:

    • Device: physical iPhone 16.
    • OS: iOS 26.6.2, as reported by the tester.
    • Browser: Safari; separate browser build not supplied.
    • Assistive technology: VoiceOver enabled, as reported.
    • Observation: navigation seemed to work, and VoiceOver announced the names of items the tester tapped. The tester describes this as an informal, non-expert check.

    Record this as a positive basic navigation/control-name observation, not a complete screen-reader audit or proof of every accessible name. Form-error recovery, dialog focus containment/return, popovers, themes, zoom/reflow, reduced motion, and Android/desktop combinations remain unverified. The exact website source revision was not established on the device; retain the earlier version-endpoint sampling limitation. Issue remains open.

  7. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer confirmed the next targeted manual check: on the previously reported iPhone 16 / iOS 26.6.2 / Safari with VoiceOver enabled, Form lab → Test server validation exposed readable form errors and error-summary links reached the correct fields.

    Record form-error announcement and error-link navigation as passing this informal operator check. Successful corrected submission, dialog focus containment/return, popovers, theme, zoom/reflow, reduced motion and Android/desktop coverage remain unverified. This does not establish a complete accessibility audit; the earlier exact-deployment-revision limitation still applies.

  8. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer confirmed both targeted dialog checks on the previously reported iPhone 16 / iOS 26.6.2 / Safari with VoiceOver enabled: Interactions → Review demo request is read by VoiceOver, and closing the dialog returns focus to its opener.

    Record dialog readability and focus return as passing this informal operator check. Modal focus containment was not explicitly tested and remains unverified, as do popovers, corrected form submission, theme, zoom/reflow, reduced motion and Android/desktop coverage. Keep the existing exact-deployment-revision limitation; this is scoped manual evidence, not a complete accessibility audit.

  9. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer confirmed the targeted theme check on the same reported iPhone 16 / iOS 26.6.2 / Safari with VoiceOver enabled: after toggling the header theme and visiting Docs/Components, the selected theme persisted and spoken navigation/content remained usable. They specifically cited VoiceOver reading “37 components found.”

    Record theme persistence across these routes and readable page information as passing this informal operator check. This observation does not establish automatic live-region announcement of changed results. Previously confirmed: basic navigation/control names, form-error reading and error-link navigation, dialog reading and focus return. Popovers, modal focus containment, corrected form submission, zoom/reflow, reduced motion and Android/desktop coverage remain unverified. Existing source-revision limitation still applies.

  10. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer confirmed the targeted popover checks on the same reported iPhone 16 / iOS 26.6.2 / Safari with VoiceOver enabled: on Interactions, both Show project details and Show pinned note exposed content reachable with VoiceOver, and both panels could be closed.

    Record popover content access and dismissal as passing this informal operator check. This does not separately verify focus placement after dismissal. Previously confirmed: basic navigation/control names, form-error reading and error-link navigation, dialog reading and focus return, theme persistence and readable page information. Modal focus containment, corrected form submission, zoom/reflow, reduced motion and Android/desktop coverage remain unverified. Retain the existing exact-source-revision limitation; issue remains open.

  11. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer reports that nothing seems out of place in landscape during the requested Components/Playground check on the previously identified iPhone 16 / iOS 26.6.2 / Safari setup.

    Record a positive informal physical-device landscape layout observation: no visible layout problem reported. Enlarged text was not explicitly confirmed, so larger-text/zoom/reflow remains unverified. Do not interpret this observation as exhaustive containment or accessibility testing. Other previously noted outstanding checks and the exact-source-revision limitation remain unchanged.

  12. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer confirmed the targeted enlarged-text check on Components and Playground using the previously reported iPhone 16 / iOS 26.6.2 / Safari setup: nothing overlapped or clipped, and forms and dropdowns opened normally.

    Record physical-device enlarged-text layout and control usability as passing this informal operator check. The exact enlargement setting/scale was not supplied; this does not establish desktop 200%/400% zoom coverage. Landscape layout was separately reported good. Reduced motion, modal focus containment, corrected form submission and Android/desktop coverage remain unverified. Retain the existing exact-source-revision limitation; issue remains open.

  13. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer confirmed the reduced-motion check on the previously reported iPhone 16 / iOS 26.6.2 / Safari setup: after enabling the iPhone Reduce Motion setting and reloading /motion, decorative animations stopped while content and controls remained usable.

    Current informal iPhone session results are positive for basic VoiceOver navigation/control names, form-error reading and error-link navigation, dialog reading and focus return, popover content access/dismissal, theme persistence/readable content, landscape layout, enlarged-text layout/control usability, and OS reduced motion. Exact text-enlargement scale and deployed website source revision remain unestablished. Modal focus containment and successful corrected form submission were not explicitly verified. Android/TalkBack and desktop screen-reader sessions are still outstanding; this issue remains open and no full conformance claim is made.

  14. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer reports that all requested Android checks worked on a physical Seeker phone running Android 16. This reply follows the requested Android/TalkBack session covering navigation, form errors, dialogs/popovers, and theme switching; record those scoped checks as passing by operator report with TalkBack enabled in the requested setup.

    Browser name/version and TalkBack version were not supplied. No specific spoken-output transcript or exact deployed website revision was established. Do not extend this result to Android enlarged text, landscape, reduced motion, detailed modal focus containment, or other checks not requested in that session. Desktop screen-reader coverage remains outstanding; this is informal manual evidence, not a complete conformance audit.

  15. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Android session metadata follow-up: the maintainer identifies the browser as Chrome mobile, reported as the latest version. Exact Chrome version/build was not captured or independently verified. Associate this with the previously reported physical Seeker / Android 16 TalkBack session and its scoped passing navigation, form-error, dialog/popover and theme checks. No additional checks were performed by this metadata update.

  16. wilkinsantana commented on Nov 8, 2026

    @wilkinsantana
    ContributorAuthor

    Maintainer reports the requested desktop session passed on Linux with Orca in both Firefox and Chrome. Requested coverage: Tab/Shift+Tab/Enter navigation, reading form errors and following error links, opening/closing dialogs and popovers, and checking sensible focus return. Record these as passing by operator report. Linux distribution/version, browser versions and Orca version were not supplied.

    The agreed device sessions now have positive informal results across iPhone/Safari/VoiceOver, Seeker/Android 16/Chrome mobile/TalkBack, and Linux/Firefox plus Chrome/Orca. This is scoped human-reported evidence, not an independent audit or WCAG conformance certification. Exact website source revision, several software version numbers, desktop 200%/400% zoom, detailed modal focus containment and successful corrected form submission remain unestablished. Keep those limitations explicit; no unperformed check is marked passed.

  17. moved this from In progress to Done in TendUIon Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Type

    No type

    Projects

    • Status
      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions