how to update aria label value
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- angular, typescript
- Domain
- accessibility, frontend
Research direction
Start with the ngx-slider component and its Options configuration, focusing on the ariaLabel setting and the rendered role and aria-label attributes shown by the user's example. Reproduce the price-slider markup and verify that the configured label produces a valid accessible slider without the reported compliance warning.
Written by the indexing model from the issue text.
Description
Hi,
we are using below code snippet to show the price slider on our site but we are getting ADA compliance issue for this.
<ngx-slider *ngIf="isBrowser" [(value)]="min" [(highValue)]="max" [options]="options" (userChangeEnd)="appliedFilter($event)" >
ADA compliance issue reported : aria-label attribute is not well supported on a ngx-slider with no valid role attribute.
to fix this we tried. -
<ngx-slider *ngIf="isBrowser" [(value)]="min" [(highValue)]="max" [options]="options" (userChangeEnd)="appliedFilter($event)" role="slider" aria-label="Select a range">
Also tried to update like below :
options: Options = {
floor: 0,
ceil: 10000,
ariaLabel: "Select a Price"
};
but still seeing same when inspecting code -
Can you please check and let us know.. how to update the aria-label value to fix the compliance issue.
- Dominant language
- TypeScript
- Stars
- 412
- Forks
- 177
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from angular-slider/ngx-slider
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
angular-slider/ngx-slider#450 ·
-
On Applying high contrast Aquatic/Dessert themes, Slider control is not visible.Possibly taken @dajiaohuang claimed this 21 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
angular-slider/ngx-slider#448 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
angular-slider/ngx-slider#403 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
angular-slider/ngx-slider#398 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
angular-slider/ngx-slider#393 · 1 comment ·
All issues in angular-slider/ngx-slider
Similar issues
-
area: web
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
inabagumi/shinju-date#6823 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#540 ·
Maintainers usually reply within 1 day
-
accepted ai-dev ai-implementing
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
livesport/homer#218 · 1 comment ·
Maintainers usually reply within 1 day
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
figma/code-connect#419 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100