Administrative Workspace - Announcements - Add Attachments - Non-Standard Interface and Accessibility Issue
GENERAL
TESTING
GENERAL
TESTING
Description
Attachments
2
- 17 Jul 2019, 11:37 AM
- 17 Jul 2019, 11:34 AM
Activity
Show:
Shawn Foster July 17, 2019 at 2:21 PM
We reviewed this at today's Sakai UX call. The group agreed that this is an issue that needs to be addressed. The Add menu doesn't seem to have the style and functionality that it should so that it looks like the Action menu in Resources.
We also noticed some issues with JavaScript functionality missing on the Add Announcement page, so that might be a hint as to what is missing.
Thanks, @Alan Regan, for reporting it!
Details
Details
Priority
Components
Assignee
Core Team
Core TeamReporter
Alan Regan
Alan ReganCreated July 16, 2019 at 1:00 PM
Updated August 19, 2019 at 11:58 AM
ISSUE
The "Add Attachments" process for an administrator account in the "Announcements" tool of "Administrative Workspace" does not use the same attachment process as a course or project site. There are two items to review and address:
Non-standard "Add" process to upload files, create folders, etc. (A bulleted list appears where the word "Add" is clickable via mouse but a triangle icon is not clickable.)
The "Add" feature is not keyboard accessible (cannot tab to the selection).
STEPS TO REPLICATE
Go to Trunk (https://trunk-mysql.nightly.sakaiproject.org/)
Log in as the "admin" account
Go to "Administrative Workspace"
Click "Announcements"
Click "Add"
Scroll down and click "Add Attachments"
The non-standard attachments page displays with a view of the Administrative Workspace Resources
"Tab" on the page and attempt to interact with the "Add" link (I have not been successful using Chrome 75.0.3770.100 for Windows 10). I can click the link with my mouse which displays a bulleted list of actions.
PROPOSAL
Implement the standard "Actions" drop-down menu from Resources that is keyboard accessible and consistent with other tools. Or implement the standard "Add Attachments" process, if appropriate. (My instinct says that since it interfaces with the Admin Resources the normal process from a course or project site may not be feasible.)
NOTE: I am not sure how far back this issue goes. I can replicate in Sakai 12 but I have not tested for Sakai 11 or earlier.