trillium-solutions / mendocino-wp-theme Goto Github PK

Site has overlapping use for some Post Types.

"Posts" can be categorized as News, Service Alert, Board of Directors, etc. but have limited functionality. User wanted to create a News post, created it through Posts and categorized it as News, but the article failed to display in the News section.

But there are specific Post types to create these elements. As far as I can tell these are working as expected. Instructed user to create the News post using the News Post Type.

I think we should remove the generic "Post" post type or at least remove those categories better served by their specific post types.

Board meetings data somehow dropped off the website in the recent update. They have an upcoming meeting soon so this is urgent for them.

Layout tables were used before css was as robust as it is now for handling presentation and design. However, this is a misuse of the <table> element, and can cause accessible technologies to misinterpret the content.

For example, the homepage form is a layout table. There may be others throughout the site.

Links with text like "click here" and "see all" are inaccessible to screen readers. Remove "see all" links from homepage and anywhere else they occur, and instead just make the relevant text (e.g. "News" or "Alerts") into a link.

The main nav menu should use icons + text, rather than including the text within the icon.

Some fields on the homepage planner have a "tabindex" attribute. Remove this entirely from the homepage form, and check that it isn't present anywhere else on the website.

The basic link color should be darker.

Per https://trilliumtransit.zendesk.com/agent/tickets/52334

@websites we're takiung back Mendocino! somehow

it's timetables are...not
example: https://mendocinotransit.org/routes/route-65/northbound/

but good news! we now have

1. updated their schedules
2. made tts
3. they all look good on my end except 7/9, which is multiroute so I can't run it on my own.

options

1. your team attempts to tcp-ify the website, a la tart
2. my team uses html to attempt update via WP (I don't see anything on sftp, but I also haven't been on this site in forever)
3. do nothing at this time

from @ekeaton

1. Mendo is much older than TART and isn't linked to TCP at all. TART was, it just used Tablepress, so the process was half done and pretty smooth-ish-ish. Mendo would require a larger website overhaul to get set up with TCP at this time.
2. Mendo only uses SFTP for PDF's so you're right TT's aren't uploaded there. They are done via the timetable pages in WP. Example here: https://mendocinotransit.org/wp-admin/post.php?post=1723&action=edit

Many moons ago when I took all their TT's down, I just removed the times from the TT's and not the HTML tables themselves, so the structure is all there. Their HTML looks custom-like, semi-similar to YARTS. But if you want to go rouge with the generic tt's from g2h...
To find a tt for a route in WP pages, use the search bar and search "Route - (number of route) - (direction).
3. Yes! :)

cc @danielleogden @NomeQ

Possible to copy code + styles from other themes. If you give the <main> element an ID of content during #3 you could even just copy the code directly from Ellensburg.

The nav Menu button for the mobile site isn't working.

The many background and gradient images could be compressed without noticeable quality loss, or possibly even be replaced with css gradients and removed entirely.

From client:
On our landing page there’s a blue circle with the route 7 for a link. The link takes us to the route 75 which is incorrect. The 7 is a Ukiah route that we are not currently using. The other link inside the schedule page also links to 75 can we just put a temp page that says due to the pandemic we do not currently have a route 7? Thanks

We'll have to change up the base styles from the site here, because each input needs a label associated with it, and "When" is being applied to multiple elements. "Date" and "Time" need associated labels, as does the dropdown select, I suggest "Depart" for that label.

This was actualy part of the accessibility upgrade project and slipped by us! We still have plenty of budget for it (just stop doing any more work on the nice-to-have accessibility updates). If you have any questions, please work with @NomeQ to get this implemented.

Alt text is used incorrectly throughout the site. There is no such thing as an "alt" attribute for <a> elements, or any elements other than images.

Remove alt text that is incorrectly implemented, and instead attach it to the appropriate images in the theme code.

The route page title should be an <h1>. Check and make sure that no other custom template pages are lacking an <h1> as well.

<ul>, <ol>, and <li> elements could all benefit from more padding and margin. E.g. https://mendocinotransit.org/how-to-ride/

I don't really like how the list bullets show up "outdented" instead of indented.

Add correctly formatted labels to the fare calculator.

"Alt" text is present, but is applied incorrectly to the surrounding elements, rather than the images themselves. Would also be helpful to update alt text to be more than a number. E.g. say "Route 3" instead of just "3"

• use <thead> for the top row table header where it exists
• add <caption> for tables to provide accessible titles/headings for fares

Let's get rid of this almost invisible and unnecessary header.

Unfortunately, even white text does not have enough contrast with the background, so we will need to make the blue darker.

Depending on how hard it is to edit the background image, we may want to just replace the background image with a css gradient.

Can copy the basic skeleton theme we use for all our sites, adding at minimum a <header>, <footer>, <main> and <aside> for all pages.

Note that <aside> is used for a sidebar element, if it exists.

Please help me put together a summary of the accessibility improvements we made to Mendocino. They just need something to provide to Caltrans to show what was done. Probably best if it's pretty high level descriptions. Can you just get a doc started with the list of improvements? Then I can flesh it out and make it look official.

Luis also pointed out that the homepage Ai map highlights were missing from the live site. Not sure when this happened.

Can you provide an hours estimate for what it would take to replace the current board meetings functionality with our newer Board Meetings post type? Like the one used for BAT

https://mendocinotransit.org/fares/

Picker doesn't load any zones. @evantrillium is there an issue with their fares data?

Every element ID should be unique on a given page. I found multiple of home-news-arhive-link on the homepage and route-connections-box on the route page. Remove the ID and use classes instead.

All images that have been uploaded to posts and pages should have alt text. These can be updated in wp-admin, in the media library.

Add screen reader text within the link element that says "Mendocino Transit Authority". Make this screen reader text an <h1> element on just the homepage.

Fare tables are squished and kind of hard to read. Update css styles so that tables are responsive (where appropriate), and have more padding for table cells.

All form elements should have a correctly associated <label>. Marking this as medium because there may be more form elements than I am aware of.

https://webaim.org/techniques/forms/controls

Replace the wrapping html element with

<!doctype html>
<html <?php language_attributes(); ?>>

• Fares icon is hard to see, too detailed for this size. Replace with simpler icon.
• Clock icon for schedules doesn't match style of "info" icon - find a clock that uses thicker line widths
• Add hover/focus styles for nav items that matches live site (box around nav item)

"Google" is not descriptive text. Change to "Get Directions"

• Is it possible to only load Recaptcha on the form pages where it is used?
• Can we replace Recaptcha with a different alternative?
• Is it at least possible to defer loading the Recaptcha js?

Create and style visible labels all time/date fields

Let's bill this to the tcp plugin task.

Note that rt 66 may come back in the future.

The icons need text that is accessible to screen readers so users know where the links go. The screen-reader-text class and css can be borrowed from Ellensburg, which provides a way to hide text from sighted users viewing the page, but still make it fully visible to screen readers.