caMicroscope
Replies: 2 comments 19 replies
-
|
Yes sure I will be happy to assist |
Beta Was this translation helpful? Give feedback.
-
|
Awesome. Thank you @We13b-MD. I and some other contributors have raised a couple of assessibility issues. The common ones are:
Do you think it's something you can take on; set up a workflow that will automatically test for these issues when a push is made to the repository? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah sure can you send a screenshot of the issue regarding low color contrast |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Does this help? |
Beta Was this translation helpful? Give feedback.
-
|
Yes let me take a good look at it will get back to you I will try setting up the workflow if I have any issues I will let you know |
Beta Was this translation helpful? Give feedback.
-
|
Alright. No problem. When you're done, I'd love to know how you set up the workflow. |
Beta Was this translation helpful? Give feedback.
-
|
I think you may find this helpful: https://github.com/dequelabs/axe-core |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone. |
Beta Was this translation helpful? Give feedback.
-
|
When building again add no cache to the build command |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @We13b-MD. I will implement that |
Beta Was this translation helpful? Give feedback.
-
Hi everyone, hope we're all enjoying contributing to the project.
I'm working on the Accessibility task in the contributor task list. It struck me that there is an overlap between accessibility and testing. So rather than just identify accessibility bugs, we could set up Github workflows to test for accessibility whenever a change is made to the repository. This way, we can catch accessibility bugs quicker and fix them.
I've spent a chunk of my time reading about the WCAG 2.1 standards, how to check for accessibility using tools like Axe and Google Lighthouse. I've made some progress in that regard and succeeded in identifying some accessibility issues within caMicroscope. Where I'm facing a challenge is figuring out how to set up Github workflows that will automatically test for these issues. I've devoured a substantial amount of Github documentation on the subject but it appears it was written with developers in mind. As a UX designer, most of the explanation flies over my head.
I'm hoping to collaborate with other community members who are knowledgeable in the field and may already be contributing to testing. Please, if this is an area you're interested in, I'd appreciate your response to this message.
@birm
Beta Was this translation helpful? Give feedback.
All reactions