Re: Regarding AccName and case sensitivity of roles and attribute values

Not quite. That only defines case requirements when ARIA is used with HTML.

________________________________
From: Schnabel, Stefan <[email protected]>
Sent: Friday, August 28, 2020 1:59:43 AM
To: Steve Faulkner <[email protected]>
Cc: Bryan Garaventa <[email protected]>; ARIA <[email protected]>
Subject: RE: Regarding AccName and case sensitivity of roles and attribute values


Thanks! Bryan, I think you have your answer 😊



From: Steve Faulkner <[email protected]>
Sent: Freitag, 28. August 2020 10:51
To: Schnabel, Stefan <[email protected]>
Cc: Bryan Garaventa <[email protected]>; ARIA <[email protected]>
Subject: Re: Regarding AccName and case sensitivity of roles and attribute values



The W3C HTML validator



Example: https://validator.w3.org/nu/?showoutline=yes&doc=https%3A%2F%2Fcdpn.io%2Fstevef%2Fdebug%2FOJNmGOO


On Friday, 28 August 2020, Schnabel, Stefan <[email protected]<mailto:[email protected]>> wrote:

Steve,



Are you aware of any validators checking this?



Regards

Stefan



From: Steve Faulkner <[email protected]<mailto:[email protected]>>
Sent: Freitag, 28. August 2020 09:38
To: Schnabel, Stefan <[email protected]<mailto:[email protected]>>
Cc: Bryan Garaventa <[email protected]<mailto:[email protected]>>; ARIA <[email protected]<mailto:[email protected]>>
Subject: Re: Regarding AccName and case sensitivity of roles and attribute values



There are normative authoring requirements around this:



Authors MUST use lowercase ASCII letters<https://xm2c042ryh.proxynodejs.usequeue.com/multipage/infrastructure.html#lowercase-ascii-letters> for all role token values and any state or property attributes (aria-*) whose values are defined as tokens<https://ekuhu0ggzk.proxynodejs.usequeue.com/TR/wai-aria-1.1/#propcharacteristic_value>.



https://93seqoby0t.proxynodejs.usequeue.com/html-aria/#case-sensitivity <https://93seqoby0t.proxynodejs.usequeue.com/html-aria/#case-sensitivity>



--

Regards

SteveF

Accessibility is political[✊]

Working for the web<https://dn3qbixcap.proxynodejs.usequeue.com/stevefaulkner/status/940835584410574850>,

anywhere and everywhere [🖖🏽]





On Fri, 28 Aug 2020 at 07:31, Schnabel, Stefan <[email protected]<mailto:[email protected]>> wrote:

From my humble knowledge of the past group decisions, it IS strict and SHOULD be accepted by User Agents if correct.

User agents may apply internal heuristics to work around and therefore uppercase has no effect in practice.



But I think even some validators out there check already attribute case (Must look for examples here).



Regards

Stefan



From: Bryan Garaventa <[email protected]<mailto:[email protected]>>
Sent: Donnerstag, 27. August 2020 18:32
To: ARIA <[email protected]<mailto:[email protected]>>
Subject: Regarding AccName and case sensitivity of roles and attribute values



Hi,

Does anyone know how strict the case requirement is for ARIA roles and supporting attributes?



Since AccName changes depending on specific roles when present, I need to know if certain usages are automatically ignored or if they should be supported, such as if role=”tablist” is correct, but role=”TabList” is not. According to the ARIA spec, the second is not valid.



Please let me know your thoughts.



Thanks,

Bryan













Bryan Garaventa

Principal Accessibility Architect

Level Access, Inc.

[email protected]<mailto:[email protected]>

415.624.2709 (o)

www.LevelAccess.com<https://nhfjemsxwq.proxynodejs.usequeue.com/>




--

--

Regards

SteveF

Accessibility is political[✊]

Working for the web<https://dn3qbixcap.proxynodejs.usequeue.com/stevefaulkner/status/940835584410574850>,

anywhere and everywhere [🖖🏽]