task: #3625607 Update @vardot/varbase-e2e to 2.0.7 and widen the accessibility coverage

Rajab Natshahrequested to merge
issue/varbase_starter-3625607:3625607-varbase-e2e-2-0-7 into 1.0.x

Issue: https://www.drupal.org/i/3625607

Changes

  • Bumps to @vardot/varbase-e2e ^2.0.7, whose impact gate is now cumulative (no serious also fails on critical), with a one-step full check, an element-level rule check, and structural probes that skip anything assistive technology cannot reach. Release notes
  • Widens 15-02 from 10 scenarios on mostly the homepage to 34 across every public page: one gate per page, with the rules that matter pinned by id.
  • Adds 15-04-accessibility-structure.feature (15 scenarios): title, language, one h1, heading order, landmarks, skip link, zoom, control names, ARIA references and roles, and positive tabindex.

Testing

49 of 49 scenarios pass on a fresh Drupal CMS install of the recipe, though CI installs on a Varbase base rather than Drupal CMS, so the two paths can differ.

Remaining tasks

  • Raise About Varbase, Features, Blog and Contact Us from a level A audit to no serious accessibility violations once the colour contrast of .btn-outline-primary text on a bg-secondary-subtle card is resolved. Measured about 3.6:1 against the 4.5:1 AA threshold, 2 to 3 nodes per page. Owned by vartheme_bs5 and the recipe content, not by this change.
  • Turn I print the full accessibility check into the asserting the page should pass the full accessibility check once the site-wide search block has an accessible label. views.view.search exposes its keyword filter with label: '' and only placeholder: 'Search by keyword', which ships from the drupal_cms_search recipe and so affects both the Drupal CMS and the Varbase bases. The full check always runs the structural probes, so no audit level avoids it.
  • Restore the form-field label probe on Contact Us and Blog once that same search label is fixed. It is currently pinned to /user/login only.

AI-Generated: Yes

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release
Edited by Rajab Natshah

Merge request reports