-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New resource request: ODS one pager #300
Comments
@mrose914 this is another one pager we took to conferences. I had a harder time with this one making it through the accessibility checker, so I left both items marked as "needs manual check" alone, but happy to do whatever is needed. Here's the report it generated: |
@mrose914 can you please do the manual review of this PDF for accessibility concerns and reply in this ticket when you have confirmed it is good to go? |
Yup, will do today! |
@thekaveman manual check all set. Logical reading order and color contrast lgtm. As a side note, it would probably be good to go through our Cal-ITP colors and make sure the color combinations pass contrast/that we define acceptable and unacceptable combinations. There doesn't seem to be an amazing way to streamline manual accessibility checks but that may be a step in the right direction. Tools like this can help: https://webaim.org/resources/contrastchecker/. Will add to my longer term backlog of TODOs. |
I believe Segacy had done extensive checking and reworking of the Cal-ITP color schemes (for the websites at least) to be accessibility compliant before she went out. |
I just took a look at the one-pager and tested with the Figma tool we use (Stark). Everything passes to AAA WCAG standards (the highest accessibility standard for web text) except for the blue subheading (e.g. Reduce cost and improve efficiency) which is hex code 046B99. I believe we updated that color (also known at Cal-ITP blue) to 045B86. So it looks like Segacy might have just been using the out of date color. I can change that in the Figma file now if that's preferable, but will need some guidance on creating PDFs |
@srhhnry thank you for this info! Glad there is a tool that is simpler than some of what I'm seeing. Let me find a few mins and we can sync - would love to get your thoughts on how to promote accessible colors/design for others across Cal-ITP, too. For this particular doc, let's please change to the updated Cal-ITP blue so we can proceed with the upload to the website. Thank you! |
Subheaders are updated to the new Cal-ITP blue (edit: in the Figma file). I also noticed there is a light grey page 1 at the bottom that also does not pass accessibility tests. I can see why it's light (to detract emphasis) but should I increase the contrast on that as well? I would argue we don't need it if there's...only one page. |
Chatted with @srhhnry. Let's remove the page number. As for next steps:
|
Page number removed |
@srhhnry thank you! Could you please link me or export the updated pdf here? |
Export can be found here on Figma: https://www.figma.com/file/XiYsM66X6c3nzVikVYB3or/ODS-one-pager?type=design&node-id=0%3A1&mode=design&t=wxObPYDk5d8YZutV-1 or attached here |
Approved?
Yes
Title
Overview: Operational Data Standard
Is the document correctly named and formatted?
Cal-ITP
?-
,.
and_
.report-june-2024.pdf
,file-v1.2.pdf
. AllowedGTFS-guidlines-v3.pdf
, as version 3 is an official version number.Asset URL
https://drive.google.com/file/d/1U8DKyqj9Nx5J0rpgVlHMBsctEm0I6IIO/view?usp=sharing
Category
Fact sheets & overviews
Tag
GTFS
Date - Year
2023
Date - Month
11
The text was updated successfully, but these errors were encountered: