- From: Scott O'Hara via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Dec 2024 19:55:56 +0000
- To: public-svg-issues@w3.org
scottaohara has just created a new issue for https://github.com/w3c/svg-aam: == Review mapping for svg element == Opening regarding this NVDA issue - https://github.com/nvaccess/nvda/issues/13863 where it was mentioned (in March 2023) that SVG elements have inconsistent mappings across platforms / how even the ways that browsers are mapping this have their own unique issues. >Browser mappings for svg are pretty messy. According to the spec, the svg element should map to ROLE_SYSTEM_DOCUMENT, which IMO doesn't make any sense. Firefox maps it to IA2_ROLE_DIAGRAM to differentiate it from normal images which normally don't have any children. Chrome maps it to ROLE_SYSTEM_GRAPHIC, the same as normal images. So, neither browser follows the spec and all mappings have problems in various cases. I think this needs to get sorted out across the board. I'm just logging this issue as I was pinged about it - but otherwise dont' have much in the way of context/background here. Please view or discuss this issue at https://github.com/w3c/svg-aam/issues/38 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 December 2024 19:55:57 UTC