- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Mon, 25 Jan 2016 22:57:33 +0000
- To: Rich Schwerdtfeger <richschwer@gmail.com>, "public-aria@w3.org" <public-aria@w3.org>
- Message-ID: <SN1PR0301MB1981FEE036BBDB32048EC31898C70@SN1PR0301MB1981.namprd03.prod.outlook.>
> be inserted before the text found in role="presentation": "For any element with an explicit or inherited role of presentation, user agents MUST ignore any non-global, role-specific WAI-ARIA states and properties. However, the user agent MUST always expose global WAI-ARIA states and properties to accessibility APIs, even if an element has an explicit or inherited role of presentation." Would this only apply to images, or to all elements? If all elements, then this would change the naming calculation for all elements where aria-label is applied for example, where currently they are ignored in the computation. From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] Sent: Monday, January 25, 2016 2:46 PM To: public-aria@w3.org Subject: ACTION-1380 and ACTION-1700 Given the shortcomings of the SVG mappings regarding <img src=“foo.svg”> discussed on the list I am recommending we place the following text in the role=“presentation” text: revised proposed text: When the <img> is used to refer to either a raster image (e.g. <img src=“foo.jpg”>) or a vector graphics image <img src=“foo.svg”> it is treated as a single entity with all descendant elements being presentational. This is regardless of whether the target graphic has descendant elements that would normally be exposed to assistive technologies, such as with an SVG document. Consequently applying role=“presentation” or role=“none” are applied to the <img> they result is the same as aria-hidden=“true” is applied to the image. If it is possible to make the descendant elements accessible the SHOULD embed the document directly within the host document without it being referred to by <img>. be inserted before the text found in role="presentation": "For any element with an explicit or inherited role of presentation, user agents MUST ignore any non-global, role-specific WAI-ARIA states and properties. However, the user agent MUST always expose global WAI-ARIA states and properties to accessibility APIs, even if an element has an explicit or inherited role of presentation." Rich Schwerdtfeger
Received on Monday, 25 January 2016 22:58:09 UTC