Skip to content

heading with aria-level > 6 #1050

Closed

Description

@JAWS-test

I suggest that https://w3c.github.io/aria/#heading explicitly mentions that aria-level, unlike HTML headings, can be greater than 6.

Activity

  1. added this to the ARIA 1.3 milestone on Sep 26, 2019
  2. sahilempire commented on Mar 2, 2021

    @sahilempire

    I want to work on this issue, please assign me.

    Thank you.

  3. sahilempire commented on Mar 4, 2021

    @sahilempire

    Hello @jnurthen ,

    I am new and a quite beginner in the world of Open Source, so please help me through and please tell me what exactly I have to do.

    Thanking you

  4. johnfoliot commented on Mar 4, 2021

    @johnfoliot

    I don't have too much skin in the game here, but I question whether allowing aria-level to exceed "6" is a good idea or not.

    My understanding with a lot of the aria attributes is/was to develop parity with host languages (here HTML), and in HTML, the heading levels go from 1 to 6. Experience suggests however that under most circumstances, headings beyond level 'h5' are exceedingly rare, and I question any real value in allowing aria-level to fork from the default values previously determined in HTML, and supported by AT for more than 2 decades. (Do we have any assurance or indication that assistive technology would support a level 7, 8, 9, or 10?)

    If anything, rather than making an edit to role=heading, I'd seek to add clarification to aria-level and implement a max value (of 6).

    My $0.02 from an old punter.

  5. sahilempire commented on Mar 10, 2021

    @sahilempire

    Hello, @johnfoliot ,

    You are absolutely correct, because as a Web Developer, I am understand the concept of this heading and all, so I don't think so, that we have to add more heading levels.

    So please tell me now what next I have to do, as I really want to contribute in W3C.

    Thanking You.

  6. jnurthen commented on Mar 10, 2021

    @jnurthen
    Member

    @JAWS-test do you have a test page which shows the level of support for heading levels > 6?

  7. JAWS-test commented on Mar 11, 2021

    @JAWS-test
    ContributorAuthor

    @jnurthen https://codepen.io/jaws-test/pen/bGBOgQX

    Test results

    • JAWS + Edge, IE 11, Chrome, Firefox: 1-6 as level 1-6, all other as level 2, fractional numbers are rounded down
    • NVDA + Edge, Chrome: 1-9 as level 1-9, all other as level 2, fractional numbers are rounded down
    • NVDA + IE 11: 1-1000000 as level 1-1000000, without level and 0 as heading without any level, fractional numbers are rounded down
    • NVDA + Firefox: 1-1000000 as level 1-1000000, without level and 0 as level 2, fractional numbers are rounded down
    • MS Narrator + Edge, Chrome: 1-9 as level 1-9, all other as level 2, fractional numbers are rounded down
    • MS Narrator + Firefox: 1-9 as level 1-9, without level and 0 as level 2, 10 and larger: no output as heading, fractional numbers are rounded down
    • TalkBack + Chrome: 1-6 as level 1-6, 7-9 not as heading but as column header, all other as level 2, fractional numbers are rounded down
    • VoiceOver + Safari (iPhone): 1-1000000 as level 1-1000000, without level and 0 as level 2, fractional numbers are rounded down

    Firefox submits level 2 to the Accessibility API for missing values and values less than 1, and the respective number for all numbers greater than 1 (rounded down for fractional numbers).

    Chrome and Edge correctly submit to the Accessibility API the value in aria-level and also determine two custom values for a heading level (see figure 1):

    • 1st value: for 1-9 the values 1-9, for all others the value 2.
    • 2nd value: for 1-9 the values 1-9, for all others the value 0 (probably to show that there is actually no correct value).

    chrome_aria-level
    Figure 1: Accessiblity Tab of Chrome (F12)

    More test results with other browsers and screen readers are welcome!

  8. added
    clarificationclarifying or correcting language that is either confusing, misleading or under-specified
    on Sep 13, 2022
  9. added a commit that references this issue on Mar 3, 2023
    af84654
  10. added a commit that references this issue on Oct 10, 2023
    69979bf
  11. moved this to Good first issues in ARIA 1.3on Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

clarificationclarifying or correcting language that is either confusing, misleading or under-specifiedgood first issue

Type

No type

Projects

  • Status
    Good first issues

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions