Skip to content

Accessibility (A11y) #2

@evanplaice

Description

@evanplaice

Accessibility (A11y)

Description

A11y is a significant and important issue worth addressing. I feel like a shift back to semantic HTML should make the transition easier but how should WC be designed so that their functionality is visible to non-visual consumers?

Is the semantic metadata (ex img.alt) encapsulated within a WC accessible outside of the WC, does adding a ShadowRoot have an impact on this?

Does the WC itself need an attribute to mark it's function/contents? How can this be implemented?

What's the best approach for testing/verifying that a WC is A11y-friendly?

Notes (optional)

References (optional)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions