You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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.
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).
Figure 1: Accessiblity Tab of Chrome (F12)
More test results with other browsers and screen readers are welcome!
Activity
sahilempire commentedon Mar 2, 2021
I want to work on this issue, please assign me.
Thank you.
sahilempire commentedon Mar 4, 2021
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
johnfoliot commentedon Mar 4, 2021
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.
sahilempire commentedon Mar 10, 2021
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.
jnurthen commentedon Mar 10, 2021
@JAWS-test do you have a test page which shows the level of support for heading levels > 6?
JAWS-test commentedon Mar 11, 2021
@jnurthen https://codepen.io/jaws-test/pen/bGBOgQX
Test results
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):
Figure 1: Accessiblity Tab of Chrome (F12)
More test results with other browsers and screen readers are welcome!
fix(aria-level): update to specify only level 1-6 (#1873)
fix(aria-level): update to specify only level 1-6 (#1873)