Phase Two Assumptions and Scope

Assumptions

• The version of Material UI used will not be taken from the next branch
• Changes made will not be accepted by the Call ‘em All project team
• Rework may be necessary if additional libraries are added
• Rework may be necessary to provide compatibility with old
• Screen readers will be provided that match the capabilities of the client
• Web AIM evaluations standards will be used
• CSS changes are out of scope
• API changes using required parameters cannot be made
• API changes must be resilient enough to be able to cope with missing values
• Priority will be placed on components for user interaction, such as text boxes and buttons

Due to the composite nature of the components, it may be possible to update multiple issues with changes an underlying base feature.