Theme 9: System Navigation Sample Clauses

Theme 9: System Navigation. This refers to general navigation aspects of the system. The test environment for the usability tests was xxxxx://xx0.xxx.xxxx.xx/ Table 19 - Case Study 1 External Testing System Navigation Theme Details Aspect Observation Suggestions for improvement Registration All testers reported that finding where to register was unclear and most spent one minute locating it at ‘login’. Suggest adding ‘login/register’ title to this function. Keep it in the same place on the screen. Tabs and breadcrumbs Font is far too small. Think about people with visual disabilities. Dashboard navigation Dashboard features were lauded but finding the dashboard was not intuitive, and most testers found it a bit confusing. What happens when you shut down one of the boxes on dashboard? How can you bring it back? Supply guidance / instructions. Submitting a blog Not clear what happens after blog is submitted. Email depositor to notify events, e.g. when blog submission is live. Export and basket features Very nice and good but location-wise they are too low; they seem like footers and not important information. Promote these features.
AutoNDA by SimpleDocs
Theme 9: System Navigation. This refers to general navigation aspects of the system. Table 25 - Case Study 2 External Testing System Navigation Theme Details Aspect Observation Suggestions for improvement Registration The log-in process makes you think you are logged in as a guest. No suggestions made Registration Registration task was not very easy to complete (link is hidden). His experience in computer systems helped him carry out the task assigned. He expects that this task will be much harder for a novel user. No suggestions made Dashboard navigation Sorting, organizing, browsing the information do not facilitate the navigation. No suggestions made Navigation Very easy to navigate. The user especially liked the provision of external links found in a post on the right sidebar. The interface was intuitive. No suggestions made The above section highlighted the issues identified during the test as well as included further suggestions coming from the testers. All of the participants followed the same set of tasks and were given the same questions to answer, which enabled a collation of the results. The overall impression of the testers about the system was positive. Many features of the system were praised by the testers. They were satisfied with the way the content was organised, accuracy of author names and dates, and the availability of citation information. The general view of the system was positive. However, the evaluation has been fruitful in identifying bugs and collecting suggestions for further improvements. All the suggestions were reported in this section and brought to the attention of the development team. Some of the prominent suggestions included various uses of date for changing the presentation order of weblog posts from chronological to reversed chronological and including faceted search by date. Most of the bugs and observations did not suggest a need for a major redesign or changes in the system.
Theme 9: System Navigation. This refers to general navigation aspects of the system. The test environment for the usability tests was xxxx://xx0.xxx.xxxx.xx/ Table 42 - Case Study 4 External Testing System Navigation Theme Details Aspect Observation Suggestions for improvement Registration Registration was an easy task. “Register” option could be more visible and distinct. Registration process After the message that the user received an email with a link to verify his account, a link to register appears again. The message gives the impression that you can login immediately. Wrong encoding to the Greek notification letter for the account verification. Register/login url is not https. The message should be clearer that you should see the email in order to proceed. Email text: “about 3 days” is not precise, maybe “about” should be removed. Check if username is the same with the password, inform the user if the password is weak/safe. Tabs Tabs help in navigation: you can see where you are and the adjacent options. Add border-radius to tabs. Bigger tabs and bigger font- size. Tabs Links open in same window. Links (from Files and Export as) to open in a new tab. Tabs Keywords and references usually was zero. If they are zero values, then make the tab inactive. Export As Element not prominent. Could be in a more visible position. It can be in another Tab because “Export” is important in the preservation concept. Maybe move the element above its current position. Fonts Fonts are not easy to read. Available languages text is too small. Green colour of the fonts makes them unreadable in combination with the green background in the top of the page. Bigger font-size in the footer. Maybe a background colour instead of the white background. Tab position Reference links (right sidebar) Do not obscure post content overlap with the content of the post. with the design. Drop down menus Drop-down menu (any field) show more options in case of the Greek language than in English. Add more options in English.
Theme 9: System Navigation. This refers to general navigation aspects of the system. The test environment for the usability tests was xxxxx://xx0.xxx.xxxx.xx/ Table 48 – Case Study 5 & 6 External Testing System Navigation Theme Details Aspect Observation Suggestions for improvement Registration Participants are not immediately sure if the “sign up” button is what we mean with “registration process” but other than this there was no problem. One user liked the option not to have to register to use the software. No further suggestions made. Navigation to account The word “dashboard” was not immediately clear to participants, in terms of what we meant. Also not that clicking on the user name brought you to the dashboard. One user was not able to figure out how to add widgets, but in the end he was able to figure it out on his own. Additional Comments: “Funny behaviour, not predictable which widget will jump where”. Supply guidance on dashboard functions and its benefits. Navigation with ‘time slider’ Some participants were unable to use the timeline slider to open a blog post. Either the link (accessed by hovering over the bullet point in the timeline slider) was not “alive”, or the No further suggestions made. participant could not access the actual post through the link that appeared when hovering over the bullet point in the timeline slider. This was true for several other blog pages that we attempted to access. Dashboard navigation User had a few difficulties returning to the dashboard once user began the searches. Supply guidance on how to get to the dashboard/account. Submitting a blog All participants completed this Hints or examples for the extra task successfully, but there information when submitting a was still some confusion in the blog are needed. interface. For example: AS: “What's the difference between referred and not referred? Why do I get to another screen which does nothing else but to ask me to press another button. The Topic List is not very intuitive and does not cover everything. The license type is not intuitive. I think you have to explain, why it's important to have restricted or private access.” The usability tests from August 2013 highlight confusion around navigation, especially in relation to the dashboard and around various back scenarios (back from the search, back to the dashboard). The feedback shows issues with clarifying the benefits of some features (for e. g. why purchase restricted content, what is the license copy for, how to use the dashboard). T...

Related to Theme 9: System Navigation

  • Sites Sites shall mean the locations set forth in the Contract Documentation.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Synchronization The Licensor hereby grants limited synchronization rights for One (1) music video streamed online (Youtube, Vimeo, etc..) for up to 500,000 non-monetized video streams on all total sites. A separate synchronisation license will need to be purchased for distribution of video to Television, Film or Video game.

  • Internet Connectivity School must provide sufficient hardline internet connectivity and the required network configurations (provided in Exhibit A) for each Pixellot System to allow live broadcasts. PlayOn will provide the point-to-point wireless internet base station (“Point to Point”) when needed to deliver hardline internet connectivity to Pixellot Systems installed in outdoor venues; provided that PlayOn is able to select the make and model of the Point to Point system. In the event that School requests, or requires, a specific Point to Point system that is different from what is provided by PlayOn, then School must provide and install the Point to Point system at its own expense.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Infrastructure (a) The Borrower has and will maintain a sufficient infrastructure to conduct its business as presently conducted and as contemplated to be conducted following its execution of this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.