No support for multiple roles

[rdeltour]

Summary

According to ARIA 1.1

• The attribute value MUST allow a token list as the value;
• The first name literal of a non-abstract WAI-ARIA role in the list of tokens in the role attribute defines the role according to which the user agent MUST process the element.

However, JAWS doesn’t go past unknown role values, and ignores any valid supported role that may appear after the 1st position in the token list.

Example:

1. Go to https://s.codepen.io/stevef/debug/wKrdYQ (test pen from @stevefaulkner)
2. test 2 and 4 aren’t processed as main areas.

Expected result

Test 2 and 4 should be announced like test 1, 3, and 5.

Unknown, or otherwise illegal roles (such as abstract roles "section" and "landmark") should be ignored, and the first non-abstract role "main" should be taken into account.

Actual result

The role "main" is not applied to test 2 and 4.

Example

See @stevefaulkner’s "multiple role values tests" pen

Additional Information

See also TPG’s testing results.

JAWS version and build number

JAWS 2018, build 1712.10 ILM.

Operating System and version

Windows 10 64bit.

Browser and version:

IE 11 (11.1198.14393.0)

[hanshillen]

These are the results I'm getting with JAWS 2018.1803.24 ILM:

IE11

• Test 2 (landmark main): No role announced
• Test 4 (section landmark main): No role announced

  Edge

• Test 5 (main section landmark): Content is not read at all, JAWS just says "Blank". If you remove the other content following test 5, JAWS announces "test 5" but does not announce the role.

  Firefox ESR 52.7.3

• Only Test 1 is announced correctly with a main role, the others aren't.

  Chrome 65

• Only Test 1 is announced correctly with a main role, the others aren't.

All other test cases are announced correctly

Logged as bug # 100677

[stevefaulkner]

Tested with JAWS 2024.2310.70 , NVDA 2023.3, chrome and Firefox latest. NVDA recognizes the correct roles for all, The roles are exposed correctly in the browser acc tree. JAWS only recognises the first landmark, it's fine with the switches. test case

[BrettLewisVispero]

Imported into ADO as bug 49382