Skip to content

input type=number, type=range should report a violation for use of aria-valuemin #360

Closed
Closed
input type=number, type=range should report a violation for use of aria-valuemin#360
Assignees
shunguoy
Labels
BugSomething isn't workingdevelopmentengine-rulesIssues in the accessibility-checker-engine componentpriority-3 (low)

Description

@carmacleod
carmacleod
opened on Mar 15, 2021

Steps:

input type=number and type=range should report a violation for use of aria-valuemin

Activity

  1. carmacleod
    added
    BugSomething isn't working
    on Mar 15, 2021
  2. tombrunet
    added
    engine-rulesIssues in the accessibility-checker-engine component
    on Apr 21, 2021

  3. MHoov commented on Jun 1, 2021

    @MHoov
    MHoov
    on Jun 1, 2021

    As of June 1

    • general rule description (SME & Dev)
    • testcases written (Dev)
    • rule bug (Dev)
    • message written (SME)
    • help written (SME)
  4. aliunwala
    added
    development
    priority-3 (low)
    on Jan 11, 2022

  5. shunguoy commented on Mar 8, 2022

    @shunguoy
    shunguoy
    on Mar 8, 2022
    Contributor

    this should be covered in #721. close.

  6. shunguoy
    self-assigned this
    on Mar 9, 2022
  7. shunguoy
    closed this as completedon Mar 9, 2022
  8. marcjohlic
    added a parent issue on Oct 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething isn't workingdevelopmentengine-rulesIssues in the accessibility-checker-engine componentpriority-3 (low)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions