Closed awentzel closed 2 years ago
This will be taken care of as part of the migration to this repo. For now, I'm renaming and updating this to be a task.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Latest FastPass results attached. These results can be replicated by running "Accessibility Insights for the Web" Anaheim extension on https://www.fast.design
I think most of the above are fixed; I'll run it later this evening locally if I can to confirm - but we can also run after tomorrow's scheduled deployment.
I gave it a run. Two issues remain. If you have
if you have the "Accessibility insights for web", then this link may also work extension://ghbhpcookfemncgoinjblecnilppimih/DetailsView/detailsView.html?tabId=589
I did a Fast Pass w/ Accessibility Insights (extension) to see how we're looking and found two new issues. extension://ghbhpcookfemncgoinjblecnilppimih/DetailsView/detailsView.html?tabId=432
@chrisdholt will these be completed for Thursday or should we punt one release?
I can’t see these with the link above, but @khamudom is working on the results of my pass on Sunday before I headed out of town. If it’s done for release, great - if not, I don’t see it as a blocker. Worst case, so long as nothing unpublished on npm is added after this release, we can always release as needed.
Pushing to next release
Should we push this out again?
@eisenbergeffect let's pull this from releases for now. The only outstanding issues for the homepage is color contrast issues which could be related to our recipes. This is an ongoing thing we'll need to be tracking and working on, I think it's a bit of churn to link it to a specific release as we continue to work and drive ahead on it. Not to mention, the docusaurus pages are contributing to overall errors across the fast.design namespace and we technically can't fix those. I'm fine with keeping this open, but it would be great to not link it directly to a given release right now.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug; what happened? See the validation errors produced by Accessibility Insights Edge (Chromium) browser extension.
What are the steps to reproduce the issue?
What behavior did you expect? No errors
If applicable, provide screenshots:
In what environment did you see the issue?
Is there any additional context? no