Repository navigation
feat(site): explain each operation in plain words - #31
Merged
Merged
Conversation
The page said what Covering array and Strength were called but not what they meant. Each operation (count, list and its limit, dead values, covering array and its strength, one combination by index, and explain) now has a short paragraph under its heading or beside its field, and the controls name it in aria-describedby, so it shows on screen and a screen reader reads it when the control is focused. No tooltip is involved. The texts live in one module, filled into placeholders in index.html when the page starts. A test reads index.html itself and checks that every control of an operation names a description that exists and has text, that every description has a paragraph, and that the covering array and strength wording says what it was asked to.
Mearman
marked this pull request as ready for review
October 29, 2026 18:03
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
|
🎉 This PR is included in version 2.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The page named Covering array and Strength without saying what they are. Each operation now has a short paragraph under its heading, and the fields that need one (the list limit, Strength) have another beside them: count, list, dead values, covering array, one combination by index, and explain. The controls name them in
aria-describedby, so a screen reader reads each on focus; they are plain paragraphs, not tooltips, so they show on a phone and in both colour schemes.Covering array reads as a short list of valid combinations that tests every interaction you care about without listing them all, checked and reported. Strength is how many options at a time must be covered together: 1 every single value, 2 (pairwise, the default) every pair of values from any two dimensions, 3 every triple, with combinations the rules make impossible not required.
The texts are in
site/src/help.tsand filled into placeholders inindex.htmlat start. A jsdom test loadsindex.htmlitself and checks that every control of an operation names a description that exists and has text, that every description has a paragraph, that the wording covers what was asked, and that none contains a dash or a spaced double hyphen. I broke each of those in turn and the test failed. In headless Chromium I checked the text is visible, that Chromium's accessibility tree reports each paragraph as the control's description, that no horizontal scroll appears at 375px, that the text has at least 4.5:1 contrast against its panel in light and dark, and that a covering array still builds.