Foundry Academy · Software QA · Lesson 6 of 6

Regression, accessibility, and release signoff

Assemble risk-based regression and accessibility evidence into a transparent release recommendation with defects, gaps, ownership, and rollback readiness.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Regression, accessibility, and release signoff

Objective: Assemble risk-based regression and accessibility evidence into a transparent release recommendation with defects, gaps, ownership, and rollback readiness.

Regression selection should follow change impact, dependency paths, defect history, critical customer journeys, permissions, data integrity, and operational controls. Maintain a small smoke set for rapid confidence and deeper suites for affected risks. Remove or repair flaky tests rather than treating reruns as normal evidence. Accessibility belongs throughout design and testing; combine automated checks with keyboard, zoom, focus, name-role-value, error, contrast, reflow, screen-reader, caption, and content review appropriate to the product. Automated tools find only part of accessibility risk, and conformance claims require qualified evaluation beyond this course.

A release recommendation summarizes build, scope, environments, results, open defects, critical criteria, accessibility findings, security or performance evidence, untested areas, data or migration checks, monitoring, support readiness, rollback, and named risk owners. QA recommends based on evidence; authorized stakeholders accept or reject residual risk. A signoff should never say 'bug-free.' If a critical criterion failed or required evidence is missing, state that clearly and recommend no release unless an authorized exception process applies. Preserve the test package and decision version so incidents can be compared with what was known at release time.

Before you begin

  • Confirm F01, F02, F07-F09, F11, and F12; record that controlled test assets, requirement versions, environment details, accessibility evidence, tax baseline, defect links, execution records, and release authorization are absent.
  • STOP. If controlled assets, versions, environments, accessibility evidence, tax baseline, defect links, or execution records are missing or conflict with F01/F02/F07–F09/F11/F12, route the manifest to authorized release, product, accessibility, payments, and dependency owners; do not claim regression execution, release recommendation approval, or authorization.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This is a fictional, sanitized software-quality case. All systems, users, transactions, and records are fabricated; testing remains authorized and bounded and provides no security, legal, accessibility, or defect-free guarantee.

BlueMesa checkout release

BlueMesa is a fictional business-to-business storefront preparing release 4.8 of its checkout. The approved requirement says authenticated buyers may purchase approved catalog items up to their account credit limit, apply one active contract discount, choose an allowed shipping method, and receive an accessible confirmation. The release candidate is build 4.8.17 in staging. Six browsers and two mobile devices are in scope, but the test plan lists only the latest desktop Chrome. A sample account has a $10,000 credit limit and an existing $9,600 open balance. The cart contains a $700 item, a 10 percent contract discount, $55 shipping, and an 8.25 percent tax rule. The product owner expects the order to be blocked, while the developer says discounts should be considered before the credit check; the requirement does not state calculation order. In preliminary testing, the keyboard focus disappears after the shipping modal closes, the error summary is not announced by the screen reader, and refreshing after payment timeout sometimes creates a second pending order. Logs show the same idempotency key on both requests, but the payment sandbox returns different response identifiers. The tax service was upgraded after the last regression baseline. A defect titled checkout broken includes no build, data, steps, expected result, actual result, or evidence. Marketing already announced Friday availability, and the release manager proposes accepting all medium defects. Learners must define risk and acceptance, control environments, write reproducible tests, explore edge cases within authority, classify defects, and make an evidence-bounded release recommendation. They must not conduct unapproved security testing or claim exhaustive coverage.

Supported example — reference only

Item
Release candidate build
Source or location
Staging build record; exact controlled location not supplied.
Version or date
4.8.17; date not supplied
Owner
QA/release owner
Access or review status
Build identity supplied; access and integrity review pending.
Gap
Commit/hash, deployment timestamp, configuration, and access evidence are not supplied.

A well-handled evidence gap

Item
Accessibility regression evidence
Source or location
Controlled location not supplied.
Version or date
Date/version not supplied
Owner
Accessibility and QA reviewers
Access or review status
Blocked - review record absent.
Gap
F07/F08 observations require approved cases, environment coverage, capture files, and results; none are supplied.

Flawed approach — do not copy

Marking this regression manifest “approved and complete” without the required evidence or reviewer is a flawed submission. Stop release recommendation when a critical manifest item, version, environment, dependency baseline, trace link, or result is missing or stale.

Repair: Rework the regression manifest as an evidence-backed draft, not an approved result. Index build 4.8.17 and every controlled requirement, test, environment, data, dependency, defect, and evidence item needed for regression. Record source/location and version/date only when supplied; otherwise write not supplied. Link the six-browser/two-device scope and accessibility checks to the relevant test assets. Check the revision against this requirement: Build, requirements, cases, environments, data, dependency, defects, accessibility, and results are indexed. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.

Full case record, ambiguities and all assignments →

03 · Bounded practice

Build the regression manifest.

Design focused regression and a conditional release-evidence process; do not run tests or record owner approval.

Deliverable: A regression manifest proposal, traceability matrix starter, accessibility-summary template, and conditional release-evidence brief with results and approval pending.

Complete a bounded starter and gap analysis using only CB01, F01, F02, F07, F08, F09, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M06-I01 · F01 — The release candidate is build 4.8.17 in staging.
  • M06-I02 · F02 — Six browsers and two mobile devices are in scope, while the plan covers one desktop browser.
  • M06-I03 · F07 — Keyboard focus disappears after the shipping modal closes.
  • M06-I04 · F08 — The error summary is not announced by the screen reader.
  • M06-I05 · F09 — Refreshing after payment timeout can create a second pending order.
  • M06-I06 · F11 — The tax service changed after the prior regression baseline.
  • M06-I07 · F12 — The existing checkout-broken defect lacks reproducibility and expected-result evidence.
  • M06-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M06-S01 · F01, F02, F07, F08, F09, F11, F12 — Build a starter version of “A regression manifest proposal, traceability matrix starter, accessibility-summary template, and conditional release-evidence brief with results and approval pending.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. Index build 4.8.17 and every controlled requirement, test, environment, data, dependency, defect, and evidence item needed for regression.
  2. Record source/location and version/date only when supplied; otherwise write not supplied.
  3. Link the six-browser/two-device scope and accessibility checks to the relevant test assets.
  4. Treat the tax-service change as a baseline invalidation requiring an approved new reference.
  5. Include duplicate-order and incomplete-defect remediation artifacts without claiming closure.
  6. Assign access/review owners and identify stale, missing, or blocked items.
  7. Final-QC item uniqueness, version integrity, traceability, access status, gaps, and no release claim.
Field-by-field guidance
Item
Use only a supplied value or a clearly labeled learner proposal; expose missing evidence. Module use: Use the manifest as the controlled index behind a conditional release recommendation, not as evidence that regression passed.
Source or location
Name the controlled source or mark its location not supplied. Module use: Use the manifest as the controlled index behind a conditional release recommendation, not as evidence that regression passed.
Version or date
Use supplied version/date only; otherwise mark not supplied. Module use: Use the manifest as the controlled index behind a conditional release recommendation, not as evidence that regression passed.
Owner
Name the authorized operating or specialist role. Module use: Use the manifest as the controlled index behind a conditional release recommendation, not as evidence that regression passed.
Access or review status
State whether review/access evidence is supplied, pending, or blocked. Module use: Use the manifest as the controlled index behind a conditional release recommendation, not as evidence that regression passed.
Gap
Name the missing artifact, result, version, or approval. Module use: Use the manifest as the controlled index behind a conditional release recommendation, not as evidence that regression passed.
Regression manifest · learning draft
ItemSource or locationVersion or dateOwnerAccess or review statusGap

Start with 6 rows; the complete workbook specifies 22 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 6 · 2-item formative check

Regression, accessibility, and release signoff

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 6 · knowledgeWhich release statement remains within the evidence finite testing can support?
Question 2 of 2 · MODULE 6 · scenarioBlueMesa confirms build 4.8.17 in F01, incomplete environment coverage in F02, accessibility barriers in F07 and F08, duplicate-order risk in F09, a changed tax service in F11, and an incomplete defect in F12. Which release record is defensible?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • Build, requirements, cases, environments, data, dependency, defects, accessibility, and results are indexed.
  • F01/F07/F08/F09/F11 drive explicit entries.
  • The recommendation remains conditional and no regression result is invented.

Stop: Stop release recommendation when a critical manifest item, version, environment, dependency baseline, trace link, or result is missing or stale.

Go: Proceed to review when every required item is indexed, accessible to the authorized reviewer, and version-controlled.

Escalate: Escalate missing critical evidence and baseline drift to release, product, accessibility, payments, and dependency owners.

04 · Evidence to keep

Leave with usable work.

Submit the regression rationale, accessibility record, defect summary, coverage gaps, release recommendation, approvals, monitoring, and rollback checklist.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Software developer reviewing code and test evidence on a tablet.
Learn the standard. Practice the work.
Developer testing and reviewing software code in a modern office.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

w3c-wcag-22 · Standards-body recommendation

Web Content Accessibility Guidelines (WCAG) 2.2

The W3C Recommendation defining testable success criteria for more accessible web content.

Open reviewed external source ↗

nist-sp-800-218 · Official guidance

NIST SP 800-218 Secure Software Development Framework Version 1.1

Primary NIST guidance for integrating secure software practices across the development lifecycle.

Open reviewed external source ↗

ws-software-qa-operating-standard · Academy internal operating standard

Wealth Synergy software-QA internal operating standard

Academy-selected risk, test-case, defect, evidence, regression, and release-review controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.