search

accessibilitysupported / a11ysupport.io

Accessibility Support data for various HTML, ARIA, CSS, and SVG features
https://a11ysupport.io/
Other
279 stars 32 forks source link

Help wanted #3

Open mfairchild365 opened 6 years ago

mfairchild365 commented 6 years ago

Please reply to this issue if you are interested in helping with the project.

Ways that you can help:

hollsk commented 6 years ago

I can help!

I'm mainly good for writing copy and for research.

I can help to an extent with running and verifying tests, but I don't have a comprehensive testing setup, and I'm not a habitual AT user. I can probably propose new features and tests too 🙂

modulist commented 6 years ago

Interested! subscribing...

robfentress commented 6 years ago

I'd be glad to help, as I have time, since I do this sort of stuff internally anyway. I have access to the following AT:

On Window 10 Fall Creators Edition

On MacOS High Sierra

iPad Pro (10.5") with iOS 11.4.1

iPod touch (6th generation) with iOS 11.3.1

Samsung Galaxy S8 with Android 8.0.0

Android Pixel C with Android 8.1

Humanware BrailleNote Touch (though I don't know Braille so that would require assistance from our Braille expert)

We also have assorted older software, like Kurzweil and WindowEyes, but I'm not sure how useful it would be to test with them.

robfentress commented 6 years ago

I do not need to use any of these AT, but I know how to use them well enough for testing (with the caveat that I might not use them the same way as someone who has to use them).

alexroseb commented 6 years ago

I'd love to help! I can probably propose new features and tests and also I'm pretty good at technical writing for things like instructions and copy/documentation. I'm interested in the potential of running dev workshops as well. I don't use AT very often, so I'm not the best person to help with running those tests, but other than that I'd like to help in any way possible.

mfairchild365 commented 6 years ago

I'm glad to hear all of your interest!

@hollsk @robfentress @alexroseb - Ideally the tests would be set up so that you don't need to have any experience using AT in most situations. The commands and expected results would be right there.

However, that won't be the case as we get started because those previous results are not there. That is why test results should be verified by at least one other user. By creating an issue that details the results, there is an opportunity for others to make suggestions and for everyone to learn.

ShadowBB commented 6 years ago

I want to help. I audit sites with WCAG for a living and consult professionally on A11Y.

I am probably best for the following tasks:

mfairchild365 commented 6 years ago

Hey folks. Just wanted to mention that I haven't forgotten about this project. Things are just rather busy right now. I fully intend to keep this moving forward.

Some of the next big tasks:

In the meantime, feel free to run more of the existing tests.

gsilver commented 6 years ago

Hey Michael!

I was just thinking the world needs this, when I ran into this via the iTag agenda for today.

I can propose and run tests, and verify results. I can help with the UX as well.

It occurred to me that other than doing this work specifically, this might be a good repo of observations found by serendipity in the course of our other work.

hchiam commented 4 years ago

Not sure if it's needed, but I can help manually test on VoiceOver (macOS). If I understand correctly, I can run tests by clicking on links in the run-tests page. But for features without any data (e.g. "aria-activedescendant attribute (aria)"), how might I create tests for them?

mfairchild365 commented 4 years ago

@hchiam - Thank you for your interest! Yes, you can identify tests that need to be run from the run-tests page. That page could honestly use some work to make it easier to identify a test and kick off a test run. I'll consider that.

Creating tests is a lot more complex and requires a pull request. It also requires extensive knowledge of both this project and assistive technologies. Is that something you are interested in?

hchiam commented 4 years ago

Thanks @mfairchild365!

First, I’ll try doing a PR for some test run data.

Then I might be interested in creating at least 1 test afterwards, but I admit I'm a noob. For example, I can create a test for aria-atomic by putting some newly acquired knowledge into practice. https://github.com/accessibilitysupported/a11ysupport.io/blob/master/data/tech/aria/aria-atomic_attribute.json

sarahmonster commented 4 years ago

Improve the UI of the site; reduce clutter and make it easier to understand

👋 I'd love to help! I have a background in visual & UX/product design and am generally a big fan of making things more usable and comprehensible.

mfairchild365 commented 4 years ago

@hchiam - please let me know if you have any questions!

@sarahmonster - please feel free to provide any feedback! I'd be glad to hear your thoughts, and I know that there is a lot of room for improvement.

furstenberg commented 4 years ago

Just arrived at this project. This is a very good initiative. Thank you.

I'll ask my manager if we can try to work on running some of these tests.

sarahmonster commented 4 years ago

@mfairchild365 I have a few thoughts off the top of my head, but it's good to get a solid understanding of the aims and requirements of the project before diving into some solutions, to be sure that we're solving actual problems. 🙌

Any objections to my starting a new issue to discuss in more detail?

mfairchild365 commented 4 years ago

@sarahmonster please do :)

hchiam commented 4 years ago

@hchiam - please let me know if you have any questions!

Thanks @mfairchild365! All previous tests have result "unknown", but I keep getting "Action, button". This is a result "fail", and not result "unknown", right? https://github.com/accessibilitysupported/a11ysupport.io/pull/89#issuecomment-555808178

sandrina-p commented 3 years ago

Hi @mfairchild365,

I've discovered this website around 1 year ago and honestly this is one of my favorite gems about accessibility. Like a "can I use" but for ARIA.

In every workshop I give about Web Accessibility, I mention this website, a hidden gem 💎.

I'd love to help here. As a frontend engineer, how I can help:

@mfairchild365, it would be helpful if the issues had labels to better identify the status of each one (bug, feature, good starter, etc...)