- From: Ku, JaEun Jemma <jku@uic.edu>
- Date: Wed, 7 Apr 2021 14:41:30 +0000
- To: Jeremy Echols <jechols@uoregon.edu>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <9DA932A2-9014-4A2F-B0CC-CF9BF74EFB83@uic.edu>
I would also like to second Jeremy’s saying and point out another relevant resources, ARIA Authoring Practice Guide. https://www.w3.org/TR/wai-aria-practices-1.2/#read_me_first 2.1 No ARIA is better than Bad ARIA Functionally, ARIA roles, states, and properties are analogous to a CSS for assistive technologies. For screen reader users, ARIA controls the rendering of their non-visual experience. Incorrect ARIA misrepresents visual experiences, with potentially devastating effects on their corresponding non-visual experiences. Before using ARIA or any of the guidance in this document, please take time to understand the following two essential principles. Principle 1: A role is a promise Principle 2: ARIA Can Both Cloak and Enhance, Creating Both Power and Danger Best, JaEun Jemma Ku, PhD Assistant Director of Digital Accessibility Co-Facilitator and Editor of W3C ARIA APG<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps*3A*2F*2Fwww.w3.org*2FTR*2Fwai-aria-practices-1.2*2F%26data%3D04*7C01*7Cjku*40uic.edu*7C019cfb0067b6414019af08d8b74b87d8*7Ce202cd477a564baa99e3e3b71a7c77dd*7C0*7C0*7C637460882316299771*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000%26sdata%3Dp6U*2FjjHhjHi2HexN6YMu7imJiBTN*2FP8tDze*2BtMVe27c*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!DZ3fjg!pz5cC3-NjwaAQXUmHqHQ9v0UD9PRH6UUOw23A2CpVnJLd0arthDDQa28eAXsEyo81Q%24&data=04%7C01%7Cjku%40uic.edu%7Ceee223a4cc7f45a3e2f708d8e9c94b25%7Ce202cd477a564baa99e3e3b71a7c77dd%7C0%7C0%7C637516398039044314%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kJ3YDuFBno59MCfgdJ8S9IfRtCPmi6q%2Fd1uS83ldyy4%3D&reserved=0> Office for Access and Equity<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttp*3A*2F*2Fwww.uic.edu*2Fdepts*2Foae*2F%26data%3D04*7C01*7Cjku*40uic.edu*7C019cfb0067b6414019af08d8b74b87d8*7Ce202cd477a564baa99e3e3b71a7c77dd*7C0*7C0*7C637460882316309727*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000%26sdata%3DA5mKSj1vGGf4xDRgWqFyhIgchqUVlvZP28MNqFYQ*2FWM*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJSU!!DZ3fjg!pz5cC3-NjwaAQXUmHqHQ9v0UD9PRH6UUOw23A2CpVnJLd0arthDDQa28eAXBk3X7Dw%24&data=04%7C01%7Cjku%40uic.edu%7Ceee223a4cc7f45a3e2f708d8e9c94b25%7Ce202cd477a564baa99e3e3b71a7c77dd%7C0%7C0%7C637516398039054278%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CjaoFG28araqA9wwwmHigMPA1Pvuzqz%2F2G5zNWYwVRc%3D&reserved=0> University of Illinois Chicago Email: jku@uic.edu<mailto:jku@uic.edu> Under the Illinois Freedom of Information Act any written communication to or from university employees regarding university business is a public record and may be subject to public disclosure. From: Jeremy Echols <jechols@uoregon.edu> Date: Wednesday, April 7, 2021 at 9:14 AM To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org> Subject: RE: Aria roles Resent-From: <w3c-wai-ig@w3.org> Resent-Date: Wednesday, April 7, 2021 at 9:10 AM Bear in mind that ARIA is more of a “promise”. ARIA alone doesn’t actually change any behaviors. For a concrete example, if you make a link claim (through aria) that it’s a button, you also must use JavaScript to make it *act* like a button. It has to respond to the spacebar, not just the enter key. Most ARIA role changes will have behaviors that have to be built manually, and you may have to dig pretty deep in the w3c specs to be sure you understand them. In my opinion using aria where native HTML could suffice is a red flag that the site needs extra attention in an audit. Using ARIA like this can be an indication the devs didn’t really understand accessibility, but thought they did, and that tends to result in a more accessibility errors than completely ignorant developers. From: Bristow, Alan <Alan.Bristow@elections.ca> Sent: Wednesday, April 7, 2021 06:06 To: Ms J <ms.jflz.woop@gmail.com>; w3c-wai-ig@w3.org Subject: Re: Aria roles Hi Sarah, The ARIA spec is your friend here https://www.w3.org/TR/using-aria/#firstrule<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fwww.w3.org%2FTR%2Fusing-aria%2F*firstrule__%3BIw!!C5qS4YX3!XxW62ijOt64v98q0mrNQw7TMpsv5P7qehjndT8DFB8xVp9pbuw4XEpn365Fw4cTLdg%24&data=04%7C01%7Cjku%40uic.edu%7Cecbee9ea23cf4688a48308d8f9cf7181%7Ce202cd477a564baa99e3e3b71a7c77dd%7C0%7C0%7C637534016644624223%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=G5Ux8Xy5vd3edNEwTNHIoVM%2B9L9MQvThsLBsADl34dQ%3D&reserved=0> It says: If you can use a native HTML element [HTML51<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fwww.w3.org%2FTR%2Fusing-aria%2F*bib-html51__%3BIw!!C5qS4YX3!XxW62ijOt64v98q0mrNQw7TMpsv5P7qehjndT8DFB8xVp9pbuw4XEpn365H0TT507w%24&data=04%7C01%7Cjku%40uic.edu%7Cecbee9ea23cf4688a48308d8f9cf7181%7Ce202cd477a564baa99e3e3b71a7c77dd%7C0%7C0%7C637534016644634169%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BS2sE19BaufK%2FNgLgK9mSNuDjDUQrosN3TrztxW1JBk%3D&reserved=0>] or attribute with the semantics and behavior you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so. W3's emphasis, not mine (though I agree with it entirely). So while sometimes a restrictive back-end will not allow a particular type of HTML in a location, and then perhaps ARIA is needed to bend the "wrong" HTML to the role, this is sad and clearly not ideal (a better back-end publishing system would be an improvement). In a11y audits, generally I look for ARIA being used where there is not an HTML alternative; where it is adding to the HTML story rather than replacing it. For example, an open menu using aria-expanded="true" (etc) is a great addition to the semantics of a page. I hope that's helpful and not too ARIA-101. Regards, Alan -Alan Bristow Web Programmer Elections Canada alan.bristow@elections.ca<mailto:alan.bristow@elections.ca> From: Ms J <ms.jflz.woop@gmail.com<mailto:ms.jflz.woop@gmail.com>> Sent: Wednesday, April 7, 2021 8:51 AM To: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org> Subject: Aria roles Hi all I was wondering if there was anything that specified whether aria roles should be applied to specific elements. For example, I have often seen websites implement a lot of their functionality using links, and then give the links new aria roles such as ‘button’ or ‘radio’ to indicate their purpose rather than using the proper element in the first instance. Is this likely to cause any issues? Thanks Sarah Get Outlook for iOS
Received on Wednesday, 7 April 2021 14:41:45 UTC