Thread Subject: Grouping of the current 28 software/webstandards
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
Return to this mailing list's archives
From: Jim Thatcher
Date: Wed, Oct 11 2006 11:35 AM
Subject: Grouping of the current 28 software/webstandards
All,
I think the grouping of standards will be very helpful. I like Peter Korn's
suggestion but have modified it somewhat. I find 4 groups as indicated
below. I think we will want to look at some web and software at the same
time since the requirements are similar or identical - See "don't use color
alone" as a prime example.
We entered the EITAAC (previous Advisory Committee) effort for software with
existing wording from Dept. Of Ed. and from IBM. That was a huge help. (The
fact that the software committee was only 8 members was a help too.)
Similarly, today we can bring in WCAG 2.0 and other guidelines addressing
these issues.
Can anyone provide a list of (recent) existing software guidelines?
Jim
Accessibility Consulting: http://jimthatcher.com/
512-306-0931
Group A: Interaction and operating system
21(a) When software is designed to run on a system that has a keyboard,
product functions shall be executable from a keyboard where the function
itself or the result of performing a function can be discerned textually.
21(b) Applications shall not disrupt or disable activated features of other
products that are identified as accessibility features, where those features
are developed and documented according to industry standards. Applications
also shall not disrupt or disable activated features of any operating system
that are identified as accessibility features where the application
programming interface for those accessibility features has been documented
by the manufacturer of the operating system and is available to the product
developer.
21(g) Applications shall not override user selected contrast and color
selections and other individual display attributes.
21(j) When a product permits a user to adjust color and contrast settings, a
variety of color selections capable of producing a range of contrast levels
shall be provided.
Group B: Requirements by content type
21(e) When bitmap images are used to identify controls, status indicators,
or other programmatic elements, the meaning assigned to those images shall
be consistent throughout an application's performance.
21(h) When animation is displayed, the information shall be displayable in
at least one non-animated presentation mode at the option of the user.
21(i) Color coding shall not be used as the only means of conveying
information, indicating an action, prompting a response, or distinguishing a
visual element.
21(k) Software shall not use flashing or blinking text, objects, or other
elements having a flash or blink frequency greater than 2 Hz and lower than
55 Hz.
22(j) Pages shall be designed to avoid causing the screen to flicker with a
frequency greater than 2 Hz and lower than 55 Hz.
22(a) A text equivalent for every non-text element shall be provided (e.g.,
via "alt", "longdesc", or in element content).
22(b) Equivalent alternatives for any multimedia presentation shall be
synchronized with the presentation.
22(c) Web pages shall be designed so that all information conveyed with
color is also available without color, for example from context or markup.
22(e) Redundant text links shall be provided for each active region of a
server-side image map.
22(f) Client-side image maps shall be provided instead of server-side image
maps except where the regions cannot be defined with an available geometric
shape.
22(k) A text-only page, with equivalent information or functionality, shall
be provided to make a web site comply with the provisions of this part, when
compliance cannot be accomplished in any other way. The content of the
text-only page shall be updated whenever the primary page changes.
22(p) When a timed response is required, the user shall be alerted and given
sufficient time to indicate more time is required.
Group C: Programmatic exposure of information:
21(c) A well-defined on-screen indication of the current focus shall be
provided that moves among interactive interface elements as the input focus
changes. The focus shall be programmatically exposed so that assistive
technology can track focus and focus changes.
21(d) Sufficient information about a user interface element including the
identity, operation and state of the element shall be available to assistive
technology. When an image represents a program element, the information
conveyed by the image must also be available in text.
21(f) Textual information shall be provided through operating system
functions for displaying text. The minimum information that shall be made
available is text content, text input caret location, and text attributes.
22(l) When pages utilize scripting languages to display content, or to
create interface elements, the information provided by the script shall be
identified with functional text that can be read by assistive technology.
22(m) When a web page requires that an applet, plug-in or other application
be present on the client system to interpret page content, the page must
provide a link to a plug-in or applet that complies with §1194.21(a) through
(l).
Group D: Correct coding
22(d) Documents shall be organized so they are readable without requiring an
associated style sheet.
22(g) Row and column headers shall be identified for data tables.
22(h) Markup shall be used to associate data cells and header cells for data
tables that have two or more logical levels of row or column headers.
22(i) Frames shall be titled with text that facilitates frame identification
and navigation.
21(l) When electronic forms are used, the form shall allow people using
assistive technology to access the information, field elements, and
functionality required for completion and submission of the form, including
all directions and cues.
22(n) When electronic forms are designed to be completed on-line, the form
shall allow people using assistive technology to access the information,
field elements, and functionality required for completion and submission of
the form, including all directions and cues.
22(o) A method shall be provided that permits users to skip repetitive
navigation links.
From: Tamas Babinszki
Date: Wed, Oct 11 2006 12:35 PM
Subject: Re: Grouping of the current 28 software/webstandards
An other suggestion would be to group the standards
based on the principles of the WCAG 2.0 latest draft.
Even if we decide not to follow this structure, such
grouping could potentially bring us closer to
harmonization.
Tamas Babinszki
--- Jim Thatcher < = EMAIL ADDRESS REMOVED = > wrote:
> All,
>
> I think the grouping of standards will be very
> helpful. I like Peter Korn's
> suggestion but have modified it somewhat. I find 4
> groups as indicated
> below. I think we will want to look at some web and
> software at the same
> time since the requirements are similar or identical
> - See "don't use color
> alone" as a prime example.
>
> We entered the EITAAC (previous Advisory Committee)
> effort for software with
> existing wording from Dept. Of Ed. and from IBM.
> That was a huge help. (The
> fact that the software committee was only 8 members
> was a help too.)
> Similarly, today we can bring in WCAG 2.0 and other
> guidelines addressing
> these issues.
>
> Can anyone provide a list of (recent) existing
> software guidelines?
>
> Jim
>
> Accessibility Consulting: http://jimthatcher.com/
> 512-306-0931
>
>
> Group A: Interaction and operating system
>
> 21(a) When software is designed to run on a system
> that has a keyboard,
> product functions shall be executable from a
> keyboard where the function
> itself or the result of performing a function can be
> discerned textually.
>
> 21(b) Applications shall not disrupt or disable
> activated features of other
> products that are identified as accessibility
> features, where those features
> are developed and documented according to industry
> standards. Applications
> also shall not disrupt or disable activated features
> of any operating system
> that are identified as accessibility features where
> the application
> programming interface for those accessibility
> features has been documented
> by the manufacturer of the operating system and is
> available to the product
> developer.
>
> 21(g) Applications shall not override user selected
> contrast and color
> selections and other individual display attributes.
>
> 21(j) When a product permits a user to adjust color
> and contrast settings, a
> variety of color selections capable of producing a
> range of contrast levels
> shall be provided.
>
>
> Group B: Requirements by content type
>
> 21(e) When bitmap images are used to identify
> controls, status indicators,
> or other programmatic elements, the meaning assigned
> to those images shall
> be consistent throughout an application's
> performance.
>
> 21(h) When animation is displayed, the information
> shall be displayable in
> at least one non-animated presentation mode at the
> option of the user.
>
> 21(i) Color coding shall not be used as the only
> means of conveying
> information, indicating an action, prompting a
> response, or distinguishing a
> visual element.
>
> 21(k) Software shall not use flashing or blinking
> text, objects, or other
> elements having a flash or blink frequency greater
> than 2 Hz and lower than
> 55 Hz.
>
> 22(j) Pages shall be designed to avoid causing the
> screen to flicker with a
> frequency greater than 2 Hz and lower than 55 Hz.
>
> 22(a) A text equivalent for every non-text element
> shall be provided (e.g.,
> via "alt", "longdesc", or in element content).
>
> 22(b) Equivalent alternatives for any multimedia
> presentation shall be
> synchronized with the presentation.
>
> 22(c) Web pages shall be designed so that all
> information conveyed with
> color is also available without color, for example
> from context or markup.
>
> 22(e) Redundant text links shall be provided for
> each active region of a
> server-side image map.
>
> 22(f) Client-side image maps shall be provided
> instead of server-side image
> maps except where the regions cannot be defined with
> an available geometric
> shape.
>
> 22(k) A text-only page, with equivalent information
> or functionality, shall
> be provided to make a web site comply with the
> provisions of this part, when
> compliance cannot be accomplished in any other way.
> The content of the
> text-only page shall be updated whenever the primary
> page changes.
>
> 22(p) When a timed response is required, the user
> shall be alerted and given
> sufficient time to indicate more time is required.
>
>
> Group C: Programmatic exposure of information:
>
> 21(c) A well-defined on-screen indication of the
> current focus shall be
> provided that moves among interactive interface
> elements as the input focus
> changes. The focus shall be programmatically exposed
> so that assistive
> technology can track focus and focus changes.
>
> 21(d) Sufficient information about a user interface
> element including the
> identity, operation and state of the element shall
> be available to assistive
> technology. When an image represents a program
> element, the information
> conveyed by the image must also be available in
> text.
>
> 21(f) Textual information shall be provided through
> operating system
> functions for displaying text. The minimum
> information that shall be made
> available is text content, text input caret
> location, and text attributes.
>
> 22(l) When pages utilize scripting languages to
> display content, or to
> create interface elements, the information provided
> by the script shall be
> identified with functional text that can be read by
> assistive technology.
>
> 22(m) When a web page requires that an applet,
> plug-in or other application
> be present on the client system to interpret page
> content, the page must
> provide a link to a plug-in or applet that complies
> with §1194.21(a) through
> (l).
>
>
> Group D: Correct coding
>
> 22(d) Documents shall be organized so they are
> readable without requiring an
> associated style sheet.
>
> 22(g) Row and column headers shall be identified for
> data tables.
>
> 22(h) Markup shall be used to associate data cells
> and header cells for data
> tables that have two or more logical levels of row
> or column headers.
>
> 22(i) Frames shall be titled with text that
> facilitates frame identification
> and navigation.
>
> 21(l) When electronic forms are used, the form shall
> allow people using
> assistive technology to access the information,
> field elements, and
> functionality required for completion and submission
> of the form, including
> all directions and cues.
>
=== message truncated ===
From: Richard Schwerdtfeger
Date: Wed, Oct 11 2006 12:59 PM
Subject: Re: Grouping of the current 28software/web standards
I agree. WCAG has been working on this for 4 years. This is a great
starting point.
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
Tamas Babinszki
<tbabinszki@yahoo
.com> To
Sent by: = EMAIL ADDRESS REMOVED = , TEITAC
teitac-websoftwar Web/Software Subcommittee
= EMAIL ADDRESS REMOVED = < = EMAIL ADDRESS REMOVED =
itac.org >
cc
10/11/2006 01:29 Subject
PM Re: [teitac-websoftware] Grouping
of the current 28 software/web
standards
Please respond to
TEITAC
Web/Software
Subcommittee
<teitac-websoftwa
= EMAIL ADDRESS REMOVED =
g>
An other suggestion would be to group the standards
based on the principles of the WCAG 2.0 latest draft.
Even if we decide not to follow this structure, such
grouping could potentially bring us closer to
harmonization.
Tamas Babinszki
--- Jim Thatcher < = EMAIL ADDRESS REMOVED = > wrote:
> All,
>
> I think the grouping of standards will be very
> helpful. I like Peter Korn's
> suggestion but have modified it somewhat. I find 4
> groups as indicated
> below. I think we will want to look at some web and
> software at the same
> time since the requirements are similar or identical
> - See "don't use color
> alone" as a prime example.
>
> We entered the EITAAC (previous Advisory Committee)
> effort for software with
> existing wording from Dept. Of Ed. and from IBM.
> That was a huge help. (The
> fact that the software committee was only 8 members
> was a help too.)
> Similarly, today we can bring in WCAG 2.0 and other
> guidelines addressing
> these issues.
>
> Can anyone provide a list of (recent) existing
> software guidelines?
>
> Jim
>
> Accessibility Consulting: http://jimthatcher.com/
> 512-306-0931
>
>
> Group A: Interaction and operating system
>
> 21(a) When software is designed to run on a system
> that has a keyboard,
> product functions shall be executable from a
> keyboard where the function
> itself or the result of performing a function can be
> discerned textually.
>
> 21(b) Applications shall not disrupt or disable
> activated features of other
> products that are identified as accessibility
> features, where those features
> are developed and documented according to industry
> standards. Applications
> also shall not disrupt or disable activated features
> of any operating system
> that are identified as accessibility features where
> the application
> programming interface for those accessibility
> features has been documented
> by the manufacturer of the operating system and is
> available to the product
> developer.
>
> 21(g) Applications shall not override user selected
> contrast and color
> selections and other individual display attributes.
>
> 21(j) When a product permits a user to adjust color
> and contrast settings, a
> variety of color selections capable of producing a
> range of contrast levels
> shall be provided.
>
>
> Group B: Requirements by content type
>
> 21(e) When bitmap images are used to identify
> controls, status indicators,
> or other programmatic elements, the meaning assigned
> to those images shall
> be consistent throughout an application's
> performance.
>
> 21(h) When animation is displayed, the information
> shall be displayable in
> at least one non-animated presentation mode at the
> option of the user.
>
> 21(i) Color coding shall not be used as the only
> means of conveying
> information, indicating an action, prompting a
> response, or distinguishing a
> visual element.
>
> 21(k) Software shall not use flashing or blinking
> text, objects, or other
> elements having a flash or blink frequency greater
> than 2 Hz and lower than
> 55 Hz.
>
> 22(j) Pages shall be designed to avoid causing the
> screen to flicker with a
> frequency greater than 2 Hz and lower than 55 Hz.
>
> 22(a) A text equivalent for every non-text element
> shall be provided (e.g.,
> via "alt", "longdesc", or in element content).
>
> 22(b) Equivalent alternatives for any multimedia
> presentation shall be
> synchronized with the presentation.
>
> 22(c) Web pages shall be designed so that all
> information conveyed with
> color is also available without color, for example
> from context or markup.
>
> 22(e) Redundant text links shall be provided for
> each active region of a
> server-side image map.
>
> 22(f) Client-side image maps shall be provided
> instead of server-side image
> maps except where the regions cannot be defined with
> an available geometric
> shape.
>
> 22(k) A text-only page, with equivalent information
> or functionality, shall
> be provided to make a web site comply with the
> provisions of this part, when
> compliance cannot be accomplished in any other way.
> The content of the
> text-only page shall be updated whenever the primary
> page changes.
>
> 22(p) When a timed response is required, the user
> shall be alerted and given
> sufficient time to indicate more time is required.
>
>
> Group C: Programmatic exposure of information:
>
> 21(c) A well-defined on-screen indication of the
> current focus shall be
> provided that moves among interactive interface
> elements as the input focus
> changes. The focus shall be programmatically exposed
> so that assistive
> technology can track focus and focus changes.
>
> 21(d) Sufficient information about a user interface
> element including the
> identity, operation and state of the element shall
> be available to assistive
> technology. When an image represents a program
> element, the information
> conveyed by the image must also be available in
> text.
>
> 21(f) Textual information shall be provided through
> operating system
> functions for displaying text. The minimum
> information that shall be made
> available is text content, text input caret
> location, and text attributes.
>
> 22(l) When pages utilize scripting languages to
> display content, or to
> create interface elements, the information provided
> by the script shall be
> identified with functional text that can be read by
> assistive technology.
>
> 22(m) When a web page requires that an applet,
> plug-in or other application
> be present on the client system to interpret page
> content, the page must
> provide a link to a plug-in or applet that complies
> with §1194.21(a) through
> (l).
>
>
> Group D: Correct coding
>
> 22(d) Documents shall be organized so they are
> readable without requiring an
> associated style sheet.
>
> 22(g) Row and column headers shall be identified for
> data tables.
>
> 22(h) Markup shall be used to associate data cells
> and header cells for data
> tables that have two or more logical levels of row
> or column headers.
>
> 22(i) Frames shall be titled with text that
> facilitates frame identification
> and navigation.
>
> 21(l) When electronic forms are used, the form shall
> allow people using
> assistive technology to access the information,
> field elements, and
> functionality required for completion and submission
> of the form, including
> all directions and cues.
>
=== message truncated ===
From: Roberto Scano - IWA/HWG
Date: Wed, Oct 11 2006 1:20 PM
Subject: Re: Grouping of the current 28software/webstandards
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Tamas
Babinszki
Sent: Wednesday, October 11, 2006 8:29 PM
To: = EMAIL ADDRESS REMOVED = ; TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Grouping of the current 28
software/webstandards
An other suggestion would be to group the standards
based on the principles of the WCAG 2.0 latest draft.
Even if we decide not to follow this structure, such
grouping could potentially bring us closer to
harmonization.
Roberto Scano:
Agree for this!
Roberto Scano ( = EMAIL ADDRESS REMOVED = )
IWA/HWG International Project Manager and EMEA Coordinator
International Webmasters Association / HTML Writers Guild
W3C Advisory Commitee Representative for IWA/HWG W3C
WCAG Working Group Member - W3C ATAG Working Group Member
Expert of ISO/TC 159/SC 4/WG 5 'Software ergonomics and human-computer
dialogues'
http://www.iwanet.org - http://www.hwg.org
E-Mail: = EMAIL ADDRESS REMOVED = - = EMAIL ADDRESS REMOVED =
Personal web site: http://www.robertoscano.info
From: Debbie Cook
Date: Wed, Oct 11 2006 1:45 PM
Subject: Re: Grouping of the current 28software/webstandards
Yes, for the reasons stated so far. And also because we need to merge these
standards insofar as it's reasonable to do so.
----- Original Message -----
From: "Tamas Babinszki" < = EMAIL ADDRESS REMOVED = >
To: < = EMAIL ADDRESS REMOVED = >; "TEITAC Web/Software Subcommittee"
< = EMAIL ADDRESS REMOVED = >
Sent: Wednesday, October 11, 2006 11:29 AM
Subject: Re: [teitac-websoftware] Grouping of the current 28
software/webstandards
An other suggestion would be to group the standards
based on the principles of the WCAG 2.0 latest draft.
Even if we decide not to follow this structure, such
grouping could potentially bring us closer to
harmonization.
Tamas Babinszki
--- Jim Thatcher < = EMAIL ADDRESS REMOVED = > wrote:
> All,
>
> I think the grouping of standards will be very
> helpful. I like Peter Korn's
> suggestion but have modified it somewhat. I find 4
> groups as indicated
> below. I think we will want to look at some web and
> software at the same
> time since the requirements are similar or identical
> - See "don't use color
> alone" as a prime example.
>
> We entered the EITAAC (previous Advisory Committee)
> effort for software with
> existing wording from Dept. Of Ed. and from IBM.
> That was a huge help. (The
> fact that the software committee was only 8 members
> was a help too.)
> Similarly, today we can bring in WCAG 2.0 and other
> guidelines addressing
> these issues.
>
> Can anyone provide a list of (recent) existing
> software guidelines?
>
> Jim
>
> Accessibility Consulting: http://jimthatcher.com/
> 512-306-0931
>
>
> Group A: Interaction and operating system
>
> 21(a) When software is designed to run on a system
> that has a keyboard,
> product functions shall be executable from a
> keyboard where the function
> itself or the result of performing a function can be
> discerned textually.
>
> 21(b) Applications shall not disrupt or disable
> activated features of other
> products that are identified as accessibility
> features, where those features
> are developed and documented according to industry
> standards. Applications
> also shall not disrupt or disable activated features
> of any operating system
> that are identified as accessibility features where
> the application
> programming interface for those accessibility
> features has been documented
> by the manufacturer of the operating system and is
> available to the product
> developer.
>
> 21(g) Applications shall not override user selected
> contrast and color
> selections and other individual display attributes.
>
> 21(j) When a product permits a user to adjust color
> and contrast settings, a
> variety of color selections capable of producing a
> range of contrast levels
> shall be provided.
>
>
> Group B: Requirements by content type
>
> 21(e) When bitmap images are used to identify
> controls, status indicators,
> or other programmatic elements, the meaning assigned
> to those images shall
> be consistent throughout an application's
> performance.
>
> 21(h) When animation is displayed, the information
> shall be displayable in
> at least one non-animated presentation mode at the
> option of the user.
>
> 21(i) Color coding shall not be used as the only
> means of conveying
> information, indicating an action, prompting a
> response, or distinguishing a
> visual element.
>
> 21(k) Software shall not use flashing or blinking
> text, objects, or other
> elements having a flash or blink frequency greater
> than 2 Hz and lower than
> 55 Hz.
>
> 22(j) Pages shall be designed to avoid causing the
> screen to flicker with a
> frequency greater than 2 Hz and lower than 55 Hz.
>
> 22(a) A text equivalent for every non-text element
> shall be provided (e.g.,
> via "alt", "longdesc", or in element content).
>
> 22(b) Equivalent alternatives for any multimedia
> presentation shall be
> synchronized with the presentation.
>
> 22(c) Web pages shall be designed so that all
> information conveyed with
> color is also available without color, for example
> from context or markup.
>
> 22(e) Redundant text links shall be provided for
> each active region of a
> server-side image map.
>
> 22(f) Client-side image maps shall be provided
> instead of server-side image
> maps except where the regions cannot be defined with
> an available geometric
> shape.
>
> 22(k) A text-only page, with equivalent information
> or functionality, shall
> be provided to make a web site comply with the
> provisions of this part, when
> compliance cannot be accomplished in any other way.
> The content of the
> text-only page shall be updated whenever the primary
> page changes.
>
> 22(p) When a timed response is required, the user
> shall be alerted and given
> sufficient time to indicate more time is required.
>
>
> Group C: Programmatic exposure of information:
>
> 21(c) A well-defined on-screen indication of the
> current focus shall be
> provided that moves among interactive interface
> elements as the input focus
> changes. The focus shall be programmatically exposed
> so that assistive
> technology can track focus and focus changes.
>
> 21(d) Sufficient information about a user interface
> element including the
> identity, operation and state of the element shall
> be available to assistive
> technology. When an image represents a program
> element, the information
> conveyed by the image must also be available in
> text.
>
> 21(f) Textual information shall be provided through
> operating system
> functions for displaying text. The minimum
> information that shall be made
> available is text content, text input caret
> location, and text attributes.
>
> 22(l) When pages utilize scripting languages to
> display content, or to
> create interface elements, the information provided
> by the script shall be
> identified with functional text that can be read by
> assistive technology.
>
> 22(m) When a web page requires that an applet,
> plug-in or other application
> be present on the client system to interpret page
> content, the page must
> provide a link to a plug-in or applet that complies
> with §1194.21(a) through
> (l).
>
>
> Group D: Correct coding
>
> 22(d) Documents shall be organized so they are
> readable without requiring an
> associated style sheet.
>
> 22(g) Row and column headers shall be identified for
> data tables.
>
> 22(h) Markup shall be used to associate data cells
> and header cells for data
> tables that have two or more logical levels of row
> or column headers.
>
> 22(i) Frames shall be titled with text that
> facilitates frame identification
> and navigation.
>
> 21(l) When electronic forms are used, the form shall
> allow people using
> assistive technology to access the information,
> field elements, and
> functionality required for completion and submission
> of the form, including
> all directions and cues.
>
=== message truncated ===
From: Barrett, Don
Date: Wed, Oct 11 2006 1:55 PM
Subject: Re: Grouping of the current28software/web standards
Esteemed Group,
Please let's not get caught up in the intellectual machinations of how to break the 28 standards into groups. The major purpose for doing this is only manageability in discussion; we are not forming new categories as I understand things. Whether we use Peter's, Richard's, Jim's, Jonathan's, doesn't matter so much as just picking some artificial scheme and using it to make our task manageable.
Am I missing something?
Don
_____
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Richard Schwerdtfeger
Sent: Wednesday, October 11, 2006 2:56 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Grouping of the current 28software/web standards
I agree. WCAG has been working on this for 4 years. This is a great starting point.
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
Tamas Babinszki < = EMAIL ADDRESS REMOVED = >
Tamas Babinszki < = EMAIL ADDRESS REMOVED = >
Sent by: = EMAIL ADDRESS REMOVED =
10/11/2006 01:29 PM
Please respond to
TEITAC Web/Software Subcommittee < = EMAIL ADDRESS REMOVED = >
To
= EMAIL ADDRESS REMOVED = , TEITAC Web/Software Subcommittee < = EMAIL ADDRESS REMOVED = >
cc
Subject
Re: [teitac-websoftware] Grouping of the current 28 software/web standards
An other suggestion would be to group the standards
based on the principles of the WCAG 2.0 latest draft.
Even if we decide not to follow this structure, such
grouping could potentially bring us closer to
harmonization.
Tamas Babinszki
--- Jim Thatcher < = EMAIL ADDRESS REMOVED = > wrote:
> All,
>
> I think the grouping of standards will be very
> helpful. I like Peter Korn's
> suggestion but have modified it somewhat. I find 4
> groups as indicated
> below. I think we will want to look at some web and
> software at the same
> time since the requirements are similar or identical
> - See "don't use color
> alone" as a prime example.
>
> We entered the EITAAC (previous Advisory Committee)
> effort for software with
> existing wording from Dept. Of Ed. and from IBM.
> That was a huge help. (The
> fact that the software committee was only 8 members
> was a help too.)
> Similarly, today we can bring in WCAG 2.0 and other
> guidelines addressing
> these issues.
>
> Can anyone provide a list of (recent) existing
> software guidelines?
>
> Jim
>
> Accessibility Consulting: http://jimthatcher.com/
> 512-306-0931
>
>
> Group A: Interaction and operating system
>
> 21(a) When software is designed to run on a system
> that has a keyboard,
> product functions shall be executable from a
> keyboard where the function
> itself or the result of performing a function can be
> discerned textually.
>
> 21(b) Applications shall not disrupt or disable
> activated features of other
> products that are identified as accessibility
> features, where those features
> are developed and documented according to industry
> standards. Applications
> also shall not disrupt or disable activated features
> of any operating system
> that are identified as accessibility features where
> the application
> programming interface for those accessibility
> features has been documented
> by the manufacturer of the operating system and is
> available to the product
> developer.
>
> 21(g) Applications shall not override user selected
> contrast and color
> selections and other individual display attributes.
>
> 21(j) When a product permits a user to adjust color
> and contrast settings, a
> variety of color selections capable of producing a
> range of contrast levels
> shall be provided.
>
>
> Group B: Requirements by content type
>
> 21(e) When bitmap images are used to identify
> controls, status indicators,
> or other programmatic elements, the meaning assigned
> to those images shall
> be consistent throughout an application's
> performance.
>
> 21(h) When animation is displayed, the information
> shall be displayable in
> at least one non-animated presentation mode at the
> option of the user.
>
> 21(i) Color coding shall not be used as the only
> means of conveying
> information, indicating an action, prompting a
> response, or distinguishing a
> visual element.
>
> 21(k) Software shall not use flashing or blinking
> text, objects, or other
> elements having a flash or blink frequency greater
> than 2 Hz and lower than
> 55 Hz.
>
> 22(j) Pages shall be designed to avoid causing the
> screen to flicker with a
> frequency greater than 2 Hz and lower than 55 Hz.
>
> 22(a) A text equivalent for every non-text element
> shall be provided (e.g.,
> via "alt", "longdesc", or in element content).
>
> 22(b) Equivalent alternatives for any multimedia
> presentation shall be
> synchronized with the presentation.
>
> 22(c) Web pages shall be designed so that all
> information conveyed with
> color is also available without color, for example
> from context or markup.
>
> 22(e) Redundant text links shall be provided for
> each active region of a
> server-side image map.
>
> 22(f) Client-side image maps shall be provided
> instead of server-side image
> maps except where the regions cannot be defined with
> an available geometric
> shape.
>
> 22(k) A text-only page, with equivalent information
> or functionality, shall
> be provided to make a web site comply with the
> provisions of this part, when
> compliance cannot be accomplished in any other way.
> The content of the
> text-only page shall be updated whenever the primary
> page changes.
>
> 22(p) When a timed response is required, the user
> shall be alerted and given
> sufficient time to indicate more time is required.
>
>
> Group C: Programmatic exposure of information:
>
> 21(c) A well-defined on-screen indication of the
> current focus shall be
> provided that moves among interactive interface
> elements as the input focus
> changes. The focus shall be programmatically exposed
> so that assistive
> technology can track focus and focus changes.
>
> 21(d) Sufficient information about a user interface
> element including the
> identity, operation and state of the element shall
> be available to assistive
> technology. When an image represents a program
> element, the information
> conveyed by the image must also be available in
> text.
>
> 21(f) Textual information shall be provided through
> operating system
> functions for displaying text. The minimum
> information that shall be made
> available is text content, text input caret
> location, and text attributes.
>
> 22(l) When pages utilize scripting languages to
> display content, or to
> create interface elements, the information provided
> by the script shall be
> identified with functional text that can be read by
> assistive technology.
>
> 22(m) When a web page requires that an applet,
> plug-in or other application
> be present on the client system to interpret page
> content, the page must
> provide a link to a plug-in or applet that complies
> with §1194.21(a) through
> (l).
>
>
> Group D: Correct coding
>
> 22(d) Documents shall be organized so they are
> readable without requiring an
> associated style sheet.
>
> 22(g) Row and column headers shall be identified for
> data tables.
>
> 22(h) Markup shall be used to associate data cells
> and header cells for data
> tables that have two or more logical levels of row
> or column headers.
>
> 22(i) Frames shall be titled with text that
> facilitates frame identification
> and navigation.
>
> 21(l) When electronic forms are used, the form shall
> allow people using
> assistive technology to access the information,
> field elements, and
> functionality required for completion and submission
> of the form, including
> all directions and cues.
>
=== message truncated ===
From: Andi Snow-Weaver
Date: Wed, Oct 11 2006 3:05 PM
Subject: Re: Grouping of thecurrent 28software/web standards
Don Barrett wrote:
>Please let's not get caught up in the intellectual machinations of how to
break the 28 standards into groups. The major purpose for doing this is
only manageability in discussion; we are not forming new categories as I
understand things. Whether we use Peter's, Richard's, Jim's, Jonathan's,
doesn't matter so much as just picking some artificial scheme and using it
to make our task manageable.
Am I missing something?
<end of Don's comments>
Don,
You are correct. The purpose of the grouping is simply to facilitate our
discussion of the existing provisions. I propose that we group them for our
discussion as Jim Thatcher last suggested [1].
To answer Jim's question about a list of standards, the JTC-1 Special
Working Group on Accessibility has just completed an inventory of standards
- both accessibility standards and standards that probably should include
accessibility provisions. It is a spreadsheet and is quite extensive. You
can download it at [2].
I would ask you all to hold off on getting into detailed discussions on the
provisions for a few more days. Before this list was available, I was
communicating with some early subcommittee members via a distribution list.
I have urged them all to subscribe to this list as I will stop using the
distribution list as of Monday, October 16th. So I would like to wait until
next week before we get into any more technical discussions to give them
all a chance to subscribe.
[1] http://teitac.org/mailarchives/mail_message.php?id=108&listid=3
[2] http://www.jtc1access.org/documents/swga_211.zip
Andi
From: Katie Haritos-Shea
Date: Wed, Oct 11 2006 3:05 PM
Subject: Re: Grouping of the current 28software/web standards
<HEAD>
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV>Don,</DIV>
<DIV> </DIV>
<DIV>It is just a good idea (certainly not the only one) that subject matter be split up into logical groups as you say. If those folks continue on past discussion to produce work items it is nice to have the 'like' information easy to grab.</DIV>
<DIV> </DIV>
<DIV>As one idea......WCAG 2.0 has four basic principles, it would be 'easier' for folks who know those issues and in the end to equate the two for later mappings. On the other hand, sometimes a fresh recipe doesn't hurt. </DIV>
<DIV> </DIV>
<DIV>Katie<BR><BR><BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 0px; BORDER-LEFT: #0000ff 2px solid">-----Original Message----- <BR>From: "Barrett, Don" < = EMAIL ADDRESS REMOVED = ><BR>Sent: Oct 11, 2006 3:50 PM <BR>To: TEITAC Web/Software Subcommittee < = EMAIL ADDRESS REMOVED = ><BR>Subject: Re: [teitac-websoftware] Grouping of the current 28software/web standards <BR><BR><ZZZHTML><ZZZHEAD><ZZZMETA content="text/html; charset=iso-8859-1" http-equiv="Content-Type"><ZZZMETA content="MSHTML 6.00.2900.2963" name="GENERATOR"></ZZZHEAD><ZZZBODY>
<DIV dir=ltr align=left><SPAN class=968424119-11102006><FONT face=Arial color=#0000ff size=2>Esteemed Group,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=968424119-11102006><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=968424119-11102006><FONT face=Arial color=#0000ff size=2>Please let's not get caught up in the intellectual machinations of how to break the 28 standards into groups. The major purpose for doing this is only manageability in discussion; we are not forming new categories as I understand things. Whether we use Peter's, Richard's, Jim's, Jonathan's, doesn't matter so much as just picking some artificial scheme and using it to make our task manageable.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=968424119-11102006><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=968424119-11102006><FONT face=Arial color=#0000ff size=2>Am I missing something?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=968424119-11102006><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=968424119-11102006><FONT face=Arial color=#0000ff size=2>Don</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=968424119-11102006></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] <B>On Behalf Of </B>Richard Schwerdtfeger<BR><B>Sent:</B> Wednesday, October 11, 2006 2:56 PM<BR><B>To:</B> TEITAC Web/Software Subcommittee<BR><B>Subject:</B> Re: [teitac-websoftware] Grouping of the current 28software/web standards<BR></FONT><BR></DIV>
<DIV></DIV>
<P>I agree. WCAG has been working on this for 4 years. This is a great starting point.<BR><BR><BR>Rich Schwerdtfeger<BR>Distinguished Engineer, SWG Accessibility Architect/Strategist<BR>Chair, IBM Accessibility Architecture Review Board<BR>blog: <A href="http://www.ibm.com/developerworks/blogs/page/schwer">http://www.ibm.com/developerworks/blogs/page/schwer</A><BR><IMG height=16 alt="Inactive hide details for Tamas Babinszki < = EMAIL ADDRESS REMOVED = >" src="cid:968424119@11102006-0EA7" width=16 border=0>Tamas Babinszki < = EMAIL ADDRESS REMOVED = ><BR><BR><BR>
<TABLE cellSpacing=0 cellPadding=0 width="100%" border=0>
<TBODY>
<TR vAlign=top>
<TD style="BACKGROUND-IMAGE: url(cid:2__= = EMAIL ADDRESS REMOVED = ); BACKGROUND-REPEAT: no-repeat" width="40%">
<UL>
<UL>
<UL>
<UL><B><FONT size=2>Tamas Babinszki < = EMAIL ADDRESS REMOVED = ></FONT></B><FONT size=2> </FONT><BR><FONT size=2>Sent by: = EMAIL ADDRESS REMOVED = </FONT>
<P><FONT size=2>10/11/2006 01:29 PM</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD width=168 bgColor=#ffffff>
<DIV align=center><FONT size=2>Please respond to<BR>TEITAC Web/Software Subcommittee < = EMAIL ADDRESS REMOVED = ></FONT></DIV></TD></TR></TBODY></TABLE></P></UL></UL></UL></UL></TD>
<TD width="60%">
<TABLE cellSpacing=0 cellPadding=0 width="100%" border=0>
<TBODY>
<TR vAlign=top>
<TD width="1%"><IMG height=1 alt="" src="cid:968424119@11102006-0EAE" width=58 border=0><BR>
<DIV align=right><FONT size=2>To</FONT></DIV></TD>
<TD width="100%"><IMG height=1 alt="" src="cid:968424119@11102006-0EAE" width=1 border=0><BR><FONT size=2> = EMAIL ADDRESS REMOVED = , TEITAC Web/Software Subcommittee < = EMAIL ADDRESS REMOVED = ></FONT></TD></TR>
<TR vAlign=top>
<TD width="1%"><IMG height=1 alt="" src="cid:968424119@11102006-0EAE" width=58 border=0><BR>
<DIV align=right><FONT size=2>cc</FONT></DIV></TD>
<TD width="100%"><IMG height=1 alt="" src="cid:968424119@11102006-0EAE" width=1 border=0><BR></TD></TR>
<TR vAlign=top>
<TD width="1%"><IMG height=1 alt="" src="cid:968424119@11102006-0EAE" width=58 border=0><BR>
<DIV align=right><FONT size=2>Subject</FONT></DIV></TD>
<TD width="100%"><IMG height=1 alt="" src="cid:968424119@11102006-0EAE" width=1 border=0><BR><FONT size=2>Re: [teitac-websoftware] Grouping of the current 28 software/web standards</FONT></TD></TR></TBODY></TABLE>
<TABLE cellSpacing=0 cellPadding=0 border=0>
<TBODY>
<TR vAlign=top>
<TD width=58><IMG height=1 alt="" src="cid:968424119@11102006-0EAE" width=1 border=0></TD>
<TD width=336><IMG height=1 alt="" src="cid:968424119@11102006-0EAE" width=1 border=0></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE><BR><TT>An other suggestion would be to group the standards<BR>based on the principles of the WCAG 2.0 latest draft.<BR>Even if we decide not to follow this structure, such<BR>grouping could potentially bring us closer to<BR>harmonization.<BR><BR>Tamas Babinszki<BR><BR>--- Jim Thatcher < = EMAIL ADDRESS REMOVED = > wrote:<BR><BR>> All,<BR>> <BR>> I think the grouping of standards will be very<BR>> helpful. I like Peter Korn's<BR>> suggestion but have modified it somewhat. I find 4<BR>> groups as indicated<BR>> below. I think we will want to look at some web and<BR>> software at the same<BR>> time since the requirements are similar or identical<BR>> - See "don't use color<BR>> alone" as a prime example.<BR>> <BR>> We entered the EITAAC (previous Advisory Committee)<BR>> effort for software with<BR>> existing wording from Dept. Of Ed. and from IBM.<BR>> That was a huge help. (The<BR>> fact that the software committee was only 8 members<BR>> was a help too.)<BR>> Similarly, today we can bring in WCAG 2.0 and other<BR>> guidelines addressing<BR>> these issues.<BR>> <BR>> Can anyone provide a list of (recent) existing<BR>> software guidelines?<BR>> <BR>> Jim<BR>> <BR>> Accessibility Consulting: </TT><TT><A href="http://jimthatcher.com/">http://jimthatcher.com/</A></TT><TT><BR>> 512-306-0931<BR>> <BR>> <BR>> Group A: Interaction and operating system<BR>> <BR>> 21(a) When software is designed to run on a system<BR>> that has a keyboard,<BR>> product functions shall be executable from a<BR>> keyboard where the function<BR>> itself or the result of performing a function can be<BR>> discerned textually.<BR>> <BR>> 21(b) Applications shall not disrupt or disable<BR>> activated features of other<BR>> products that are identified as accessibility<BR>> features, where those features<BR>> are developed and documented according to industry<BR>> standards. Applications<BR>> also shall not disrupt or disable activated features<BR>> of any operating system<BR>> that are identified as accessibility features where<BR>> the application<BR>> programming interface for those accessibility<BR>> features has been documented<BR>> by the manufacturer of the operating system and is<BR>> available to the product<BR>> developer.<BR>> <BR>> 21(g) Applications shall not override user selected<BR>> contrast and color<BR>> selections and other individual display attributes.<BR>> <BR>> 21(j) When a product permits a user to adjust color<BR>> and contrast settings, a<BR>> variety of color selections capable of producing a<BR>> range of contrast levels<BR>> shall be provided.<BR>> <BR>> <BR>> Group B: Requirements by content type<BR>> <BR>> 21(e) When bitmap images are used to identify<BR>> controls, status indicators,<BR>> or other programmatic elements, the meaning assigned<BR>> to those images shall<BR>> be consistent throughout an application's<BR>> performance.<BR>> <BR>> 21(h) When animation is displayed, the information<BR>> shall be displayable in<BR>> at least one non-animated presentation mode at the<BR>> option of the user.<BR>> <BR>> 21(i) Color coding shall not be used as the only<BR>> means of conveying<BR>> information, indicating an action, prompting a<BR>> response, or distinguishing a<BR>> visual element.<BR>> <BR>> 21(k) Software shall not use flashing or blinking<BR>> text, objects, or other<BR>> elements having a flash or blink frequency greater<BR>> than 2 Hz and lower than<BR>> 55 Hz.<BR>> <BR>> 22(j) Pages shall be designed to avoid causing the<BR>> screen to flicker with a<BR>> frequency greater than 2 Hz and lower than 55 Hz.<BR>> <BR>> 22(a) A text equivalent for every non-text element<BR>> shall be provided (e.g.,<BR>> via "alt", "longdesc", or in element content).<BR>> <BR>> 22(b) Equivalent alternatives for any multimedia<BR>> presentation shall be<BR>> synchronized with the presentation.<BR>> <BR>> 22(c) Web pages shall be designed so that all<BR>> information conveyed with<BR>> color is also available without color, for example<BR>> from context or markup.<BR>> <BR>> 22(e) Redundant text links shall be provided for<BR>> each active region of a<BR>> server-side image map.<BR>> <BR>> 22(f) Client-side image maps shall be provided<BR>> instead of server-side image<BR>> maps except where the regions cannot be defined with<BR>> an available geometric<BR>> shape.<BR>> <BR>> 22(k) A text-only page, with equivalent information<BR>> or functionality, shall<BR>> be provided to make a web site comply with the<BR>> provisions of this part, when<BR>> compliance cannot be accomplished in any other way.<BR>> The content of the<BR>> text-only page shall be updated whenever the primary<BR>> page changes.<BR>> <BR>> 22(p) When a timed response is required, the user<BR>> shall be alerted and given<BR>> sufficient time to indicate more time is required.<BR>> <BR>> <BR>> Group C: Programmatic exposure of information:<BR>> <BR>> 21(c) A well-defined on-screen indication of the<BR>> current focus shall be<BR>> provided that moves among interactive interface<BR>> elements as the input focus<BR>> changes. The focus shall be programmatically exposed<BR>> so that assistive<BR>> technology can track focus and focus changes.<BR>> <BR>> 21(d) Sufficient information about a user interface<BR>> element including the<BR>> identity, operation and state of the element shall<BR>> be available to assistive<BR>> technology. When an image represents a program<BR>> element, the information<BR>> conveyed by the image must also be available in<BR>> text.<BR>> <BR>> 21(f) Textual information shall be provided through<BR>> operating system<BR>> functions for displaying text. The minimum<BR>> information that shall be made<BR>> available is text content, text input caret<BR>> location, and text attributes.<BR>> <BR>> 22(l) When pages utilize scripting languages to<BR>> display content, or to<BR>> create interface elements, the information provided<BR>> by the script shall be<BR>> identified with functional text that can be read by<BR>> assistive technology.<BR>> <BR>> 22(m) When a web page requires that an applet,<BR>> plug-in or other application<BR>> be present on the client system to interpret page<BR>> content, the page must<BR>> provide a link to a plug-in or applet that complies<BR>> with §1194.21(a) through<BR>> (l).<BR>> <BR>> <BR>> Group D: Correct coding<BR>> <BR>> 22(d) Documents shall be organized so they are<BR>> readable without requiring an<BR>> associated style sheet.<BR>> <BR>> 22(g) Row and column headers shall be identified for<BR>> data tables.<BR>> <BR>> 22(h) Markup shall be used to associate data cells<BR>> and header cells for data<BR>> tables that have two or more logical levels of row<BR>> or column headers.<BR>> <BR>> 22(i) Frames shall be titled with text that<BR>> facilitates frame identification<BR>> and navigation.<BR>> <BR>> 21(l) When electronic forms are used, the form shall<BR>> allow people using<BR>> assistive technology to access the information,<BR>> field elements, and<BR>> functionality required for completion and submission<BR>> of the form, including<BR>> all directions and cues.<BR>> <BR>=== message truncated ===<BR><BR>
WebAIM is an initiative of:
