Thread Subject: Group A: 21(b) Interference with accessibilityfeatures
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: Andi Snow-Weaver
Date: Thu, Oct 19 2006 9:20 AM
Subject: Group A: 21(b) Interference with accessibilityfeatures
Current Section 508 wording:
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.
In ISO 9241 Part 171, this is addressed as:
Software shall not disable or interfere with the accessibility features of
the operating system and software that provide services for use by other
software or any other applications.
The ISO spec also includes a provision for accessibility shortcut key
assignments, specifically five consecutive clicks of the shift key and
holding the shift key down for 8 seconds. It also notes that platform
software may reserve additional shortcut keys.
My view (not speaking as co-chair here) is that reserving the shortcut key
assignments is already required by the current 508 provision and the first
ISO one above. If you use the shortcut keys that are being used to activate
accessibility features, you are interfering with them.
Andi
From: Brett, Thomas F
Date: Thu, Oct 19 2006 9:55 AM
Subject: Re: Group A: 21(b) Interference withaccessibilityfeatures
"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."
This standard has always made me a bit hesitant. The operating system
today may have 10 accessibility features but tomorrow has 25 features.
Tom Brett,
Section 508 Coordinator
US Office of Personnel Management
Rm 6H34A
2026061206 (v)
2026062582 (tty)
Disabled does not mean Unable
= EMAIL ADDRESS REMOVED =
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Thursday, October 19, 2006 11:18 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] Group A: 21(b) Interference with
accessibilityfeatures
Current Section 508 wording:
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.
In ISO 9241 Part 171, this is addressed as:
Software shall not disable or interfere with the accessibility features
of
the operating system and software that provide services for use by other
software or any other applications.
The ISO spec also includes a provision for accessibility shortcut key
assignments, specifically five consecutive clicks of the shift key and
holding the shift key down for 8 seconds. It also notes that platform
software may reserve additional shortcut keys.
My view (not speaking as co-chair here) is that reserving the shortcut
key
assignments is already required by the current 508 provision and the
first
ISO one above. If you use the shortcut keys that are being used to
activate
accessibility features, you are interfering with them.
Andi
WebAIM is an initiative of:
