Adjustment for the deaf-blind community
There are a number of our requirements written in such as way as to assume that a blind person can hear, or that a deaf person can see. Where possible we should try to write these in a way that doesn't exclude the needs of the deaf-blind community. While adding a braille display to a "closed functionality" public kiosk or other device is not really feasible, I think we need to be very conscious not to carry false assumptions across in other places where we can do better. For example, an indication that something has changed on screen could be communicated to a deaf-blind person by vibration rather than an audio indication. Clearly, forcing a manufacturer to install an audio capability or a lamp in a device intended for a deaf-blind user is an unreasonable demand.
I propose we use this Issue to keep track of those requirements we spot that might benefit from some rewording in this respect. This is a list for consideration rather than definitive for action. Feel free to add more.
I'll start the list with:
5.1.3.1
6.2.2.1 (RTT is important for the deaf-blind)
6.2.2.4
6.5.5