You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's easier to ignore a WCAG problem than to fix it, so users ignore problems. Why don't we create one button to locate and fix problems?
Solution
Admins click a "Locate & Fix" button, which fixes WCAG compliance issues.
Development
"Locate & Fix" is a complex feature to build. First, we must identify what WCAG compliance issues we can solve. Then we must figure out how to find source code related to the issue. Finally, we must ensure that any changes can be previewed and rolled back.
I propose we focus on one common compliance issue at a time, testing MVP versions as we iterate toward production-ready versions.
Locate & Fix Color Contrast: The First Issue We Tackle
Many compliance issues are around color contrast.
Why don't we output a stylesheet with compliant color contrast? That MVP would test if users want to fix color contrast issues, building the starting blocks for further automation.
Locate & Fix Color Contrast: MVP User Experience
Here is how I imagine the "Color Contrast Fixing" feature works:
User links their stylesheet to a site.
WAVE reports color contrast issues.
User clicks "Locate + Fix"
They select from several options of colors in the same family.
Once fixed, the app exports the revised CSS.
Locate & Fix Color Contrast: Known Issues
As I said, the described user experience is an MVP. We will launch the feature to see if folks are interested in it, then solve these and other issues:
SCSS Support: How do we know if CSS is generated from SCSS? I don't know, so we can't support SCSS (yet).
Inline CSS Support: We won't fix inline CSS without access to a CMS, which we can't access (yet).
Automation: Ideally, we want to commit the updates to a repo for testing. We're no doing that (yet).
Future Developments
If fixing color contrast works, perhaps we can fix missing alt text? Or perhaps we further automate color contrast? Hopefully, the MVP for color contrast is wildly successful so that we can tackle ever-more problems, continuously optimizing our work.
The ultimate goal is to make fixing content accessibility errors as easy as possible. Easy fixes = Greater Accessibility
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The Problem
It's easier to ignore a WCAG problem than to fix it, so users ignore problems. Why don't we create one button to locate and fix problems?
Solution
Admins click a "Locate & Fix" button, which fixes WCAG compliance issues.
Development
"Locate & Fix" is a complex feature to build. First, we must identify what WCAG compliance issues we can solve. Then we must figure out how to find source code related to the issue. Finally, we must ensure that any changes can be previewed and rolled back.
I propose we focus on one common compliance issue at a time, testing MVP versions as we iterate toward production-ready versions.
Locate & Fix Color Contrast: The First Issue We Tackle
Many compliance issues are around color contrast.
Why don't we output a stylesheet with compliant color contrast? That MVP would test if users want to fix color contrast issues, building the starting blocks for further automation.
Locate & Fix Color Contrast: MVP User Experience
Here is how I imagine the "Color Contrast Fixing" feature works:
Locate & Fix Color Contrast: Known Issues
As I said, the described user experience is an MVP. We will launch the feature to see if folks are interested in it, then solve these and other issues:
Future Developments
If fixing color contrast works, perhaps we can fix missing alt text? Or perhaps we further automate color contrast? Hopefully, the MVP for color contrast is wildly successful so that we can tackle ever-more problems, continuously optimizing our work.
The ultimate goal is to make fixing content accessibility errors as easy as possible. Easy fixes = Greater Accessibility
Beta Was this translation helpful? Give feedback.
All reactions