Use case review: Accessibility and Personalization about dpub-pwp-ucr HOT 4 CLOSED

IndieUI will re-launch in WAI soon (timeline TBD). It will be very helpful to have use cases to turn over to them when they start, but this is not our first priority.

from dpub-pwp-ucr.

The accessibility TF did not do a great job of resolving the relationship is between these use cases to the note that we have been creating; putting this on the agenda for our next meeting. (cc: @clapierre)

I will say that for our purposes we did not only focus on ideas that were unique to PWP (I'd argue that nothing is unique to PWP except the spec for PWP), but on any idea which is an unsolved problem & which is extremely important to the industry. E.g. dealing with accessibility of timed tests is flat-out vital to digital publishing, regardless of who else it may be important for as well. I would argue that timed test accessibility is much less generic than the personalization points, which will likely apply to any web resource.

from dpub-pwp-ucr.

To be more precise, these use cases have been not reviewed at all by the accessibility TF. We should discuss on the TF:

1. 1. The difference between the purposes of the use cases and the purpose of the note.
2. How much of the use cases should be incorporated into the note's future work.
3. Whether we are going to do a full editorial review of the accessibility use cases as part of the TF once we have a better understanding of their purpose.

cc @clapierre

from dpub-pwp-ucr.

Agreed this is something we will discuss in the DPUB A11Y TF and figure out what we may need to add to our Note regarding use cases for Accessibility & Personalization. I have added this to our agenda this week.

from dpub-pwp-ucr.