Skip to content

test: cover accessible component markup - #7

Merged
phcodesage merged 1 commit into
phcodesage:mainfrom
mgalore:test/issue-5-accessible-components
Sep 11, 2026
Merged

phcodesage merged 1 commit into
phcodesage:mainfrom
mgalore:test/issue-5-accessible-components

Conversation

@mgalore

@mgalore mgalore commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

What changed?

Adds focused server-rendered accessibility assertions for the existing component macros: native button type and disabled state; labelled inputs and textareas with error descriptions; alert semantics; avatar alternative text; spinner status labels; and dialog labelling plus its keyboard-reachable close control.

Closes #5.

Checklist

  • I ran make test.
  • I ran make lint.
  • I ran npm run build:css when changing templates or Tailwind styles.
  • I added or updated tests where appropriate.
  • I updated documentation for public API changes.
  • I did not include secrets or generated files.

Screenshots

Not applicable: this change adds rendering assertions only and does not alter component markup.

@phcodesage phcodesage left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed. This is a focused test-only change with no runtime or dependency impact. The assertions match the current component output and CI passes across Python 3.9–3.13, Tailwind, and GitGuardian. Approved.

@phcodesage
phcodesage merged commit f9edd95 into phcodesage:main Sep 11, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add accessibility assertions for rendered component markup

2 participants