Conventional pattern used
Normative Text
[Title, role, or organization] asserts that:
- A review has been conducted and changes made (when necessary) to ensure that Components follow established conventions:
- Each component follows applicable platform conventions for how users interact with that type of component.
- If a component library is used, then each component in the library:
- is tested for accessibility before being used
- follows applicable platform conventions for how users interact with that type of component
Information that needs to be included publicly:
- Title, role or organization making the assertion (if different from the conformance claim).
- Date of when the review was completed.
- Date of assertion (if different from the date of the conformance claim).
Recommended internal documentation (Informative):
- Results from the review.
- Process or policy for maintaining the review.
A component library specifies a set of standardized components used in a product or products. It can include code to use, but at a minimum would define how the component is used and define pointer, keyboard, and assistive technology interactions.
Using a component library can help larger teams and organizations provide a consistent experience.
Examples of component libraries include GDS, Carbon Design System, and Lion.
Examples of platform patterns are ARIA Platform Authoring Guide (web), Apple human interface guidelines, and Android Material Design.
Tests
This content needs to be written.
Key Terms
- component
grouping of elements for a distinct function