Skip to content
This repository was archived by the owner on Jan 4, 2026. It is now read-only.
This repository was archived by the owner on Jan 4, 2026. It is now read-only.

A11y Screen Reader - Page structure challenges #111

Open

Description

@DaveBest99

Screen reader WCAG issues.

  1. Perceivable: Page structure lacks content relationships; (no region), (missing text label on ), (missing text label on ).
  2. Operable: Pressing Enter key on Link elements (like "COMPONENTS" and "GUIDES") provide no verbal feedback of cursor focus change to notify the blind user.
  3. Understandable: The page is simple but is missing Breadcrumb and proper page Title for orientation.
  4. Robust: Not tested.

Angular Material Accessibility Introduction.mp4: https://www.dropbox.com/s/rz2gtuhnbx9czus/Angular%20Material%20Accessibility%20Introduction.mp4?dl=0

Activity

  1. naomiblack commented on Apr 7, 2017

    @naomiblack

    @riavalon could you update this issue with status? Other than the issue with routing, where are we at on the remainder of these page structure questions?

  2. riavalon commented on Apr 7, 2017

    @riavalon
    Contributor

    Sure thing: I've added in some tweaks to update how the page is structured with different regions as well as added the ability to have the page title updated on route change now. There is still an issue with getting verbal feedback about page transitions that I don't think we have officially settled on a solution for. There's more info in the PR I created: #117

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions