internet explorer 8 does not support the textcontent property

For example, in a corporation or university and internal site may dictate the set of browsers and AT that are used/supported and thus determining whether something is AT supported may simply mean evaluating those dictated technologies. If alt cannot be used or it doesn’t make sense for alt to be used in the situation, teams must determine if the method used is accessibility supported.Īccessibility supported is different depending on the environment. In general, when the alt attribute can be used developers should continue to use the alt attribute. Methods indicated in the check for the failure indicate that the title attribute, aria-label, aria-labelledby, or alt could be used to provide alternatives. no sufficient technique was created - they are simply softening the failure to allow for newer techniques that are accessibility supported. The WCAG WG is not endorsing these methods for elements that can use alt i.e. This failure was updated by the WCAG working group to loosen the requirement that alt be mandated for these element types as long as another method is used and the method is accessibility supported. Failures are stronger than sufficient techniques and when a failure occurs it generally means a success criteria was not met unless another sufficient technique for the same element occurred or an alternative conforming page was present. Softening the failure to provide altįailure technique F65 for WCAG 2 SC 1.1.1 Non-Text Content is an existing documented failure to check for the presence of an alt attribute for an img, input type image or area element (either with a text alternative or null to indicate the image was decorative img).

In the technique an example is given a of a rating bar with several image elements wrapped in a div element with a role of “img”.Ī sufficient technique is not a requirement but one documented way of meeting a success criteria (in this case SC 1.1.1 Non-text Content) that is known to be accessibility supported (supported by major browsers and assistive technology). The sufficient technique ARIA10 was created to provide an example of how ARIA could be used to provide alternative text for an element that does not support the alt attribute by using aria-labelledby.

A New sufficient technique to promote ARIA for elements that don’t support alt This post serves to describe the change in position, its roots, and implications for use. A primary change is the allowance of new methods other than the alt attribute for non-text elements (e.g. In March 2014 the Web Content Accessibility Guidelines (WCAG) Working Group (WG) published several new ARIA techniques for WCAG 2 and updated several failure techniques.

Internet explorer 8 does not support the textcontent property