Privacy-Preserving Accessibility Support

From IDESG Wiki
Jump to navigation Jump to search

Title: Privacy-Preserving Accessibility Support


Use Case Description: A student with specific accessibility needs and preferences (e.g., visual and motor accommodation requirements) can avail themselves of an online e-text associated with her course in a way that allows her to see and understand the graphics even though she is color-blind and check the boxes on the end-of-chapter quizzes even though she lacks the fine motor control that would allow her to use the mouse to move and click. She does this without fear that information about her needs and preferences will be leaked to unrelated parties (for example, potential health insurance providers or prospective employers).

Background: By and large, purveyors of online services and resources have fallen short in accommodating the accessibility requirements of many of the people they want to serve. The problem is challenging but its urgency is undeniable. One of the core challenges is providing users the ability to express personal accessibility needs and preferences and to control the release of subsets of that information in a privacy-preserving way to enable online services to tailor their presentation and user interfaces accordingly.

[Use an action verb name to describe the use case, not including the primary actor name, but identifying any subject actors. Verb modifiers may be used to refine the use case. Examples:  authenticate to system with trusted identity, authenticate to system with pseudonymous identity, match names between systems, verify attributes with privacy protection]


Use Case Category:


Contributor: Keith Hazelton


Use Case Details

Actors:

  • Student
  • Identity Provider (by which student authenticates)
  • Attribute Provider (from which the accessibility needs and preference information is available under user control and consent)
  • Authorization Server (the functional element that enforces the user's wishes with respect to conditions under which the information is released and to which parties it is released)
  • Relying Party (e-text vendor site)


Goals:


Assumptions:


Requirements:


Process Flow:


Success Scenario:


Error Conditions:


Relationships

  • Extended by:
  • Extension of:

References and Citations