Skip to content
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

Update MATS for section 508 compliance #1203

Open
mollybsmith-noaa opened this issue Jul 24, 2024 · 4 comments
Open

Update MATS for section 508 compliance #1203

mollybsmith-noaa opened this issue Jul 24, 2024 · 4 comments
Assignees
Labels
client Improvements or additions to the client code common Issue related to the common code MATS An issue affecting the MATS project MATScommon An issue affecting the MATScommon project METexpress An issue affecting the METexpress project task An actionable item of work

Comments

@mollybsmith-noaa
Copy link
Collaborator

I thought we already had an issue for this, but apparently not! We need to update MATS for accessibility requirements / section 508.

@mollybsmith-noaa mollybsmith-noaa added task An actionable item of work client Improvements or additions to the client code common Issue related to the common code MATS An issue affecting the MATS project METexpress An issue affecting the METexpress project MATScommon An issue affecting the MATScommon project labels Jul 24, 2024
@mollybsmith-noaa mollybsmith-noaa self-assigned this Jul 24, 2024
@ian-noaa
Copy link
Collaborator

ian-noaa commented Jul 24, 2024

Some notes.

Section 508/accessibility is more commonly known as a11y in the web world.

Accessibility Tooling

Even the best automated tooling only catches ~40% of accessibility issues. Using multiple tools and doing hand audits are recommended.

Resources

This issue could dovetail with #629 if we need to modify the site's CSS extensively. However, if we can achieve our accessibility goals without modifying the site's CSS, then treating those two issues separately would be ideal. There is also the question of whether Bootstrap or USWDS is the best design system for us to use.

@ian-noaa
Copy link
Collaborator

ian-noaa commented Aug 5, 2024

One other resource for this - GSL's Lunch & Learn series on accessibility: https://docs.google.com/document/d/1jfHN6vrQdbNwOyC2e1X71yB-F4jKPSSSALburo0iiAA/edit

@ian-noaa
Copy link
Collaborator

ian-noaa commented Oct 9, 2024

Another great resource is 18F's Accessibility guide. They're GSA's software modernization team and are currently working on the rewrite of weather.gov. They've been pushing some best practices for government websites. https://guides.18f.gov/accessibility/

From GSL, we also have the following:

I've been using some free readability scanners to check sites. Most of the issues revolve around colors and some graphics that don't have clear headers. Here is one that I like which gives you some details about what can be done to improve readability for 508 compliance.
https://userway.org/accessibility-checker/
and another one I liked...
https://www.accessibilitychecker.org/
Both sites give free recommendations for your site.

@mollybsmith-noaa
Copy link
Collaborator Author

As of now, MATS has been brought into compliance in the areas of color contrast, image alt text, unique div ids, that USA banner on the top of the page, and the "not operational" disclaimer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Improvements or additions to the client code common Issue related to the common code MATS An issue affecting the MATS project MATScommon An issue affecting the MATScommon project METexpress An issue affecting the METexpress project task An actionable item of work
Projects
None yet
Development

No branches or pull requests

2 participants