You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
guidelines, but suggestions for providing a consistent experience for users through different portals.
165
165
Different implementers may choose to implement these guidelines in a slightly different way, some examples
166
166
can be seen in the <ahref="#implementations">Implementations</a> section of the document.</p>
167
+
<sectionid="accessibility-claims">
168
+
<h2>Accessibility claims and declarations</h2>
169
+
170
+
<p>When presenting accessibility metadata provided by the publisher, it is suggested that the section is introduced using terms such as "claims" or "declarations." This heading should clearly convey to the end user that the information comes directly from the publisher and represents the accessibility information that the publisher intends to communicate.
171
+
</p>
172
+
</section>
167
173
168
174
<sectionid="metadata-ecosystem">
169
175
<h2>Publisher metadata ecosystem</h2>
@@ -261,7 +267,7 @@ <h3>Visual adjustments</h3>
261
267
262
268
<divclass="note">
263
269
<p>This key information should always be displayed, even if there is no metadata (See the examples where
264
-
the metadata is not known). </p>
270
+
the metadata is not known). </p>
265
271
</div>
266
272
267
273
<p>Indicates if users can modify the appearance of the text and the page layout according to the
<p>This publication is certified by Foo's Accessibility Testing </p>
501
507
<p>The certifier's credential is "Enterprise Accessibility Rating."</p>
502
508
@@ -781,7 +787,48 @@ <h4>Metadata techniques</h4>
781
787
</ul>
782
788
</section>
783
789
</section>
790
+
<sectionid="legal-considerations">
791
+
<h3>Legal considerations</h3>
792
+
<divclass="note">
793
+
<p>This key information should be hidden if metadata is not present .</p>
794
+
</div>
795
+
<divclass="note"><p>We are actively seeking comments on this "legal consideration" section. If you are a publisher, we want your feedback! Please visit the GitHub Issue tracking to leave a comment in the existing issue at: <divclass="issue" data-number="350"></div></p>
796
+
</div>
797
+
798
+
<divclass="note">Disclaimer: nothing here may be construed as legal advice supplied by W3C or any the groups or individuals who have contributed to this document.
799
+
Always get legal advice from in-house or your retained counsel to assess legal compliance and risk.</div>
800
+
801
+
<p>In some jurisdictions publishers may be able to claim an exemption from the provision of accessible publications, including the provision of accessibility metadata. This should always be subject to clarification by legal counsel for each jurisdiction.
802
+
One example of this, at time of writing, is from the EAA when the publisher is a micro-enterprise (i.e., enterprises employing fewer than 10 people and with annual turnover or balance sheet total not exceeding 2 million euro).</p>
803
+
<p>Other legal considerations currently included in the EAA may include exceptions on individual versions of a title, where jurisdiction will not require the title to be accessible if it involves a fundamental alteration of the content, or if making it accessible would place a disproportionate burden on the publisher. (This may vary in other jurisdictions).</p>
784
804
805
+
<p>Publishers may need to include information about an exemption or exception in metadata for legal or clarity reasons, either to bodies that enforce legislation or for other business to business communication. However this is not information that needs to be displayed on public sites as it does not mean anything to most consumers and could lead to misunderstandings. Nevertheless, the objective is to provide as much accessibility information as is possible."</p>
<p>This title may not yet be fully accessible to all readers. Check the list of accessibility features to determine if this title is suitable for your way of reading.</p>
<p>These guidelines provide a general framework and make suggestions on the display of accessibility
964
1011
metadata. It is not a normative description of what must be done. It is instructive to provide
965
1012
examples of implementations from the community. </p>
1013
+
<p>We are collecting information on companies and organizations that wish to possibly commit examples of their implementation. Please visit the GitHub issue to review companies and organizations that have volunteered. Please put your company name, your name and your contact information to possibly volunteer an implementation.</p>
1014
+
<divclass="issue" data-number="268"></div>
966
1015
967
1016
<p>Linked below are static pages that show real-life implementations. We have captured these examples
968
1017
from organization's websites that have agreed to allow us to showcase the work they have done to
0 commit comments