1. Overview
2. User Stories
3. Functionality
4. Test Scenarios
5. Accessibility
6. Assumptions and Limitations
7. References

Team Name: CodeX

Developer Name: Dimitar Dimitrov

Designer Name:

• Peer Developer Name | Date:
• Design Manager Name | Date:

• Radoslav Mirchev | Date:
• Radoslav Karaivanov | Date:

The <igc-form> collects data from Ignite UI Webcomponents form controls and native form controls.

Collect data from Ignite UI Webcomponents form controls and native form controls into a single FormData object. Data is collected for the following components:

• 'input', 'radio', 'igc-radio', 'select', 'switch', 'igc-switch', 'textarea'

1. The form component should have customizable content.
2. The form component should provide a way to disable validation of child components.
3. The form component should emit an event when it is submitted from any of the following components: 'button', 'igc-button' or 'input'

Developer stories:

• Story 1: As a developer, I want to be able to collect data from supported controls into a single FormData object.
• Story 2: As a developer, I want to be able to place content between the opening and closing brackets of the form component
• Story 3: As a developer, I want to be able to disable the validation for the components, placed between the opening and closing brackets of the form component

End-user stories:

• Story 1: As an end-user, I want to be able to submit data.

3.1. End-User Experience

3.2. Developer Experience

<igc-form novalidate>
    <label for="fname">First name:</label><br>
    <input type="text" id="fname" name="fname">
    <igc-button type="submit">Submit</igc-button>
</igc-form>

3.3. Globalization/Localization

3.4. Keyboard Navigation

3.5. API

Properties

Automation

• Scenario 1: ...

ARIA Support

• <igc-form> should have role="form" if the form has an accessible name

RTL Support