Avaya Accessibility Conformance Report

3y ago
35 Views
2 Downloads
423.51 KB
17 Pages
Last View : 2m ago
Last Download : 3m ago
Upload by : Gia Hauser
Transcription

Avaya Accessibility Conformance ReportVPAT Version 2.1 – March 2018Name of Product/Version: Avaya G430 Branch Gateway, Release 8.1Product Description: The Avaya G430 Branch Gateway is a multipurpose media gateway that can support up to 150 users when deployed asa Branch Gateway in a mid-to-large branch office of a large enterprise or a call center. This requires Avaya Aura Communication Manager software running onone or more Avaya servers.Date: June 2019Contact information: huh@avaya.comNotes:The Avaya G430 Branch Gateway Release 8.1 does not have any Web-based access.The Avaya G430 Branch Gateway command line interface is accessed via terminal emulation software that resides on the administrator’s desktop computer. Theconformance statements in this document assume that the terminal emulation software is fully conformant with the statutory requirements of Section 508.The statements in this document refer only to the text-based command line interface used to administer the Standard Local Survivability (SLS) feature. The SLSfeature provides basic telephone services in the event that the connection with the primary External Call Controller (ECC) is lost and there are no survivableservers configured with this branch gateway.Service personnel and system administrators who require the support of assistive technologies may be unable to perform the initial installation, system setupand upgrades of the Avaya G430 Branch Gateway.Evaluation Methods Used: Testing is based on general product knowledgeApplicable Standards/Guidelines“Voluntary Product Accessibility Template” and “VPAT” are registeredservice marks of the Information Technology Industry Council (ITI)Page 1 of 17

This report covers the degree of conformance for the following accessibility standard/guidelines:Standard/GuidelineRevised Section 508 standards as published by the U.S. Access Board in the FederalRegister on January 18, 2017Corrections to the ICT Final Rule as published by the US Access Board in the FederalRegister on January 22, 2018Included In ReportYesTermsThe terms used in the Conformance Level information are defined as follows: Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets withequivalent facilitation.Supports with Exceptions: Some functionality of the product does not meet the criterion.Does Not Support: The majority of product functionality does not meet the criterion.Not Applicable: The criterion is not relevant to the product.Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.2017 Section 508 ReportNotes:Chapter 3: Functional Performance Criteria (FPC)Notes: The Avaya G430 Branch Gateway command line interface is accessed via a terminal emulation software that resides on the administrator’s desktopcomputer. The conformance statements in this document assumes that the terminal emulation software is fully conformant with the statutory requirements ofSection 508.Criteria302.1 Without Vision. Where a visual mode of operation is provided,ICT shall provide at least one mode of operation that does not requireConformance LevelDoes Not SupportPage 2 of 17Remarks and ExplanationsThe Avaya G430 Branch Gatewaycommand line interface is accessed via

user vision.Criteria302.2 With Limited Vision. Where a visual mode of operation isprovided, ICT shall provide at least one mode of operation that enablesusers to make use of limited vision.Conformance LevelSupports302.3 Without Perception of Color. Where a visual mode ofoperation is provided, ICT shall provide at least one visual mode ofoperation that does not require user perception of color.Supports302.4 Without Hearing. Where an audible mode of operation isprovided, ICT shall provide at least one mode of operation that does notrequire user hearing.Supports302.5 With Limited Hearing. Where an audible mode of operation isprovided, ICT shall provide at least one mode of operation that enablesusers to make use of limited hearing.Supports302.6 Without Speech. Where speech is used for input, control, oroperation, ICT shall provide at least one mode of operation that doesnot require user speech.Supports302.7 With Limited Manipulation. Where a manual mode ofoperation is provided, ICT shall provide at least one mode of operationthat does not require fine motor control or simultaneous manualoperations.Supports302.8 With Limited Reach and Strength. Where a manual mode ofoperation is provided, ICT shall provide at least one mode of operationthat is operable with limited reach and limited strength.Supports302.9 With Limited Language, Cognitive, and Learning Abilities.ICT shall provide features making its use by individuals with limitedcognitive, language, and learning abilities simpler and easier.SupportsPage 3 of 17Remarks and Explanationsterminal emulation software that resideson the user’s desktop computer. Screenreading technology may not work in thisenvironment.The Avaya G430 Branch Gatewaycommand line administrative interface istext-only. The ability to change the size,color, and font of the text is dependent onthe administrator’s terminal emulationsoftware.The Avaya G430 Branch Gatewaycommand line administrative interfacedoes not use color coding.The Avaya G430 Branch Gatewaycommand line administrative interfacedoes not have an audio component.The Avaya G430 Branch Gatewaycommand line administrative interfacedoes not have an audio component.No mode of operation or informationretrieval in the Avaya G430 BranchGateway requires user speech.No mode of operation or informationretrieval in the Avaya G430 BranchGateway requires fine motor control orsimultaneous actions.Operability with limited reach andstrength is dependent on the user’sterminal.The Avaya G430 Branch Gateway StandardLocal Survivability (SLS) administrationrequires understanding of the SLSadministration as described in the AvayaG430 Branch Gateway CLI Referencedocument.

Page 4 of 17

Chapter 4: HardwareNotes: The Avaya G430 Branch Gateway command line interface is accessed via a terminal emulation software that resides on the administrator’s desktopcomputer. The conformance statements in this document assumes that the terminal emulation software is fully conformant with the statutory requirements ofSection 508. Service personnel and system administrators who require the support of assistive technologies may be unable to perform the initial installation,system setup and upgrades of the Avaya G430 Branch Gateway.402 Closed Functionality402.1 General402.2 Speech-Output EnabledCriteriaConformance LevelHeading cell – no response requiredHeading cell – no response requiredHeading cell – no response required402.2.1 Information Displayed On-Screen. Speech output shall beprovided for all information displayed on-screen.Not Applicable402.2.2 Transactional Outputs. Where transactional outputs areprovided, the speech output shall audibly provide all informationnecessary to verify a transaction.Not Applicable402.2.3 Speech Delivery Type and Coordination. Speech outputshall be delivered through a mechanism that is readily available to allusers, including, but not limited to, an industry standard connector or atelephone handset. Speech shall be recorded or digitized human, orsynthesized. Speech output shall be coordinated with informationdisplayed on the screen.Not Applicable402.2.4 User Control. Speech output for any single function shall beautomatically interrupted when a transaction is selected. Speech outputshall be capable of being repeated and paused.Not Applicable402.2.5 Braille Instructions. Where speech output is required by402.2, braille instructions for initiating the speech mode of operationshall be provided. Braille shall be contracted and shall conform to 36CFR Part 1191, Appendix D, Section 703.3.1.Remarks and ExplanationsHeading cell – no response requiredHeading cell – no response requiredHeading cell – no response requiredNot ApplicableEXCEPTION: Devices for personal use shall not be required to conformto 402.2.5.402.3 VolumeHeading cell – no response required402.3.1 Private Listening. Where ICT provides private listening, itshall provide a mode of operation for controlling the volume. Where ICTNot ApplicablePage 5 of 17Heading cell – no response required

CriteriaConformance Leveldelivers output by an audio transducer typically held up to the ear, ameans for effective magnetic wireless coupling to hearing technologiesshall be provided.402.3.2 Non-private Listening. Where ICT provides non-privatelistening, incremental volume control shall be provided with outputamplification up to a level of at least 65 dB. A function shall be providedto automatically reset the volume to the default level after every use.Not Applicable402.4 Characters on Display Screens. At least one mode ofcharacters displayed on the screen shall be in a sans serif font. WhereICT does not provide a screen enlargement feature, characters shall be3/16 inch (4.8 mm) high minimum based on the uppercase letter “I”.Characters shall contrast with their background with either lightcharacters on a dark background or dark characters on a lightbackground.Not Applicable402.5 Characters on Variable Message Signs. Characters onvariable message signs shall conform to section 703.7 Variable MessageSigns of ICC A117.1-2009 (incorporated by reference, see 702.6.1).Not Applicable403 BiometricsHeading cell – no response requiredRemarks and ExplanationsHeading cell – no response required403.1 General. Where provided, biometrics shall not be the onlymeans for user identification or control.EXCEPTION: Where at least two biometric options that use differentbiological characteristics are provided, ICT shall be permitted to usebiometrics as the only means for user identification or control.Not Applicable404 Preservation of Information Provided for AccessibilityHeading cell – no response required404.1 General. ICT that transmits or converts information orcommunication shall not remove non-proprietary information providedfor accessibility or shall restore it upon delivery.SupportsPage 6 of 17Heading cell – no response requiredAll information and communication that istransmitted reliably on the Public SwitchedTelephone Network (PSTN) can betransmitted reliably via The Avaya G430Branch Gateway. NOTE: VoIP networkscommonly support a variety of audioencoding techniques. Some of these donot provide reliable support for assistivecommunication technologies that rely onnon-voice audio transmissions. Forexample, the accuracy of TTY

CriteriaConformance Level405 PrivacyHeading cell – no response required405.1 General. The same degree of privacy of input and output shallbe provided to all individuals. When speech output required by 402.2 isenabled, the screen shall not blank automatically.Not Applicable406 Standard ConnectionsHeading cell – no response required406.1 General. Where data connections used for input and output areprovided, at least one of each type of connection shall conform toindustry standard non-proprietary formats.Supports407 Operable PartsHeading cell – no response required407.2 Contrast. Where provided, keys and controls shall contrastvisually from background surfaces. Characters and symbols shallcontrast visually from background surfaces with either light charactersor symbols on a dark background or dark characters or symbols on alight background.Not Applicable407.3 Input ControlsHeading cell – no response required407.3.1 Tactilely Discernible. Input controls shall be operable bytouch and tactilely discernible without activation.Not Applicable407.3.2 Alphabetic Keys. Where provided, individual alphabetic keysshall be arranged in a QWERTY-based keyboard layout and the “F” and“J” keys shall be tactilely distinct from the other keys.Not Applicable407.3.3 Numeric Keys. Where provided, numeric keys shall bearranged in a 12-key ascending or descending keypad layout. Thenumber five key shall be tactilely distinct from the other keys. Wherethe ICT provides an alphabetic overlay on numeric keys, therelationships between letters and digits shall conform to ITU-TRecommendation E.161 (incorporated by reference, see 702.7.1).Not Applicable407.4 Key Repeat. Where a keyboard with key repeat is provided, thedelay before the key repeat feature is activated shall be fixed at, oradjustable to, 2 seconds minimum.Not ApplicablePage 7 of 17Remarks and Explanationstransmissions is not assured if the signalsare not digitally encoded in the mannerspecified by ITU-T Recommendation G.711.For this reason, conformance to thiscriterion may require the systemadministrator to enable or disable some ofthe available encoding options.Heading cell – no response requiredHeading cell – no response requiredAll Avaya G430 Branch Gateway input andoutput data connections conform toindustry standard non-proprietary formats.Heading cell – no response requiredHeading cell – no response required

CriteriaConformance Level407.5 Timed Response. Where a timed response is required, the usershall be alerted visually, as well as by touch or sound, and shall begiven the opportunity to indicate that more time is needed.Not Applicable407.6 Operation. At least one mode of operation shall be operablewith one hand and shall not require tight grasping, pinching, or twistingof the wrist. The force required to activate operable parts shall be 5pounds (22.2 N) maximum.Not Applicable407.7 Tickets, Fare Cards, and Keycards. Where tickets, fare cards,or keycards are provided, they shall have an orientation that is tactilelydiscernible if orientation is important to further use of the ticket, farecard, or keycard.Not Applicable407.8 Reach Height and DepthHeading cell – no response required407.8.1 Vertical Reference Plane. Operable parts shall be positionedfor a side reach or a forward reach determined with respect to a verticalreference plane. The vertical reference plane shall be located inconformance to 407.8.2 or 407.8.3.Not Applicable407.8.1.1 Vertical Plane for Side Reach. Where a side reach isprovided, the vertical reference plane shall be 48 inches (1220 mm)long minimum.Not Applicable407.8.1.2 Vertical Plane for Forward Reach. Where a forward reachis provided, the vertical reference plane shall be 30 inches (760 mm)long minimum.Not Applicable407.8.2 Side Reach. Operable parts of ICT providing a side reach shallconform to 407.8.2.1 or 407.8.2.2. The vertical reference plane shall becentered on the operable part and placed at the leading edge of themaximum protrusion of the ICT within the length of the verticalreference plane. Where a side reach requires a reach over a portion ofthe ICT, the height of that portion of the ICT shall be 34 inches (865mm) maximum.Not Applicable407.8.2.1 Unobstructed Side Reach. Where the operable part islocated 10 inches (255 mm) or less beyond the vertical reference plane,the operable part shall be 48 inches (1220 mm) high maximum and 15inches (380 mm) high minimum above the floor.Not Applicable407.8.2.2 Obstructed Side Reach. Where the operable part is locatedmore than 10 inches (255 mm), but not more than 24 inches (610 mm),Not Applicablebeyond the vertical reference plane, the height of the operable part shallbe 46 inches (1170 mm) high maximum and 15 inches (380 mm) highPage 8 of 17Remarks and ExplanationsHeading cell – no response required

Criteriaminimum above the floor. The operable part shall not be located morethan 24 inches (610 mm) beyond the vertical reference plane.407.8.3 Forward Reach. Operable parts of ICT providing a forwardreach shall conform to 407.8.3.1 or 407.8.3.2. The vertical referenceplane shall be centered, and intersect with, the operable part. Where aforward reach allows a reach over a portion of the ICT, the height ofthat portion of the ICT shall be 34 inches (865 mm) maximum.Conformance LevelNot Applicable407.8.3.1 Unobstructed Forward Reach. Where the operable part islocated at the leading edge of the maximum protrusion within the lengthof the vertical reference plane of the ICT, the operable part shall be 48 Not Applicableinches (1220 mm) high maximum and 15 inches (380 mm) highminimum above the floor.407.8.3.2 Obstructed Forward Reach. Where the operable part islocated beyond the leading edge of the maximum protrusion within thelength of the vertical reference plane, the operable part shall conform to407.8.3.2. The maximum allowable forward reach to an operable partshall be 25 inches (635 mm).Not Applicable407.8.3.2.1 Operable Part Height for ICT with ObstructedForward Reach.If the reach depth is less than 20 inches (510 mm),the operable part height shall be 48 inches (1220 mm) maximum. Ifthe reach depth is 20 inches (510 mm) to 25 inches (635 mm), theoperable part height shall be 44 inches (1120 mm) maximum.Not Applicable407.8.3.2.2 Knee and Toe Space under ICT with ObstructedForward Reach. Knee and toe space under ICT shall be 27 inches(685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30inches (760 mm) wide minimum and shall be clear of obstructions.EXCEPTIONS:1. Toe space shall be permitted to provide a clear height of 9 inches(230 mm) minimum above the floor and a clear depth of 6 inches (150mm) maximum from the vertical reference plane toward the leadingedge of the ICT.Not Applicable2. At a depth of 6 inches (150 mm) maximum from the verticalreference plane toward the leading edge of the ICT, space between 9inches (230 mm) and 27 inches (685 mm) minimum above the floorshall be permitted to reduce at a rate of 1 inch (25 mm) in depth forevery 6 inches (150 mm) in height.Page 9 of 17Remarks and Explanations

408 Display ScreensCriteriaConformance LevelHeading cell – no response required408.2 Visibility. Where stationary ICT provides one or more displayscreens, at least one of each type of display screen shall be visible froma point located 40 inches (1015 mm) above the floor space where thedisplay screen is viewed.Remarks and ExplanationsHeading cell – no response requiredNot Applicable408.3 Flashing. Where ICT emits lights in flashes, there shall be nomore than three flashes in any one-second period.EXCEPTION: Flashes that do not exceed the general flash and red flashthresholds defined in WCAG 2.0 (incorporated by reference, see702.10.1) are not required to conform to 408.3.Not Applicable409 Status IndicatorsHeading cell – no response required409.1 General. Where provided, status indicators shall be discerniblevisually and by touch or sound.Not Applicable410 Color CodingHeading cell – no response required410.1 General. Where provided, color coding shall not be used as theonly means of conveying information, indicating an action, prompting aresponse, or distinguishing a visual element.Not Applicable411 Audible SignalsHeading cell – no response required411.1 General. Where provided, audible signals or cues shall not beused as the only means of conveying information, indicating an action,or prompting a responseNot Applicable412 ICT with Two-Way Voice Communication412.2 Volume GainHeading cell – no response requiredHeading cell – no response required412.2.1 Volume Gain for Wireline Telephones. Volume gainconforming to 47 CFR 68.317 shall be provided on analog and digitalwireline telephones.Not Applicable412.2.2 Volume Gain for Non-Wireline ICT. A method forincreasing volume shall be provided for non-wireline ICT.Not Applicable412.3 Interference Reduction and Magnetic CouplingHeading cell – no response required412.3.1 Wireless Handsets. ICT in the form of wireless handsets shallconform to ANSI/IEEE C63.19-2011 (incorporated by reference, see702.5.1)Not Applicable412.3.2 Wireline Handsets. ICT in the form of wireline handsets,including cordless handsets, shall conform to TIA-1083-B (incorporatedby reference, see702.9.1).Not ApplicablePage 10 of 17Heading cell – no response requiredHeading cell – no response requiredThe Avaya G430 Branch Gatewaycommand line administrative interfacedoes not use color coding.Hea

The Avaya G430 Branch Gateway is a multipurpose media gateway that can support up to 150 users when deployed as a Branch Gateway in a mid-to-large branch office of a large enterprise or a call center. This requires Avaya Aura Communication Manager software running on one or more Avaya servers. Date: June 2019. Contact information: huh@avaya.com

Related Documents:

Avaya 4610SW IP Telephone (SIP) Avaya 4620SW IP Telephones (SIP) SIP version 2.2.2 Avaya 9620 IP Telephones (H.323) Avaya one-X Deskphone Edition 1.5 Avaya 9620 IP Telephones (SIP) Avaya 9630 IP Telephones (SIP) Avaya one-X Deskphone Edition SIP 2.0.3 Avaya one-X Desktop Edition (SIP) 2.1 Service Pack 2 Avaya 6408D Digital Telephone - Avaya .

Avaya Avaya Aura Session Manager 7.0.0.0.700007 Avaya Aura System Manager 7.0.0.0.16266 Avaya Aura Communication Manager 7.0-441 Build 0.22477 Avaya Session Border Controller for Enterprise 7.-21-6602 Avaya G430 Media Gateway 37.19. Avaya 96x0 Phone (SIP) 2_6_14_5 Avaya 9608 Phone (SIP) 7.0.0 R39 Avaya 96x0 Phone (H.323) 3.230A

Avaya PARTNER Advanced Communications System Avaya MERLIN MAGIX Avaya IP Office Avaya S8100 Media Server on Avaya G600 Media Gateway or CMC1 Gateway Avaya S8300 Media Server and an Avaya G700 Media Gateway Market Segment Small to Mid Stand Alone or Small of Large 2-48 stations Small/mid standalone Target 20-80 station size

avaya ip office Video Softphone aCm ip Softphone avaya ip agent avaya one-x Communicator avaya Communicator 2.1 avaya Communicator for microsoft lync 6.4.0.2 avaya one-x agent avaya aura agent desktop e169 media Station i2050 softphone Flare experience H175 Video phone 2 linK o

Avaya S8300 Server with Avaya G700 Media Gateway Avaya Communication Manger 4.0 (R014x.00.0.730.5) Avaya 9650 IP Telephone Avaya one-X Deskphone Edition 1.5 (H.323) Avaya 9640G IP Telephone Avaya one-X Deskphone Edition 1.5 (H.323) Avaya 9640 IP Telephone

Avaya IP Office solution A vaya IP Office 500 V2 Embedded Voicemail Avaya Web RTC Gateway Avaya one -X Portal Avaya IP Office Manager Avaya IP Office Analogue PHONE 8 Avaya IP Office VCM64/PRID U Avaya IP Office DIG DCPx16 V2 10.0.0.1.0 build 53 10.0.0.1.0 build 53 10.0.0.1.0 bui ld 3

from Avaya to install and configure Avaya components. Configure the CTI Link on the Avaya CM A CTI Link (also known as a T-Link) between the Avaya Communication Manager and AES is required for communication of events via TSAPI. The Avaya CM can be configured via the Avaya Site Administration tool (GEDI) or through a telnet session.

https://support.avaya.com for more details about the versions supported by Avaya. 3.1 Avaya IP Office IPBX AVAYA IP OFFICE IPBX – software versions Reference product Software version Certification : Certified NS : No supported Certified "Loads" Restrictions Avaya 11.0 FP4 11.0.4.0 build 74 AVAYA IP Office