Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-1669

Accessibility on IdP pages



    • Operating System:
    • Java Version:
      Other OpenJDK 11
    • Servlet Container:
      Apache Tomcat 9


      Accessibility requirements have got stricter in some jurisdictions requiring sites to comply with the W3 WCAG guidelines. Use of a third-party checking tool (in this case "Wave") shows a few things to change to comply with such requirements when targeted against a new IdP4 login page.

      The WAVE Firefox plugin checking the login page shows 1x Error, 1x Alert and some things to consider (which probably don't apply to a login page anyway):


      Error: Document language missing

      What It Means

      The language of the document is not identified.

      Why It Matters

      Identifying the language of the page allows screen readers to read the content in the appropriate language. It also facilitates automatic translation of content.

      How to Fix It

      Identify the document language using the <html lang> attribute (e.g., <html lang="en">).

      The Algorithm... in English

      The <html lang> attribute is missing or is empty.

      Standards and Guidelines

      Alert: No heading structure

      What It Means

      The page has no headings.

      Why It Matters

      Headings (<h1>-<h6>) provide important document structure, outlines, and navigation functionality to assistive technology users.

      How to Fix It

      Provide a clear, consistent heading structure, generally one <h1> and sub-headings as appropriate. Except for very simple pages, most web pages should have a heading structure.

      The Algorithm... in English

      No <h1>-<h6> elements are present in the page.

      Standards and Guidelines


        1. image-2020-09-02-16-21-43-279.png
          352 kB
          Matthew Slowe



            cantor.2@osu.edu Scott Cantor
            matthew.slowe@corp.jisc.ac.uk Matthew Slowe
            3 Start watching this issue