The main purpose for accessibility standards is to ensure that patients can use the technology they need to use to interact with the online world.
This can be as simple as choosing what mobile phone to use but can also be much more complex with integrations or bespoke interface for their needs.
When a patient is asked to enter a date on a SmartForm, they are presented with the built-in default date picker for the device, browser, integration or bespoke interface that they are using.
This means the patient then has a consistent experience, based on their choice for interacting with the online world.
This also then ensures that if a device, browser, integration or bespoke interface is updated the Date Picker will continue to work. There are infinite possibilities for the number of devices, browsers, integrations, bespoke interfaces (or combination of) as well as constant development of new ones. We would not get an explicit communication about these developments or updates and could mean that a custom Data Picker would stop working altogether whilst we try and work out how and where it has gone wrong. This is more of an issue than just a patient not understanding how their device works.
Because of the infinite combinations and new developments possible, we would not be able to provide that many instructions nor keep up with the changes and updates.
Whilst it is frustrating, helping the patient to learn how to use the device of their choice will be best for the patient. You are unlikely to have to help the more bespoke or individual choices as the patient will know how these work.
You could say that it would be a bit like choosing a car only to find out the indicator lever is on the other side of the steering column. Would you complain to the manufacture or would you learn how to use it?