26991 2014-10-07 15:45:11 +0000 Indicate clearly in the platform mappings which properties are fallback 2018-05-14 18:05:29 +0000 1 1 1 Unclassified ARIA Core AAM Future PC Windows NT RESOLVED INVALID P2 normal --- 1 jon.avila clown w3cbugzilla oldest_to_newest 112793 0 jon.avila 2014-10-07 15:45:11 +0000 Properties such as the title attribute can be used as an accessible name when other properties are not present -- this and other properties are sometimes considered fallback content --e.g. providing a name as a last resort rather than the most appropriate way to provide an accessible name. It would be helpful to indicate which properties are "fallback" to assist people determining what is sufficient or not for conformance claims. For example, a conformance claim often may not be met through relying on fallback content. 129258 1 w3cbugzilla 2018-05-14 18:05:29 +0000 I don't think an algorithm cares whether something is a fallback or not. It is up to WCAG to define what is acceptable for a conformance claim. The Core AAM documents what happens.