Prioritizing accessibility of different functions
Posted: Tue Oct 23, 2018 7:15 am
Hi,
Now that everyone has assessed OverDrive in a systematic way, which criteria would you say are imperative for any library application to be usable with a screen reader? For example, if annotation functions are not accessible but it is possible to start reading independently and to navigate a book within a particular application, it may still be usable, even if far from perfect. So in this example, annotation features may be nice-to-have, but not crucial.
We are aiming to provide vendors not only with a list of the issues we find, but also prioritize them in the final reports for them.
Thanks in advance for any and all feedback!
Now that everyone has assessed OverDrive in a systematic way, which criteria would you say are imperative for any library application to be usable with a screen reader? For example, if annotation functions are not accessible but it is possible to start reading independently and to navigate a book within a particular application, it may still be usable, even if far from perfect. So in this example, annotation features may be nice-to-have, but not crucial.
We are aiming to provide vendors not only with a list of the issues we find, but also prioritize them in the final reports for them.
Thanks in advance for any and all feedback!