Sai83 / accessibilityscore

Mobility Accessibility Score
0 stars 0 forks source link

State Website on Accessible Software - food for thought. #2

Open mel1877 opened 9 years ago

mel1877 commented 9 years ago

http://mn.gov/mnit/programs/accessibility/

mel1877 commented 9 years ago

Perhaps we should consider classifying our scoring based on these categories. I was thinking perhaps the sliders on the map. We could exclude groups of data based on the type of disability.

Section 508 addresses accessibility for people who have:

•Visual disabilities. •Hearing disabilities. •Motor disabilities. •Speech disabilities.

mel1877 commented 9 years ago

The accessibility officer here at the State focuses more on making websites and applications useable for the handicap. Although I think it would be ideal to follow these guidelines in developing our app.

diavy commented 9 years ago

I agree that classify the scoring based on categories is a good strategy. Correspondingly, we may figure out some special facility that is especially built for a certain type of disabilities. For example, a landlord with a "no pets" policy may be required to grant an exception to this rule and allow an individual who is blind to keep a guide dog in the residence. Then when we calculate the score, we should take that factor into consideration.

On Jun 8, 2015, at 10:15 AM, Melinda notifications@github.com wrote:

Perhaps we should consider classifying our scoring based on these categories. I was thinking perhaps the sliders on the map. We could exclude groups of data based on the type of disability.

Section 508 addresses accessibility for people who have:

•Visual disabilities. •Hearing disabilities. •Motor disabilities. •Speech disabilities.

— Reply to this email directly or view it on GitHub https://github.com/Sai83/accessibilityscore/issues/2#issuecomment-110034619.

fschilder commented 9 years ago

great ideas! I guess we mostly were looking at motor disabilities which is a good start though. Melinda, do you think there is data out there covering other disabilities?

on another topic: would all of you be fine with mentioning their names in a THomson Reuters internal post? I would like to post a short on the internal web site (like facebook for TR exmployees).

Thanks, Frank

On Mon, Jun 8, 2015 at 12:07 PM, David notifications@github.com wrote:

I agree that classify the scoring based on categories is a good strategy. Correspondingly, we may figure out some special facility that is especially built for a certain type of disabilities. For example, a landlord with a "no pets" policy may be required to grant an exception to this rule and allow an individual who is blind to keep a guide dog in the residence. Then when we calculate the score, we should take that factor into consideration.

On Jun 8, 2015, at 10:15 AM, Melinda notifications@github.com wrote:

Perhaps we should consider classifying our scoring based on these categories. I was thinking perhaps the sliders on the map. We could exclude groups of data based on the type of disability.

Section 508 addresses accessibility for people who have:

•Visual disabilities. •Hearing disabilities. •Motor disabilities. •Speech disabilities.

— Reply to this email directly or view it on GitHub < https://github.com/Sai83/accessibilityscore/issues/2#issuecomment-110034619 .

— Reply to this email directly or view it on GitHub https://github.com/Sai83/accessibilityscore/issues/2#issuecomment-110075239 .

minmadic commented 9 years ago

I'm cool with that Frank. :)

AJ

fschilder commented 9 years ago

If you're fine with it, could you quickly reply with your full name and a short description (on the level of detail you would like to be described)?

Thanks, Frank

On Wed, Jun 10, 2015 at 8:43 AM, Frank Schilder schilderf@gmail.com wrote:

great ideas! I guess we mostly were looking at motor disabilities which is a good start though. Melinda, do you think there is data out there covering other disabilities?

on another topic: would all of you be fine with mentioning their names in a THomson Reuters internal post? I would like to post a short on the internal web site (like facebook for TR exmployees).

Thanks, Frank

On Mon, Jun 8, 2015 at 12:07 PM, David notifications@github.com wrote:

I agree that classify the scoring based on categories is a good strategy. Correspondingly, we may figure out some special facility that is especially built for a certain type of disabilities. For example, a landlord with a "no pets" policy may be required to grant an exception to this rule and allow an individual who is blind to keep a guide dog in the residence. Then when we calculate the score, we should take that factor into consideration.

On Jun 8, 2015, at 10:15 AM, Melinda notifications@github.com wrote:

Perhaps we should consider classifying our scoring based on these categories. I was thinking perhaps the sliders on the map. We could exclude groups of data based on the type of disability.

Section 508 addresses accessibility for people who have:

•Visual disabilities. •Hearing disabilities. •Motor disabilities. •Speech disabilities.

— Reply to this email directly or view it on GitHub < https://github.com/Sai83/accessibilityscore/issues/2#issuecomment-110034619 .

— Reply to this email directly or view it on GitHub https://github.com/Sai83/accessibilityscore/issues/2#issuecomment-110075239 .

mel1877 commented 9 years ago

Melinda Miller - Sr. Management Analyst with the State of Minnesota MN.IT Services.

diavy commented 9 years ago

HI, Just want to share the following two official websites, which are authoritative information source about disabilities

One is MN http://www.mndisability.gov/public/content.do?term_id=142&level=0 http://www.mndisability.gov/public/content.do?term_id=142&level=0

The other is federal: https://www.disability.gov/ https://www.disability.gov/

Let’s see how we can integrate important features into our accessibility score for disabilities.

On Jun 10, 2015, at 5:35 PM, Melinda notifications@github.com wrote:

Melinda Miller - Sr. Management Analyst with the State of Minnesota MN.IT Services.

— Reply to this email directly or view it on GitHub https://github.com/Sai83/accessibilityscore/issues/2#issuecomment-110937346.