Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-29837

Controling focus on page load in Morpheus




      Pre-Morpheus in Sakai (with a modern browser) when a student moves from item to item (ie. quiz questions, resource folders, forum topic) focus is placed on the content automatically. This is technically because the actions are occurring in an iframe. iFrames are their own full web pages and many specs, like WCAG2, dictate that focus be placed at the top of the page on load - and possibly it's by design too.

      In trunk/Sakai 11 focus is placed at the top of the "entire" of the page. This is a change from how Sakai previously worked, but also how other web pages and other LMSs handle this. In addition, Sakai also places at the top of the page the "Jump to content" accesskey to either select or press ctrl+c to jump right back to that next question (though, there's a related regression SAK-29771).

      It would be desirable to allow tools to place initial focus in a useful location. Certainly error notices and actions (ie. SAM-2218) and also when it's clear users would either use keyboard nav or their mouse to immediately skip to the #tocontent div.

      Options considered in related SAM-2042 include if the portal selected the first important element or if tool could send a hint to portal.

        Gliffy Diagrams




              • Assignee:
                mclare Matt Clare
                mclare Matt Clare
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created:

                  Git Source Code