cmu-313 / mayan-edms Goto Github PK

Error as follows

Failing Elements

input<input class="select2-search__field" type="search" tabindex="0" autocomplete="off" autocorrect="off" autocapitalize="none" spellcheck="false" role="searchbox" aria-autocomplete="list" placeholder="" style="width: 0.75em;">

Lighthouse score for accesibility is 76

Observed SEO score of 78. Targeting "Links are not crawlable" warning caused by uncrawlable "a.disabled" link.

Located on /#/documents/document_types/

Current score for accessibility is 87

Also when implementing fix in #14 another lighthouse issue appears where we cannot have anything besides <li> and <template> tags in our unordered list

Currently the accessibility score for /dependencies/check_version page is 88.

The accessibility score of the "Create Message" page is 89. The issue I am targeting is "Background and foreground colors do not have a sufficient contrast ratio", specifically with the actions toggle dropdown, text on the screen, and the cancel button.

docker_postgresql_1 container restarts due to lack of permissions when running docker-compose in WSL2 with Ubuntu.
Running as elevated user with sudo results in docker_app_1 container restarting.

Upon evaluating the home screen's with google's "lighthouse" tool, the absence of labels from some of the site's elements has been flagged as an accessibility issue for those who use a screen reader. This problem exists across most menus, but is especially egregious on the "event subscriptions" page.

It seems as though #34 and #4 focus on labels in other parts of the site, but this page is yet to be addressed.

Improves the Accessbility score from 91 to 93 by making the color of certain texts darker on the Dashboard page.

The current performance score of the Mayan EDMS on Google Lighthouse is 59. I will attempt to reduce unused JavaScript to increase the performance score.

At 12:01:53 PM on 9/6/2021, the Lighthouse metrics were as follows:

I will be improving the performance metric which currently has a score of 53 and I'll be targeting the warning "Eliminate render-blocking resources" by deferring non-critical css files.

The All documents page has an accessibility score of 84, and the invalid values lead to incorrect interpretations for assistive technologies such as screen readers.

The current accessibility score given by lighthouse is 85 and the warning I am targeting is [aria-*] attributes do not have valid values which is checked by lighthouse against the WAI-ARIA specification.

The current performance score is 30.
Targeted warning: "Eliminate render-blocking resources"

I will attempt to improve the performance score by loading noncritical JS asynchronously.

The current Lighthouse accessibility score is 85. The Lighthouse-reported problem being targeted is that the color of the text "A short text used as the tag name", "The RGB color values for the tag", and the Cancel button do not have a sufficient contrast ratio with the color of the background. This lack of contrast makes it hard for users to read.

The accessibility score is currently 82 and gives the warning "Background and foreground colors do not have a sufficient contrast ratio." Low-contrast text in the Actions Toggle Dropdown is difficult or impossible for many users to read.

The current Lighthouse Accessibility score is 88. The problem I am targeting is that on the notification page, the "Actions" dropdown button's background and foreground color does not have a sufficient contrast ratio.

When uploading documents, the help text and drop down menu text have insufficient contrast with the background. Currently, the accessibility score is 88.

Currently the score for accessibility on the user details page is 88. One of the reasons is that there is not enough contrast in the blue text in the middle of the page

The accessibility score is currently 83. I'm addressing the issue "Background and foreground color do not have enough sufficient contrast" by changing the colors of the cancel button and text.

On the System->Tools->Events page when loading for a mobile device, the SEO score is 77, with one factor being that the tap targets not being sized appropriately.

The current lighthouse score for Accessibility is 89.

The warning that I am targeting is "Links do not have a discernible name"

Current performance score is 43. One lighthouse suggestion was to eliminate render-blocking resources (Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles). Most of bootstrap.min.css was unused code.

Current performance score is 46. One of the lighthouse suggestions is to eliminate render-blocking resources. After investigating with the Coverage tab of Google Chrome, I found the entire toastr.min.css is unused because the styling of toastr is replaced with bootstrap alert. So, removing toastr.min.css would not modify appearance or functionality of the website.

The current lighthouse score for accessibility on the /events/events/ page is 89. This can be improved by improving the contrast ratio between the background and foreground colors for certain elements.

Current Lighthouse accessibility score for this page is 89.

Targeting 'Background and foreground colors do not have a sufficient contrast ratio.' warning for 'cancel' button

The current score for the Accessibility portion is a 90 (which is where this is occurring). The bell and message icons do not have any text which may be confusing to users since they may not recognize those icons.

I will be targeting the "Background and foreground colors do not have a sufficient contrast ratio" warning on the /home page to improve its current accessibility score from 89. Increasing the contrast ratio of the View Details and Search Buttons will make the buttons readable for more users and in turn improve the accessibility of this site.

The Accessibility score reported by Google Lighthouse for the Mayan homepage is 89. One of the issues reported in this category is insufficient contrast between the background and foreground colors of the homepage's buttons.

Lighthouse reports the following scores for the desktop version of the "Checkouts/Documents" page.
Performance: 48, Accessability: 90, Best Practices: 100, SEO: 78
An offending issue that Lighthouse notes is responsible for the SEO score of 78 is an uncrawlable link titled "a.disabled"

The "Label" and "Creation Date" texts do not have sufficient contrast ratio and the accessibility score is at an 89. This is an accessibility issue because low contrast ratios can make text difficult to read for some users.

I created changes to the root and base_plain files which allowed the meta descriptions to be much more detailed - allowing people who search on any search engine to be able to find the website from the main keywords relevant to the website such as document management, business workflow, and access control.

This improved the SEO score on LightHouse from 82 to 91.

The current accessibility score is 79.
The warning I am targeting is insufficient contrast between the titles "Actions" , "Secondary" and the background.

Initially, lighthouse gives 89/100 for accessibility. Among the metrics to improve the current accessibility score, I chose to fix ARIA ID being not unique.

The issue is relevant to Lighthouse "Accessibility" score and found when viewing event subscriptions for a cabinet. The current Lighthouse scores and page where the issue is found are attached below (note Accessibility is at 84):

Furthermore, Lighthouse describes the issue as shown below:

The current Accessibility Lighthouse score is at 83. Lighthouse recommends increasing the contrast in the text and the background of the cancel button.

Lighthouse gave 89 on SEO for my running Mayan instance. One warning states that the meta description is missing, which affects the crawlers' understanding of the website's content.

The current Lighthouse score for performance is 84. One of the reasons is that Background and foreground colors do not have a sufficient contrast ratio. As text that has a low contrast ratio—that is, text whose brightness is too close to the background brightness—can be hard to read.

Lighthouse currently gives a 68 performance score on /home because text-based resources is not served with compression. The warning/opportunity being targeted is "Enable text compression".

The current Accessibility lighthouse score on the /accounts/user/edit/ page is 89.
The warning I am targeting is: Background and foreground colors do not have a sufficient contrast ratio.
I will fix this by increasing the contrast ratio between the background and foreground colors for a few elements: the help block text, as well as the Cancel button text.

Lighthouse reports that documents do not have a meta description, giving the SEO category a score of 82. Adding a meta description would make Mayan results in search engines more concise.

some "li" elements are placed outside of "o>" and "ul", which is not accessible for some screen readers This resulted in a lighthouse score of 89 on the second page of the new document page

Though the page overall has an accessibility score of 86, there is a hidden dialogue-close button that could easily be confusing for screen readers and users.

The SEO score of the "About" page is 78. The warning I am targeting is "Document does not have a meta description".

Currently, the login page has an SEO score of 89 due to the lack of document meta descriptions. After successfully logging in, the homepage has the same issue and has an SEO score of 78.

Google Lighthouse gave an Accessibility score of 89 for the Mayan homepage. One of the issues reported is that the ARIA IDs are not unique in the page, which can cause assistive technologies to only announce the first element of an ID instead of all elements.

Index templates to be queued for rebuilding, Cancel buttons are too light
http://localhost/#/indexing/instances/rebuild/
Performance: 28
Accessibility: 77
Best Practices: 93
SEO: 82

The current Lighthouse Accessibility score is 81. The Lighthouse-reported problem being targeted is that the "Actions"
dropdown button's background color does not have a sufficient contrast ratio with the text color of the button.