Skip to content

[css-forms-1] WCAG conformance design principle #12480

@lukewarlow

Description

@lukewarlow

This issue is to discuss potential clarifications to the "The controls pass 100% of WCAG 2.2 AA standards." design principle of CSS Forms base appearance mode.

This is strongly worded and while a principle rather than a claim I think it could be good to clarify the scope of what is and isn't included in that. For example, the title attribute tooltip that shows up has a number of WCAG issues (that it avoids by virtue of the fact its browser provided).

Pickers are also largely not included in the spec but the statement might give a false sense that this sovles all those issues.

Potentially we should simply say something more generic that the controls should try to account for accessibility requirements where possible.

Raising as its something that's come up on socials (e.g. https://toot.cafe/@aardrian/114851791346613604).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions