Skip to content

readonly/disabled and form-associated custom elements #257

Description

@annevk

I wonder if when these are used on custom elements the accessibility state that exists for them ought to apply. E.g., https://w3c.github.io/html-aam/#att-readonly.

Related to whatwg/html#5016 (comment).

cc @tkent-google @domenic @johndai1984 @zcorpan @muan

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions