This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26991 - Indicate clearly in the platform mappings which properties are fallback
Summary: Indicate clearly in the platform mappings which properties are fallback
Status: RESOLVED INVALID
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: Future
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Joseph Scheuhammer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-07 15:45 UTC by Jonathan Avila
Modified: 2018-05-14 18:05 UTC (History)
1 user (show)

See Also:


Attachments

Description Jonathan Avila 2014-10-07 15:45:11 UTC
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.
Comment 1 James Nurthen 2018-05-14 18:05:29 UTC
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.