-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test of accessible login creation interface #25
Labels
trigger retest
This modification will trigger retesting flags
Comments
Agree that the first tests should be modified to include accessibility of the log in interface etc.
Similarly, in the third test we can add comments about testing the accessibility of book download process in case of browser based apps. Many apps do not allow side loading of files. We have been getting our file inside the app with the help of developers etc. Actually the objective of this test is to check if users can search, select and download files from the reading system if it has or is connected to online libraries. This should be clarified in the third test.
[REQUIRED]file-310
Open content: Open the test book in the Reading System.
Indicate Pass or Fail.
From: Avneesh Singh [mailto:[email protected]]
Sent: 30 June 2018 07:49
To: daisy/epub-accessibility-tests <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [daisy/epub-accessibility-tests] Test of accessible login creation interface (#25)
The first two tests in basic test sections state the following:
Basic Functionality Tests
[REQUIRED]file-010
The device can be started independently and essential accessibility for starting and exiting applications is available.
→Indicate Pass or Fail.
1
[REQUIRED]file-110
The reading system can be activated independently.
→Indicate Pass or Fail.
If we look from an app perspective, both of the tests are asking the same question.
One way can be to update the first test to evaluate the accessibility of login interface of reading apps.
for example:
Basic Functionality Tests
[REQUIRED]file-010
If you are using a hardware device, it can be started independently and essential accessibility for starting and exiting applications is available.
If you are using reading app that requires you to create an online account for getting started then the complete getting started process should be accessible.
→Indicate Pass or Fail.
1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#25> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHF2u8ezYvB3mkJYs8ivHTy8Q2KkLGvlks5uBuAUgaJpZM4U9zix> . <https://github.com/notifications/beacon/AHF2u_ai7RkP7cAdrVEOIohhEITIrL3dks5uBuAUgaJpZM4U9zix.gif>
|
Created new issue for this: #26.
|
marisademeglio
added
the
trigger retest
This modification will trigger retesting flags
label
Jul 2, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The first two tests in basic test sections state the following:
Basic Functionality Tests
[REQUIRED]file-010
The device can be started independently and essential accessibility for starting and exiting applications is available.
→Indicate Pass or Fail.
1
[REQUIRED]file-110
The reading system can be activated independently.
→Indicate Pass or Fail.
If we look from an app perspective, both of the tests are asking the same question.
One way can be to update the first test to evaluate the accessibility of login interface of reading apps.
for example:
Basic Functionality Tests
[REQUIRED]file-010
If you are using a hardware device, it can be started independently and essential accessibility for starting and exiting applications is available.
If you are using reading app that requires you to create an online account for getting started then the complete getting started process should be accessible.
→Indicate Pass or Fail.
1
The text was updated successfully, but these errors were encountered: