Skip to content

Add keyboard and screen-reader checks for the core setup path #179

Description

@Maneek21

The production browser smoke proves core behavior, but it does not yet certify keyboard or screen-reader basics.

Acceptance criteria:

  • cover login, primary navigation, task creation, approval, and MCP setup
  • verify visible focus and semantic labels
  • add automated checks where stable
  • document any intentionally deferred findings

Metadata

Metadata

Assignees

No one assigned

    Labels

    accessibilityAccessibility and inclusive UXhelp wantedExtra attention is needed

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions