search

openfarmcc / OpenFarm

A free and open database for farming and gardening knowledge. You can grow anything!
https://OpenFarm.cc
MIT License
1.57k stars 242 forks source link

screen readers, ARIA, folks with slow internet connections. #116

Open simonv3 opened 10 years ago

simonv3 commented 10 years ago

We should probably start thinking of how we can build the site to be fairly flexible for all types of people.

Good reading: http://a11yproject.com/

I know very little about how to tackle this properly, and how to implement it specifically with RoR. I can definitely do more research though.

We should at least set up a framework so that it's super easy to build on top of it.

roryaronson commented 10 years ago

Good thinking Simon! I bet we could find a grant to fund that specific work too. It's a good thing to keep in mind when laying the foundation, though I think we should watch out for feature creep at this early stage and get an MVP out first. Not to stop the discussion though =D

simonv3 commented 10 years ago

I could argue that this isn't feature creep and kind of just what we should be doing from the get go. If we're doing it right from the start then it should not be much extra work.

Having said that, I don't know how to do it, @rickcarlino do you have any thoughts?

roryaronson commented 10 years ago

Sounds good! I accept my ignorance of programming =p

simonv3 commented 10 years ago

You're not alone :P

RickCarlino commented 10 years ago

I think it's more of a philosophy of design that happens incrementally rather than something we need to build all at once. I bet there are linters out there that can catch design flaws that hinder accessibility and notify us on how to fix. This, along with i18n and maintaining a high level of test coverage are the things we need to stay on top of and review from time to time. I will definitely keep this in mind when I create / merge future code.

Perhaps this is one of those things that should be written into a 'contributor's guide' on the wiki since it's more of a mentality than a feature.

simonv3 commented 10 years ago

That's a really good way of looking at it. I'm going to do some combing of resources, and see what we definitely should include. I'll start putting something together for the guide based on that.

On Sun, Aug 31, 2014 at 7:01 AM, Rick Carlino notifications@github.com wrote:

I think it's more of a philosophy of design that happens incrementally rather than something we need to build all at once. I bet there are linters out there that can catch designs flaws that hinder accessibility and notify us on how to fix. This, along with i18n and maintaining a high level of test coverage are the things we need to stay on top of and review from time to time. I will definitely keep this in mind when I create / merge future code.

Perhaps this is one of those things that should be written into a 'contributor's guide' on the wiki since it's more of a mentality than a feature.

— Reply to this email directly or view it on GitHub https://github.com/FarmBot/OpenFarm/issues/116#issuecomment-53974127.

m3talsmith commented 10 years ago

I can spend this week back implementing some accessibility tags into the design if you guys are ok with that. It will ease me back into the project. I might wrote a developers guide with best practices for that as well. On Aug 30, 2014 6:04 PM, "Simon" notifications@github.com wrote:

That's a really good way of looking at it. I'm going to do some combing of resources, and see what we definitely should include. I'll start putting something together for the guide based on that.

On Sun, Aug 31, 2014 at 7:01 AM, Rick Carlino notifications@github.com wrote:

I think it's more of a philosophy of design that happens incrementally rather than something we need to build all at once. I bet there are linters out there that can catch designs flaws that hinder accessibility and notify us on how to fix. This, along with i18n and maintaining a high level of test coverage are the things we need to stay on top of and review from time to time. I will definitely keep this in mind when I create / merge future code.

Perhaps this is one of those things that should be written into a 'contributor's guide' on the wiki since it's more of a mentality than a feature.

— Reply to this email directly or view it on GitHub https://github.com/FarmBot/OpenFarm/issues/116#issuecomment-53974127.

— Reply to this email directly or view it on GitHub https://github.com/FarmBot/OpenFarm/issues/116#issuecomment-53975118.

RickCarlino commented 10 years ago

I would hold off for about a week before investing too much time on it- there are some big changes coming down the pipe. Hopefully we can get it published shortly so that everyone is on the same page.

m3talsmith commented 10 years ago

Will do On Sep 1, 2014 10:00 AM, "Rick Carlino" notifications@github.com wrote:

I would hold off for about a week before investigating too much time on it- there are some big changes coming down the pipe. Hopefully we can get it published shortly so that everyone is on the same page.

— Reply to this email directly or view it on GitHub https://github.com/FarmBot/OpenFarm/issues/116#issuecomment-54078965.

simonv3 commented 9 years ago

@m3talsmith Are you still interested in doing this?

simonv3 commented 8 years ago

we should let tota11y loose on our site: https://khan.github.io/tota11y/