search

FreedomScientific / standards-support

Contains documentation for Vispero software support of Web standards
https://freedomscientific.github.io/standards-support/
GNU General Public License v3.0
105 stars 11 forks source link

JAWS ignores aria-label for <hr> element and doesn't recognize element with role='separator' in Fireforx #833

Open Karkhutvy opened 1 month ago

Karkhutvy commented 1 month ago

Summary

For the next code snippet

<div>
  Content above
  <hr aria-label='Named'>
  Content in the middle
  <div role='separator'>Visible label</div>
  Content in the middle
  <div role='separator' aria-label="Hidden label">Visible label2</div>
  Content below
</div>

User navigates through elements from the top to bottom

Expected result

Jaws announces:

  1. Content above
  2. Named separator
  3. Content in the middle
  4. separator
  5. Content in the middle
  6. Hidden label separator
  7. Content below

Actual result

Jaws announces:

  1. Content above 2. separator - accessible name not announced 3. Content in the middle and Content in the middle - announced as singular string Separator element not recognized at all - no screen reader focus on this and nothing announced
  2. Hidden label separator
  3. Content below

Example

See above

Additional Information

Is this issue related to JAWS or Firefox?

JAWS version and build number

JAWS 2024.2403.3

Operating System and version

Windows 10 Enterprise Version 10.0.19045 Build 19045

Browser and version:

Mozilla Firefox 125.0.3 (64-bit)

davidengebretson commented 1 month ago

I'm curious why you'd like to use HR elements in such an expansive way.?

Personally I've always wanted HR's to be invisible as I navigate a page with JAWS. What non-visual person needs to see an HR element?

My suggestion for your developers is to use

so I won't have to see the
in the visual design as I navigate the DOM.

HR elements just seem like visual "fluff" to me.

Thanks, David

From: Karkhut Volodymyr @.> Sent: Thursday, May 9, 2024 2:59 AM To: FreedomScientific/standards-support @.> Cc: Subscribed @.***> Subject: [FreedomScientific/standards-support] JAWS ignores aria-label for

element and doesn't recognize element with role='separator' in Fireforx (Issue #833)

Summary

For the next code snippet

Content above
Content in the middle
Visible label
Content in the middle
Visible label2
Content below

User navigates through elements from the top to bottom

Expected result

Jaws announces:

  1. Content above
  2. Named separator
  3. Content in the middle
  4. separator
  5. Content in the middle
  6. Hidden label separator
  7. Content below

Actual result

Jaws announces:

  1. Content above
    1. separator - accessible name not announced
    2. Content in the middle and Content in the middle - announced as singular string Separator element not recognized at all - no screen reader focus on this and nothing announced
  2. Hidden label separator
  3. Content below

Example

See above

Additional Information

Is this issue related to JAWS or Firefox?

JAWS version and build number

JAWS 2024.2403.3

Operating System and version

Windows 10 Enterprise Version 10.0.19045 Build 19045

Browser and version:

Mozilla Firefox 125.0.3 (64-bit)

- Reply to this email directly, view it on GitHubhttps://github.com/FreedomScientific/standards-support/issues/833, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKX5QZRFBT7F2LPLK63R32TZBNCG5AVCNFSM6AAAAABHOQYHS2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DOMZTG42TSNY. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Karkhutvy commented 1 month ago

Hi @davidengebretson, thank you for feedback. I've been working on custom separator component from our components library. This component might also contain visible label so I want to present this label as <hr> accessible name. As this is library component I can't predict all use cases of using this component. Though, if someone will decide to use this component as meaningful named element that needs to be presented to screen reader. In other case component can be hidden by client code as you suggested. So, as role='separator' description allows this element to be presented to screen reader along with it's accessible name I also want to support this functionality.

Best Regards, Volodymyr

I'm curious why you'd like to use HR elements in such an expansive way.? Personally I've always wanted HR's to be invisible as I navigate a page with JAWS. What non-visual person needs to see an HR element? My suggestion for your developers is to use

so I won't have to see the
in the visual design as I navigate the DOM. HR elements just seem like visual "fluff" to me. Thanks, David

davidengebretson commented 1 month ago

Personally I don’t think it is necessary.

The

element is visual fluff for assistive technology users, especially if proper semantic heading structure is used in the design of the content.

I’m happy to be proven wrong, however. 😊

Thanks, David

From: Karkhut Volodymyr @.> Sent: Friday, May 10, 2024 1:06 AM To: FreedomScientific/standards-support @.> Cc: David Engebretson @.>; Mention @.> Subject: Re: [FreedomScientific/standards-support] JAWS ignores aria-label for

element and doesn't recognize element with role='separator' in Fireforx (Issue #833)

Hi @davidengebretsonhttps://github.com/davidengebretson, thank you for feedback. I've been working on custom separator component from our components library. This component might also contain visible label so I want to present this label as

accessible name. As this is library component I can't predict all use cases of using this component. Though, if someone will decide to use this component as meaningful named element that needs to be presented to screen reader. In other case component can be hidden by client code as you suggested. So, as role='separator' description allows this element to be presented to screen reader along with it's accessible name I also want to support this functionality.

Best Regards, Volodymyr

I'm curious why you'd like to use HR elements in such an expansive way.? Personally I've always wanted HR's to be invisible as I navigate a page with JAWS. What non-visual person needs to see an HR element? My suggestion for your developers is to use

so I won't have to see the

in the visual design as I navigate the DOM. HR elements just seem like visual "fluff" to me. Thanks, David

— Reply to this email directly, view it on GitHubhttps://github.com/FreedomScientific/standards-support/issues/833#issuecomment-2104140887, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKX5QZTSYZRZ6FO5JX4LGVTZBR5WHAVCNFSM6AAAAABHOQYHS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBUGE2DAOBYG4. You are receiving this because you were mentioned.Message ID: @.**@.>>