Success Criteria 3.2.4 Consistent Identification: [Level AA]
Any functional components must be identified consistently across all pages they appear in.
Techniques
Using labels, names, and text alternatives consistently
Text for some functional components may change across pages, but the format of it should be consistent.
In the following example there are two different images denoting downloads for team and player profiles. The alternative text is obviuusly different is consistent in its format.
<a href="download/player.pdf" <img src="player.gif" alt="Download player profile"> />
A page with with a search form at the top and bottom of the page should use the same text for the submit button.
<form id="topsearch" action="" method="GET" > <input id="search1"type="button" value="Search" </form> ... <form id="bottomsearch" action="" method="GET" > <input id="search2" type="button" value="Search" </form>
Failures
Labels, names, and text alternatives are not used consistently
Taking the search button example above, in this instant the text is different between the buttons.
<form id="topsearch" action="" method="GET" > <input id="search1"type="button" value="Search" </form> ... <form id="bottomsearch" action="" method="GET" > <input id="search2" type="button" value="Find" </form>
Text alternatives for navigation links on a page may state the page number that is the target of the link. If this were to be changed to 'Next page' and 'Previous page' on pages then this would be a failure.
<a href="#" title="Go to page 1" ><img src="images/previous.gif" alt="Go to Page 1" /></a> <a href="#" title="Go to page 3" ><img src="images/next.gif" alt="Go to Page 3" /></a>
<a href="#" title="Previous page" ><img src="images/previous.gif" alt="PreviousPage" /></a> <a href="#" title="Next page" ><img src="images/next.gif" alt="Next page" /></a>