Thread: [Tuxpaint-devel] Fwd: comar 508 compliant
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
From: Bill K. <nb...@so...> - 2008-11-06 21:03:39
|
I received the following email, and wanted everyone else's feedback on the various items. I think a few might be 'not applicable' due to the nature of Tux Paint (a drawing program). However, I think we're non-compliant in a number of places, and I'd like to make sure we implement features to cover these various accessibility requirements. ----- Begin forwarded message (with private info removed) ----- I am a media specialist in Maryland and love Tux Paint. There are several other librarians in the county that also want to install Tux Paint in our labs and media centers however we need to fill out a COMAR form in order to get the process started. I am wondering if I could get someone with your company to help fill out the form so we can get it installed. You may have had the question before... basically we need to know if the software is COMAR 508 compliant. The questions are below. Your help is greatly appreciated and I can't wait o start using Tux paint with my students! +------------------------------------------------------------------------------+ | Meets | Does Not | Requires | Not | | | | |Instructional| | | |Criteria|Meet Criteria| Alternative |Applicable| COMAR 508 COMPLIANCE | |--------+-------------+-------------+----------+------------------------------| | | | | |Able to execute functions from| | | | | |keyboard (keyboard shortcuts) | |--------+-------------+-------------+----------+------------------------------| | | | | |Application shall not disable | | | | | |activated features of other | | | | | |products (e.g., the | | | | | |application cannot disrupt the| | | | | |display color scheme which | | | | | |assists people with low vision| | | | | |showing a visual prompt when | | | | | |an error tone is sounded to | | | | | |assist hard of hearing users, | | | | | |or providing "sticky keys" | | | | | |that allow a user to press key| | | | | |combinations) | |--------+-------------+-------------+----------+------------------------------| | | | | |Has well-defined on-screen | | | | | |indications that the current | | | | | |focus moves among interactive | | | | | |interface elements as the | | | | | |input focus changes (e.g., a | | | | | |screen enlargement program | | | | | |magnifies a section of the | | | | | |screen, the program must be | | | | | |able to follow the focus as | | | | | |the focus changes) | |--------+-------------+-------------+----------+------------------------------| | | | | |Has user interface element | | | | | |including the identity, | | | | | |operation, and state of the | | | | | |element (e.g., button | | | | | |associated with a hand for | | | | | |getting help must have a text | | | | | |label that indicates help) | |--------+-------------+-------------+----------+------------------------------| | | | | |Bitmap images used to identify| | | | | |controls, status indicators | | | | | |must have consistent meaning | | | | | |assigned to application | |--------+-------------+-------------+----------+------------------------------| | | | | |Applications shall not | | | | | |override user selected | | | | | |contrast and color selections | | | | | |or other display attributes | | | | | |(e.g., a program must have a | | | | | |section in the software that | | | | | |tells the program not to use | | | | | |its own setting, but to use | | | | | |whatever settings are already | | | | | |in place) | |--------+-------------+-------------+----------+------------------------------| | | | | |Animation information must be | | | | | |displayable in at least one | | | | | |non-animated presentation mode| | | | | |at the option of the user | | | | | |(e.g., simulations are | | | | | |exception) | |--------+-------------+-------------+----------+------------------------------| | | | | |Color coding is not used as | | | | | |the only means of conveying | | | | | |information, indicating an | | | | | |action, prompting a response, | | | | | |or distinguishing a visual | | | | | |element (e.g., "green" start | | | | | |button must have text label | | | | | |combined with the use of | | | | | |color) | |--------+-------------+-------------+----------+------------------------------| | | | | |Product has variety of color | | | | | |and contrast settings | |--------+-------------+-------------+----------+------------------------------| | | | | |Product shall not have | | | | | |flashing or blinking text, | | | | | |objects, etc. with a frequency| | | | | |greater than 1 Hz and lower | | | | | |than 55 Hz | |--------+-------------+-------------+----------+------------------------------| | | | | |Product contains electronic | | | | | |forms that allow assistive | | | | | |technology to access the | | | | | |information, field elements, | | | | | |and functionality | +------------------------------------------------------------------------------+ ----- End forwarded message ----- -- -bill! "Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux! Download it today! http://www.tuxpaint.org/ |
From: Bill K. <nb...@so...> - 2008-11-06 21:06:55
|
On Thu, Nov 06, 2008 at 01:03:23PM -0800, Bill Kendrick wrote: > > I received the following email, and wanted everyone else's feedback on > the various items. I think a few might be 'not applicable' due to the > nature of Tux Paint (a drawing program). However, I think we're non-compliant > in a number of places, and I'd like to make sure we implement features to > cover these various accessibility requirements. Just started digging on COMAR 508, and need to run to lunch, but here's a little detail from http://doit.maryland.gov/policies/Pages/NVAGuidanceFAQs.aspx#universal Federal Section 508 mandates information technology universal accessibility. State statute mandates information technology nonvisual accessibility. Consequently, the State has adopted or paraphrased many, but not all, 'Section 508' regulations. In addition, Maryland has adopted several information technology nonvisual access regulations that are not found in federal regulations. Maryland information technology nonvisual access standards effective March 1, 2005 are COMAR 17.06.02.01-.12. -bill! |
From: Caroline F. <car...@go...> - 2008-11-07 00:18:13
|
2008/11/6 Bill Kendrick <nb...@so...>: > On Thu, Nov 06, 2008 at 01:03:23PM -0800, Bill Kendrick wrote: >> >> I received the following email, and wanted everyone else's feedback on >> the various items. I think a few might be 'not applicable' due to the >> nature of Tux Paint (a drawing program). However, I think we're non-compliant >> in a number of places, and I'd like to make sure we implement features to >> cover these various accessibility requirements. > > Just started digging on COMAR 508, and need to run to lunch, but here's > a little detail from > http://doit.maryland.gov/policies/Pages/NVAGuidanceFAQs.aspx#universal > > Federal Section 508 mandates information technology universal > accessibility. State statute mandates information technology nonvisual > accessibility. Consequently, the State has adopted or paraphrased > many, but not all, 'Section 508' regulations. In addition, Maryland > has adopted several information technology nonvisual access > regulations that are not found in federal regulations. Maryland > information technology nonvisual access standards effective March 1, > 2005 are COMAR 17.06.02.01-.12. > Might this even depend on the operating system it's running on? I'm not sure how to answer this except test it. We could make high contrast icons and things certainly. Do we have theming support? I guess we could make a new build if not. Caroline |
From: Caroline F. <car...@go...> - 2008-11-07 00:22:54
|
2008/11/7 Caroline Ford <car...@go...>: > 2008/11/6 Bill Kendrick <nb...@so...>: >> On Thu, Nov 06, 2008 at 01:03:23PM -0800, Bill Kendrick wrote: >>> >>> I received the following email, and wanted everyone else's feedback on >>> the various items. I think a few might be 'not applicable' due to the >>> nature of Tux Paint (a drawing program). However, I think we're non-compliant >>> in a number of places, and I'd like to make sure we implement features to >>> cover these various accessibility requirements. >> >> Just started digging on COMAR 508, and need to run to lunch, but here's >> a little detail from >> http://doit.maryland.gov/policies/Pages/NVAGuidanceFAQs.aspx#universal >> >> Federal Section 508 mandates information technology universal >> accessibility. State statute mandates information technology nonvisual >> accessibility. Consequently, the State has adopted or paraphrased >> many, but not all, 'Section 508' regulations. In addition, Maryland >> has adopted several information technology nonvisual access >> regulations that are not found in federal regulations. Maryland >> information technology nonvisual access standards effective March 1, >> 2005 are COMAR 17.06.02.01-.12. >> > > Might this even depend on the operating system it's running on? > > I'm not sure how to answer this except test it. We could make high > contrast icons and things certainly. Do we have theming support? I > guess we could make a new build if not. Colour and contrast settings - we don't do this Visual feedback for errors - think we do that anyway as no sound is used on its own to communicate information. Sounds like they want something like tool tips, or text under icons. Caroline |
From: Karl O. H. <ka...@hu...> - 2008-11-09 15:07:26
|
Torsdag 06. november 2008 skreiv Bill Kendrick: >| | | | |Able to execute functions from| >| | | | |keyboard (keyboard shortcuts) | This would be a nice feature in any case. Cursor keys to move pointer, Enter/Return to ‘click’, and ‘Page Up’/‘Page Down’ (and ‘Home’/‘End’) to move between stamp pages. -- Karl Ove Hufthammer |
From: Bill K. <nb...@so...> - 2008-11-21 23:00:58
Attachments:
comar508_tuxpaint.html
|
On Thu, Nov 06, 2008 at 01:03:23PM -0800, Bill Kendrick wrote: > > I received the following email, and wanted everyone else's feedback on > the various items. I think a few might be 'not applicable' due to the > nature of Tux Paint (a drawing program). However, I think we're non-compliant > in a number of places, and I'd like to make sure we implement features to > cover these various accessibility requirements. Here are the results I came up with. (Attached as an HTML file; hope that works ok on the list. :^/ ) -bill! |