Uploaded image for project: 'Moodle QA'
  1. Moodle QA
  2. MDLQA-1 Moodle QA testing
  3. MDLQA-16038

An admin can activate the Accessibility toolkit plugin and request analysis

XMLWordPrintable

      If using the QA site, please begin just after the hourly reset to give yourself plenty of time to complete the test!

      Prerequisites

      • This test requires a publicly available site with admin access, the QA site can be used for this test.
      • An account needs to be created on the Brickfield Portal in order to obtain an API and secret key to activate the Accessibility toolkit plugin.
        • Please note: Feel free to request Moodle HQ Brickfield testing credentials.
      •  A course containing some content with accessibility issues to submit for analysis, if using the QA site the Activity examples course is a good course to be used for testing.
      • If you are running this test on your own test site, to speed up processing task run rates, the following scheduled tasks may be changed to run every minute rather than the default 5 minutes:
        • Process bulk caching
        • Process bulk batch accessibility checking
        • Task to check for any invalid checkids
        • Process content analysis requests
        • Update site summarydata 
      • If you want to speed up the testing run Brickfield scheduled tasks manually by visiting Site administration > Server > Scheduled tasks and click "Run now".  

      Brickfield settings and registration

      1. As admin and go to Site administration > Plugins > Admin tools > Accessibility > Brickfield registration.
      2. Verify that a notification is displayed stating 'The plugin is inactive and cannot be used.'
      3. Verify that there is a link to 'register your details' on the external Brickfield Portal site.
      4. Verify that all other accessibility plugin pages redirect you back to the registration page as they are currently inactive.
      5. Log in to the Brickfield Portal and obtain an API and secret key for your Moodle site.
      6. Return to Site administration > Plugins > Admin tools > Accessibility > Brickfield registration and enter the API and secret key, then click on "Activate" to complete your registration.
      7. Verify that a notification is now displayed stating 'Your accessibility toolkit is still being validated'.
      8. Wait for the Accessibility toolkit scheduled tasks to run then verify that a notification is displayed stating 'The plugin is activated and ready to use.'
      9. Verify that you can now go to the other Accessibility toolkit pages.

      If cron is running normally, and 'Your accessibility toolkit is still being validated' is still showing after these steps, check the registration page again, at Site administration > Plugins > Admin tools > Accessibility > Brickfield registration to ensure the keys have not been rejected as invalid.

      Accessibility toolkit analysis requests

      1. Still logged as an administrator and go to Site Administration > Plugins > Admin Tools > Accessibility > Accessibility toolkit settings.
      2. Uncheck 'Enable analysis requests' setting and save changes.
      3. Go to any course and click 'Accessibility toolkit' in the menu.
      4. Verify that the page states 'Content analysis is disabled'.
      5. Return to the Settings page, check 'Enable analysis requests' and save changes.
      6. Go to any course and verify that the Accessibility toolkit page now has a 'Submit for analysis' button. 

      Teacher can request an accessibility analysis for a course

      1. As teacher, go to a course and click 'Accessibility toolkit' in the administration menu.
      2. Click on the "Submit for analysis" button and verify you are redirected back to your course
      3. Visit the "Accessibility toolkit" page again and verify that a message is displayed stating "This course has been scheduled for analysis."
      4. Take a break and wait for the analysis to be completed. The analysis will be processed in the background by scheduled tasks, so its speed of completion will depend on task timings and task run schedules.
      5. Click "Accessibility toolkit" again and verify that the accessibility analysis for the course is now displayed.
      6. Verify that a list of errors is displayed, each with a related "Edit" link, which will directly send you to edit the content where it's located.
      7. Check for at least 3 different errors that the "Edit" link sends you to the correct location in the course content that requires resolving.
      8. Click on the "Activity breakdown" tab.
      9. Verify that a bar chart is displayed showing the pass ratio for each activity type in the course and text with a heading "Activity breakdown explained" is also displayed.
      10. Click on the "Content types" tab.
      11. Verify that a donut chart is displayed showing the total errors per content type in the course and text with a heading "Content types explained" is also displayed.
      12. Click on the "Summary report" tab.
      13. Verify that the following tables are displayed: Top errors, Failed activities, Check errors, Activity pass ratio, Error details.
      14. Click the "Download PDF" link and verify that the downloaded PDF shows the summary report.
      15. Click on the Advanced tab.
      16. Verify that information regarding features in the commercial versions of the Brickfield Accessibility Toolkit is displayed.

      Teacher can view updated accessibility results for a course

      1. Go to the Content types tab and make a note of the current number of errors for each content type.
      2. Return to the course page and update or create a new activity or resource.
      3. Add a few accessibility errors, such as a link with text "Click here", a link which opens in a new window, use b tags rather than strong, use image alt text which is the image filename etc. then save changes.
      4. Wait a short while then click "Accessibility toolkit" again.
      5. Verify that the new errors are listed correctly. If not, please wait a little longer then refresh the page.
      6. Go to the Content types tab and verify that the number of errors for the different content types has increased as expected.
      7. Return to the error list and select at least two of the new errors to edit and fix.
      8. Wait a short while then click "Accessibility toolkit" again.
      9. Verify that the fixed errors are no longer listed. If not, please wait a little longer then refresh the page.
      10. Go to the Content types tab and verify that the number of errors for the different content types has decreased as expected.

      A teacher can add the "Accessibility review" block and schedule analysis

      1. As teacher, go to a different course and turn "editing mode" on.
      2. Add the "Accessibility Review" block to the course click on the "Submit for analysis" button, then wait for the analysis to be completed.
        • The analysis is processed in the background by scheduled tasks, so its speed of completion will depend on task timings and task run schedules.
      3. Once the analysis is completed, in the "Accessibility Review" block, verify that you can view the different error counts for the different content types, which are: Image, Layout, Link, Media, Table, Text.
      4. Verify that you can view and toggle the Heatmap toggle Eye icon, in the bottom left corner, which turns on and off the course elements highlighting.
        • Please note: The heatmap currently just works for the "Weekly" and "Topic" course formats.
      5. Verify that you can view and click on the Download icon, in the bottom right corner, which produces a course summary report in PDF format.
      6. Verify that you can view and click on the Report icon, in the bottom center, which brings you to the Accessibility toolkit.

            Unassigned Unassigned
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.