EN 301 549 Report**

For consistency and ease of reference with the VPAT for the user agent / subject-to-policies mode of Privilege Manager, these criteria are included.

Chapter4: Functional Performance Statements(FPS)

Notes:

Criteria Conformance Level Remarks and Explanations
4.2.1 Usage without vision Partially Supports See “Known Issues” section of document
4.2.2 Usage with limited vision Supports
4.2.3 Usage without perception of colour Partially Supports See “Known Issues” section of document
4.2.4 Usage without hearing Supports
4.2.5 Usage with limited hearing Supports
4.2.6 Usage with no or limited vocal capability Supports
4.2.7 Usage with limited manipulation or strength Supports
4.2.8 Usage with limited reach Supports
4.2.9 Minimize photosensitive seizure triggers Supports, See Note See “Known Issues” section of document
4.2.10 Usage with limited cognition, language or learning Partially Supports See “Known Issues” section of document
4.2.11 Privacy Supports

Chapter5: Generic Requirements

The user agent of Privilege Manager is not a closed system; this chapter does not apply.

Not Applicable
Criteria Conformance Level Remarks and Explanations
5.1 Closed functionality Heading cell – no response required Heading cell – no response required
5.1.2 General Heading cell – no response required Heading cell – no response required
5.1.2.1 Closed functionality See 5.2 through 13 See information in 5.2 through 13
5.1.2.2 Assistive technology See 5.1.3 through 5.1.6 See information in 5.1.3 through 5.1.6
5.1.3 Non-visual access Heading cell – no response required Heading cell – no response required
5.1.3.1 Audio output of visual information    
5.1.3.2 Auditory output delivery including speech Not Applicable
5.1.3.3 Auditory output correlation Not Applicable
5.1.3.4 Speech output user control Not Applicable
5.1.3.5 Speech output automatic interruption Not Applicable  
5.1.3.6 Speech output for non-text content Not Applicable
5.1.3.7 Speech output for video information Not Applicable
5.1.3.8 Masked entry Not Applicable
5.1.3.9 Private access to personal data Not Applicable
5.1.3.10 Non-interfering audio output Not Applicable
5.1.3.11 Private listening volume Not Applicable
5.1.3.12 Speaker volume Not Applicable
5.1.3.13 Volume reset Not Applicable
5.1.3.14 Spoken languages Not Applicable
5.1.3.15 Non-visual error identification Not Applicable
5.1.3.16 Receipts, tickets, and transactional outputs Not Applicable
5.1.4 Functionality closed to text enlargement Not Applicable
5.1.5 Visual output for auditory information Not Applicable
5.1.6 Operation without keyboard interface Heading cell – no response required Heading cell – no response required
5.1.6.1 Closed functionality See 5.1.3.1 through 5.1.3.16 See information in 5.1.3.1 through 5.1.3.16
5.1.6.2 Input focus Not Applicable
5.1.7 Access without speech Not Applicable
5.2 Activation of accessibility features Not Applicable
5.3 Biometrics Not Applicable
5.4 Preservation of accessibility information during conversion Not Applicable
5.5 Operable parts Heading cell – no response required Heading cell – no response required
5.5.1 Means of operation Not Applicable
5.5.2 Operable parts discernibility Not Applicable
5.6 Locking or toggle controls Heading cell – no response required Heading cell – no response required
5.6.1 Tactile or auditory status Not Applicable
5.6.2 Visual status Not Applicable
5.7 Key repeat Not Applicable
5.8 Double-strike key acceptance Not Applicable
5.9 Simultaneous user actions Not Applicable

Not Used: Chapter6: ICT with Two-Way Voice Communication

Not used in evaluation, so the table of criteria does not appear here.

Not Used: Chapter7: ICT with Video Capabilities

Not used in evaluation so the table of criteria does not appear here.

Not Used: Chapter8: Hardware

Not used in evaluation so the table of criteria does not appear here.

Chapter9: Web(seeWCAG 2.x section)

See WCAG section.

Chapter10: Non-Web Documents

Notes: Support Documentation and other documents not evaluated at this time. Web-based documentation such as the Delinea Documentation Portal would be under WCAG and have its own accessibility information, which does not exist at this time.

Criteria Conformance Level Remarks and Explanations
10.0 General (informative) Heading cell – no response required Heading cell – no response required
10.1.1.1 through 10.4.1.3 See WCAG 2.x section See information in WCAG 2.x section
10.5 Caption positioning Not Applicable
10.6 Audio description timing Not Applicable

Chapter11: Software

Notes:

Criteria Conformance Level Remarks and Explanations
11.0 General (informative) Heading cell – no response required Heading cell – no response required
11.1.1.1 through 11.4.1.3 See WCAG 2.x section See information in WCAG 2.x section
11.5 Interoperability with assistive technology Heading cell – no response required Heading cell – no response required
11.5.1 Closed functionality Heading cell – no response required Heading cell – no response required
11.5.2 Accessibility services Heading cell – no response required Heading cell – no response required
11.5.2.1 Platform accessibility service support for software that provides a user interface See 11.5.2.5 through 11.5.2.17 See information in 11.5.2.5 through

* 11.5.2.17
11.5.2.2 Platform accessibility service support for assistive technologies See 11.5.2.5 through 11.5.2.17 See information in 11.5.2.5 through 11.5.2.17
11.5.2.3 Use of accessibility services See information in 11.5.2.5 through 11.5.2.17 See information in 11.5.2.5 through 11.5.2.17
11.5.2.4 Assistive technology Supports
11.5.2.5 Object information Partially Supports See “Known Issues” in document.
11.5.2.6 Row, column, and headers Not Applicable Not Applicable to function.
11.5.2.7 Values Partially Supports, See Note User agent primarily uses announcements/notifications. A flow exists to send a message as to why a user should have access to an application. Values of the action message are configured by the administration console and can be further edited by the administration; depending on edits these values and their accessibility may vary.
11.5.2.8 Label relationships Supports
11.5.2.9 Parent-child relationships Partially Supports User agent primarily uses announcements/notifications. A flow exists to send a message as to why a user should have access to an application. Values of the action message are configured by the administration console and can be further edited by the administration; depending on edits these values and their accessibility may vary.
11.5.2.10 Text Supports
11.5.2.11 List of available actions Supports
11.5.2.12 Execution of available actions Supports
11.5.2.13 Tracking of focus and selection attributes Partially Supports, See Notes Operating system overrides and settings such as modifications of focus cursor, text size, etc are respected as much as the OS allows.
1.5.2.14 Modification of focus and selection attributes Supports
11.5.2.15 Change notification Not Applicable User cannot modify/not applicable to function.
11.5.2.16 Modifications of states and properties Not Applicable User cannot modify user agent.
11.5.2.17 Modifications of values and text Partially Supports, See Note User cannot modify user agent. User agent primarily uses announcements/notifications. A flow exists to send a message as to why a user should have access to an application. Values of the action message are configured by the administration console and can be further edited by the administration; depending on edits these values and their accessibility may vary.
11.6 Documented accessibility usage Heading cell – no response required Heading cell – no response required
11.6.1 User control of accessibility features Supports, See Note Values of the action message are configured by the administration console and can be further edited by the administration; depending on edits these values and their accessibility may vary.
11.6.2 No disruption of accessibility features Partially Supports, See Note
11.7 User preferences Partially Supports, See Note Operating system overrides and settings such as modifications of focus cursor, text size, etc are respected as much as the OS allows.
11.8 Authoring tools Heading cell – no response required Heading cell – no response required
11.8.1 Content technology Heading cell – no response required Heading cell – no response required
11.8.2 Accessible content creation Not Applicable See information in WCAG 2.x section, but user agent is not an authoring tool. User agent primarily uses announcements/notifications. A flow exists to send a message as to why a user should have access to an application; that is the extent of any authoring.
11.8.3 Preservation of accessibility information in transformations Not Applicable
11.8.4 Repair assistance Not Applicable
11.8.5 Templates Not Applicable

Not Used: Chapter 12: Documentation and Support Services

Notes:

Criteria Conformance Level Remarks and Explanations
12.1 Product documentation Heading cell – no response required Heading cell – no response required
12.1.1 Accessibility and compatibility features Partially Supports Upon Request
12.1.2 Accessible documentation See WCAG 2.x section See information in WCAG 2.x section
12.2 Support Services Heading cell – no response required Heading cell – no response required
12.2.2 Information on accessibility and compatibility features Does Not Support
12.2.3 Effective communication Partially Supports
12.2.4 Accessible documentation See WCAG 2.x section See information in WCAG 2.x section

Chapter 13: ICT Providing Relay or Emergency Service Access

Notes: Not used for evaluation so table of criteria does not appear here.