You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of issue: in the fist page, previous button appears as disabled. But it is done using disabled class and span element. As a result, running a11y rules via wave extensions gives contrast error
Steps to reproduce: Just install the wave extension and right click and select "WAVE this page" to run the tool
Expected result: Elements with disabled attribute is skipped by the tool and hence there should be no contrast issue
Actual result: Since we are using disabled class and span, the element is scanned for contrast and it fails
Not exactly. disabled attribute is supported on few elements like button, input etc. Ideal solution would be to use buttons instead of span for clickable things. That also makes it semantically correct :)
Angular version: 11
ngx-pagination version: 5.1.1
Description of issue: in the fist page, previous button appears as disabled. But it is done using disabled class and span element. As a result, running a11y rules via wave extensions gives contrast error
Steps to reproduce: Just install the wave extension and right click and select "WAVE this page" to run the tool
Expected result: Elements with disabled attribute is skipped by the tool and hence there should be no contrast issue
Actual result: Since we are using disabled class and span, the element is scanned for contrast and it fails
just check the tool result on the detault stackblitz url https://angular-e1f9hq.stackblitz.io/
The text was updated successfully, but these errors were encountered: