2.4.2 Page Titled: Web pages have Supported With Exceptions Page Title is same for all the pages titles that describe topic or purpose. appearing in the Azure Data Catalog Portal. 2.4.3 Focus Order: If a Web page can Supported be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. 2.4.4 Link Purpose (In Context): The Supported purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. 2.4.5 Multiple Ways: More than one Supported way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. 2.4.6 Headings and Labels: Not Supported No headings are defined on the Headings and labels describe or application's pages. purpose. 2.4.7 Focus Visible: Any keyboard Supported operable user interface has a mode of operation where the keyboard focus indicator is visible. Principle 3: Understandable Information and the operation of user interface must be understandable. Guideline 3.1 Readable Make text content readable and understandable. Criteria Supporting Feature Remarks and Explanations 3.1.1 Language of Page: The Not Supported Language of the page is not defined default human language of each programmatically on the Azure Data Web page can be programmatically Catalog Portal pages. determined. 3.1.2 Language of Parts: The Not Supported Azure Data Catalog supports human language of each passage or entering tags, annotations, or phrase in the content can be registering asset metadata from programmatically determined except languages. However, there for proper names, technical terms, are no internal language attributes
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. Supported With Exceptions Page Title is same for all the pages appearing in the Azure Data Catalog Portal. 2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. Supported 2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. Supported 2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. Supported 2.4.6 Headings and Labels: Headings and labels describe or purpose. Not Supported No headings are defined on the application's pages. 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. Supported Principle 3: Understandable Information and the operation of user interface must be understandable. Guideline 3.1 Readable Make text content readable and understandable. Criteria Supporting Feature Remarks and Explanations 3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. Not Supported Language of the page is not defined programmatically on the Azure Data Catalog Portal pages. 3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, Not Supported Azure Data Catalog supports entering tags, annotations, or registering asset metadata from languages. However, there are no internal language attributes
Azure%20Data%20Catalog.Win32.WCAG_091217.DOCX