- From: Pyatt, Elizabeth J <ejp10@psu.edu>
- Date: Wed, 7 Apr 2021 13:29:28 +0000
- To: Ms J <ms.jflz.woop@gmail.com>
- CC: w3c-wai-ig <w3c-wai-ig@w3.org>
- Message-ID: <676338EB-D0CB-41ED-B9EF-31BA07E6970C@psu.edu>
Yes, I have seen instances where some screen readers, especially older versions, are not able to interpret ARIA as intended. For instance, I would recommend using the HTML code for forms (e.g. LABEL/INPUT) rather than adding ARIA attributes on another element whenever possible. In 5-10 years, the answer might be different, but usually the older recommendations for screen readers still work. I would also agree that developers as well as accessibility professionals review ARIA specifications carefully. My two cents. Elizabeth On Apr 7, 2021, at 8:51 AM, Ms J <ms.jflz.woop@gmail.com<mailto:ms.jflz.woop@gmail.com>> wrote: 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<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fo0ukef&data=04%7C01%7Cejp10%40psu.edu%7C95c67fa14605405fe01008d8f9c48b8f%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C637533969837674425%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=cMqHPBJK826ctgATU70MA%2BKZOoYgUIXwGVWMV6Tv4rk%3D&reserved=0> =-=-=-=-=-=-=-=-=-=-=-=-= Elizabeth J. Pyatt, Ph.D. Accessibility IT Consultant ejp10@psu.edu<mailto:ejp10@psu.edu> The 300 Building, 112 304 West College Avenue University Park, PA 16802 accessibility.psu.edu<http://accessibility.psu.edu>
Received on Wednesday, 7 April 2021 13:29:44 UTC