Updating style selectors for theme editor CC

[muskgupta]

Description

This commit aligns Adaptive Form _cq_styleConfig selectors with authored markup and canvas theme expectations: scoped label/help, long-description paragraphs, richer tabs/wizard/list markers, file-input and T&C surfaces, v2 wizard/nav/RTL, removal of duplicate submit/reset/button help entries, optional disabled widget styling, and theme config updates so datetime, scribble, and file upload v4 participate in the form theme editor.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes and the overall coverage did not decrease.
• All unit tests pass on CircleCi.
• I ran all tests locally and they pass.

[adobe-bot]

Accessibility Violations Found

Id	Impact
aria-required-attr	critical
empty-heading	minor
label-title-only	serious
target-size	serious

[adobe-bot]

Accessibility Violations Found

Id	Impact
aria-required-attr	critical
empty-heading	minor
label-title-only	serious
target-size	serious

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[sakshi-arora1]

Spot-checked the new selectors against the actual HTL/CSS — most map cleanly to real DOM (__label-container, data-cmp-enabled, switch hide-labels classes, T&C modal subtree, etc.), and several pre-existing typos (cmp-adaptiveform-X__label-container:disabled missing the leading dot, .adaptiveform-switch__widget-label missing the cmp- prefix) are nicely fixed here. A few concerns inline. High-level: please add a short manual-test note to the description (theme-editor inspector tree for the affected component families + republish check) since this PR has no test changes and is content-only.

[sakshi-arora1]

[disabled="true"] is an attribute-value match, not the standard boolean [disabled]. This will only fire when the markup literally writes disabled="true". Please verify the review HTL emits the value (vs. just disabled) — otherwise this state never matches. Same comment applies to the second htmlDisabled block at line 165.

[muskgupta]

Updated this in latest commit to resolve it as [disabled]

[adobe-bot]

Accessibility Violations Found

Id	Impact
aria-required-attr	critical
empty-heading	minor
label-title-only	serious
target-size	serious

[adobe-bot]

Accessibility Violations Found

Id	Impact
aria-required-attr	critical
empty-heading	minor
label-title-only	serious
target-size	serious

[adobe-bot]

Accessibility Violations Found

Id	Impact
aria-required-attr	critical
empty-heading	minor
label-title-only	serious
target-size	serious

[adobe-bot]

Accessibility Violations Found

Id	Impact
aria-required-attr	critical
empty-heading	minor
label-title-only	serious
target-size	serious