[Sourcing-2][Accessibility: ACC-264.1][WIP] All NGX 'Button' or 'Button menu' are provided with role 'Toggle button' and is incorrect.

[JyotiKumari1507]

Is this a bug, enhancement, or feature request?

bug

Describe your proposal.

All NGX core and Platform 'Button' or 'Button menu' are provided with role 'Toggle button' and is incorrect.... Every Button and Button Menu of NGX core and Platform is read out by screen reader as 'Toggle button'. Even though we have not used 'Toggle button' any places . Its coming from NGX component

Can you handle that on the application side

No

Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)

Accessibility expert

If this is a bug, please provide steps for reproducing it; the exact components you are using;

Using Screen reader easily can check all Button and Button menu is readout as "toggle button".

Please provide relevant source code (if applicable).

Please provide stackblitz example(s).

In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.

Yes we have got this bug from Accessibility expert only.

Did you check the documentation and the API?

Yes

Did you search for similar issues?

Is there anything else we should know?

[droshev]

@JyotiKumari1507 we would need some specific examples. In general you should test our documentation page for accessibility as it is more created for the developers to explore the cases and the API.

BTW, in the first example of the buttons I see the button being written:

I couldn't spot any toggle labels

[JyotiKumari1507]

@droshev Toggle button is read out by Screen reader for Button and Menu button every where while testing by Accessibility Team even though we have not used this word anywhere . Lets discuss about this in our next call

[droshev]

@JyotiKumari1507 we need the input written so it will be easier to process

[JyotiKumari1507]

@droshev Attaching screen reader screenshot for more details:

[droshev]

Most of the fields are not answered. We can't analyze from screenshots

[JyotiKumari1507]

@droshev please let us know what fields are pending to fill from our side. I think I have shared all details already. Lets have call if still issue isn't explained well

[droshev]

@JyotiKumari1507 did you set all aria attributes needed? If so, can you create a small stackblitz example demonstrating that you cannot set this on the application side?

[JyotiKumari1507]

@divyamalhotra488 please share stackblitz example

[droshev]

@JyotiKumari1507 any update?

[divyamalhotra488]

Hi @droshev, please find stackblitz example here: https://stackblitz.com/edit/vkz16p?file=src%2Fapp%2Fbutton-types-example.component.html