Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adding a requirement - backwards compatibility (not) #730

Merged
merged 5 commits into from
Mar 21, 2024
Merged

Adding a requirement - backwards compatibility (not) #730

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7b42d0c
Adding a requiement
alastc Jan 23, 2024
15c4004
Moved the backwards compat to 2.3
alastc Jan 30, 2024
d87c1bc
Terminology update
alastc Jan 30, 2024
5e61f45
Update requirements/index.html
alastc Jan 30, 2024
0b94bab
Merge branch 'main' into Issue569-backwards-compatibility
alastc Mar 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions requirements/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,9 @@ <h4>Maintenance</h4>
<li><strong>Evolving Technology</strong>: WCAG 3.0 needs a flexible design that can be updated as new technologies emerge, assistive technologies improve, and changing technologies produce new barriers for people with disabilities. Accessibility guidance and all supporting documentation should anticipate common scenarios like new technology and the introduction of new modalities like surface reaction and ultrahaptics. As content technology evolves, it must be re-evaluated against assistive technology for compatibility. Likewise, as assistive technology evolves or emerges, it must be evaluated against the backward compatibility of various content technology.</li>
<li>
<strong>Governance</strong>: Utilize tools that allow interested parties to predict when issues important to them are being discussed. Maintain a backlog that reflects issues along with their status. </li>
<li>
<strong>Backwards compatibility</strong> The WCAG 3 guidelines will take a cautious approach to backwards compatibility. After the first publication of WCAG 3 guidance and conformance model the guidelines aim to be backwards compatible. However, it will not be bound to backwards compatibility if a better, more accessible outcome can be achieved. Where there are backwards-incompatible changes, the changes will be included in the publication materials so that users of the guidelines know exactly what has changed.
alastc marked this conversation as resolved.
Show resolved Hide resolved
</li>
</ul>
</section>
<section id="opportunities_issue-severity">
Expand Down Expand Up @@ -231,9 +234,10 @@ <h3>Regulatory Environment</h3>
<h3>Motivation</h3>
<p>The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility.</p>
</section>
<section>
<h3>Scope</h3>
<section>
<h3>Scope</h3>
<p>The guidelines provide guidance for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. Our intent is to provide guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.</p>
</section>

</section>
</section>
Expand Down
Loading