Based on the requirements analysis we have drawn the following design implications for an accessible tracking blocker:
- Control of blocked trackers: users should be able to decide, if a tracker is blocked or not, because some services are used although privacy concerns exist.
- Personalization of warnings and information: e.g. acoustic warnings are important for blind users but considered as annoying by some visually impaired users.
- Acoustic warnings are important for blind users: like the pattern used by the JAWS screen reader a short, concise tune shall be played, which informs the users that trackers are found or respectively blocked.
- Visual feedback is important for visually impaired: visual feedback should not be to intrusive and sufficient contrast is an important factor. Participants explicitly mentioned that feedback should be provided on multiple channels.
- Warnings should be used sparingly but additional information can be accessed easily: the user’s workflow should not be interrupted too often by warnings. But if further information is wanted, additional information should be provided by a keyboard shortcut.
