Alpha4 validation checklist: Joomla integration, updates and accessibility

[joomtheme]

Goal

Track validation of Rahisi 0.1.0-alpha4 on Joomla 6.1.3 before progressing toward a stable release. Use a backed-up staging site; this checklist is not a WCAG certification or a JED listing approval.

Confirmed so far

• Local static suite: 298 checks passed.
• Local JavaScript preference logic suite: 94 assertions passed (Node VM with DOM/storage doubles, not a real browser).
• Maintainer reported Alpha4 passing JED Checker.
• Maintainer reported a successful Alpha4 template update on Joomla 6.1.3.
• Earlier maintainer testing confirmed text scaling, article spacing/contrast, reset and persistence across navigation/reload. Recheck on Alpha4 below.
• GitHub release is marked as a pre-release.
• Published update.xml and changelog.xml were retrieved successfully.
• GitHub installer asset SHA-256 matches the local package and update feed: 7f8c91bce043a2220728ffe49b748b02c75ce48bce058a581db8ae4725b867c9.

Joomla installation and lifecycle

• Record exact Joomla, PHP, database, browser and operating-system versions.
• Run PHP syntax lint on all shipped PHP files with a compatible PHP version.
• Test a fresh Alpha4 installation and manual template/plugin/module activation.
• Verify upgrades preserve configuration and saved reading preferences.
• Check Joomla/PHP logs and browser console for warnings/errors.
• On a disposable test site, test package uninstall and verify unrelated content/extensions remain intact.

Template and module regression checks

• Recheck 100–200% scaling, article spacing and contrast on Alpha4 with actual article content.
• Verify persistence across navigation/reload and reset to current template defaults.
• Test logo, alternative text, custom site title and Joomla site-name fallback.
• Test default scale, line height, article width and all three palettes.
• Test module initial expansion, help text and all control-visibility combinations.
• Confirm hiding a control does not erase its stored preference; reset still clears all preferences.
• Test multiple module instances and pages without the preferences module.
• Verify English/Turkish labels, help text and the back-to-top accessible name; no raw language keys.
• Check mobile layouts and at least two browser engines.

Joomla update channel

• Enable the Rahisi update site and verify Joomla retrieves the feed without errors.
• On an older test installation with alpha updates permitted, verify Alpha4 is offered.
• Complete the update through Joomla and verify package version, preferences and functionality.
• Confirm an existing Alpha4 installation is not offered Alpha4 as a newer version.

Accessibility checks

• Navigate the module, menu and back-to-top control using only the keyboard; verify visible focus and no keyboard traps.
• Test accessible names, expanded/checked states and help text with NVDA or VoiceOver.
• Check 200%/400% browser zoom and narrow-screen reflow for clipping or overlapping controls.
• Measure contrast for text, controls and focus indicators across palettes and preference states.
• Check text-spacing overrides, long translations and touch target usability.
• Check usable content when JavaScript or browser storage is unavailable.
• Run an automated accessibility scan and manually review its findings; do not treat a clean scan as proof of conformance.

Release housekeeping

• Optionally attach the separate developer source ZIP mentioned in the release description.
• Resolve/document source provenance: the existing Alpha4 tag points to the initial README/LICENSE commit, while implementation sources are on main. Do not silently retag the published release; future tags must point to tested source commits.

Recording results

For each test, comment with the environment, steps, expected/actual result, and screenshots or logs where useful. Do not include credentials or private site data. Mark checks complete only with supporting results; link separate bug issues for failures. Before closing, ensure every remaining item is completed or explicitly deferred with a reason.

References

• Alpha4 release
• Integration testing guide (TR)
• Alpha4 guide (TR)
• Publication status

The packaged docs record build-time status; the current README and this checklist distinguish subsequent maintainer reports from locally executed checks.