EDB WCAG 2.0 Level AA Roadmap

January 22, 2018

EnterpriseDB (EDB) is focused on meeting Section 508 requirements and is planning to meet the key requirements of WCAG 2.0 at the A and AA levels, to the degree that those requirements are applicable to web-based business applications.

 

PEM (Postgres Enterprise Manager) is the leading EDB product with a web interface; all other products leverage the command line interfaces of the underlying operating system capabilities and do not require separate VPAT or WCAG 2.0 compliance efforts, or are planned to be merged into the PEM interface in the next 18-24 months.

 

In 2018 and through Q2 2019 EDB will target to achieve Level A compliance with WCAG 2.0. WCAG 2.0 Level AA is targeted for completion in Q2 2020. Below is the high level schedule for the work.

 

The product version numbers may change, e.g., PEM 7.8, targeted for Q2 2019 may be rebranded as PEM 8, or be replaced by a different product.

Definition of WCAG 2.0 Level A requirements

Definition of WCAG 2.0 Level AA requirements

 


Disclaimer

Statements included in this blog, other than statements or characterizations of historical fact, are forward-looking statements. These forward-looking statements are based on our current expectations, estimates, and projections about our industry, management’s beliefs, and certain assumptions made by us, all of which are subject to change. These forward-looking statements are not guarantees of future results and are subject to risks, uncertainties, and assumptions that could cause our actual results to differ materially and adversely from those expressed in any forward-looking statement. By sharing our product roadmap with you, we are not undertaking an obligation to develop the software with the features and functionality discussed herein. The forward-looking statements in this blog are made as of January 3, 2018 (today). We undertake no obligation to revise or update publicly any forward-looking statement for any reason.

 

WCAG 2.0 Level A

Guideline

Product version

Target Date

Guideline 1.1 – Text Alternatives

1.1.1 Non-text Content

7.6

Q4 2018

Guideline 1.2 – Time-based Media

1.2.1 Audio-only and Video-only (Prerecorded)

1.2.2 Captions (Prerecorded)

1.2.3 Audio Description or Media Alternative (Prerecorded)

7.1 (PEM does not use pre-recorded time-based media)

Nov 2017

Guideline 1.3 – Adaptable

1.3.1 Info and Relationships

1.3.2 Meaningful Sequence

1.3.3 Sensory Characteristics

7.6

Q4 2018

Guideline 1.4 – Distinguishable

1.4.1 Use of Color

7.4

Q2 2018

1.4.2 Audio Control

7.1 (PEM does not play audio on any webpage for more than 3 secs)

Nov 2017

Guideline 2.1 – Keyboard Accessible

2.1.1 Keyboard

2.1.2 No Keyboard Trap

7.4

Q2 2018

Guideline 2.2 – Enough Time

2.2.1 Timing Adjustable

2.2.2 Pause, Stop, Hide

7.4

Q2 2018

Guideline 2.3 – Seizures

2.3.1 Three Flashes or Below Threshold

7.1

Nov 2017

Guideline 2.4 – Navigable

2.4.1 Bypass Blocks

2.4.2 Page Titled

2.4.3 Focus Order

7.4

Q2 2018

2.4.4 Link Purpose (In Context)

7.6

Q4 2018

Guideline 3.1 – Readable

3.1.1 Language of Page

7.4

Q2 2018

Guideline 3.2 – Predictable

3.2.1 On Focus

3.2.2 On Input

7.4

Q2 2018

Guideline 3.3 – Input Assistance

3.3.1 Error Identification

7.1

Nov 2017

3.3.2 Labels or Instructions

7.1

Nov 2017

Guideline 4.1 – Compatible

4.1.1 Parsing

4.1.2 Name, Role, Value

7.10

Q4 2019

 

WCAG Level AA

Guideline

Product version

Target Date

1.2.4 Captions (Live)

1.2.5 Audio Description (Prerecorded)

7.1 (PEM does not use pre-recorded time-based media)

Nov 2017

1.4.3 Contrast (Minimum)

1.4.4 Resize text

1.4.5 Images of Text

7.6

Q4 2018

2.4.5 Multiple Ways

2.4.6 Headings and Labels

2.4.7 Focus Visible

7.6

Q4 2018

3.1.2 Language of Parts

7.11

Q2 2020

3.2.3 Consistent Navigation

3.2.4 Consistent Identification

7.8

Q2 2019

3.3.3 Error Suggestion

3.3.4 Error Prevention (Legal, Financial, Data)

7.8

Q2 2019

 

Share this